Hi,
I’m getting this message
“Unpacking failed, 'utf8' codec can't decode byte 0xff in position 0: invalid start byte”
When sabnz uses a password file with for example "ÿþxxxxxxx" where xxxxxx is the actual password in the text document.
Any ideas?
Cheers,
Steve
Error decoding
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Error decoding
Could you enable Debug logging in the Status Window, wait for this error to occur and then send us the log at [email protected]?
And also include the password-file or NZB-with-password. Then we can see what's going on.
This is on 2.3.0?
And also include the password-file or NZB-with-password. Then we can see what's going on.
This is on 2.3.0?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
-
- Newbie
- Posts: 17
- Joined: August 12th, 2017, 6:52 am
Re: Error decoding
I can’t find a enable debug logging, only a show logging and t prompts where to save. Shall I send ou that file after an error?
Re: Error decoding
In that window change the dropdown "Errors/Warnings" or "+Info" to +Debug.
Only then we will have with the next time it happens all the info.
Only then we will have with the next time it happens all the info.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: Error decoding
We found that the password file was encoded using UTF 16, which is rarely the case.
Solution is to create the passwords file via a basic editor and save it as plain text (UTF8 or ASCII), this is usually the default for notepad etc.
Solution is to create the passwords file via a basic editor and save it as plain text (UTF8 or ASCII), this is usually the default for notepad etc.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
-
- Newbie
- Posts: 17
- Joined: August 12th, 2017, 6:52 am
Re: Error decoding
Thanks. I edit the file using my iPad with an app called Textforce, that must be the source of the issue.
Will see how I can get round the issue.
Cheers
Steve
Will see how I can get round the issue.
Cheers
Steve
Re: Error decoding
Textforce is made by yyutaka, short for Yutaka Yagiura, who seems to be Japanese. So why UTF16 (not UTF8)? Maybe these quotes explain that:Greenblood wrote: ↑September 30th, 2017, 1:23 pm Thanks. I edit the file using my iPad with an app called Textforce, that must be the source of the issue.
"If you are in fact storing only Japanese text and space is a concern, you may be better off with UTF16."
"UTF-16 is better where ASCII is not predominant, since it uses 2 bytes per character, primarily. "
"UTF-16: <snip> Bad for English text, good for Asian text."
Re: Error decoding
Update: the Textforce author said:
So ... can you check that in the Textforce app?If user create new text files, Textforce save in UTF8 at default.
So, I don’t know why the saving result is UTF16.
Additionally, user can force select encode to UTF8 by app setting.
-
- Newbie
- Posts: 17
- Joined: August 12th, 2017, 6:52 am
Re: Error decoding
Yes, I have changed the option in setting to use 8...let’s hooe all,is now resolved.
Many thanks for your help,
Steve
Many thanks for your help,
Steve