SABnzbd Forums

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

Could you enable Debug logging in the Status Window, wait for this error to occur and then send us the log at safihre@sabnzbd.org?
And also include the password-file or NZB-with-password. Then we can see what's going on.

This is on 2.3.0?

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?

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.

Sent:-)

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.

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

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.

Textforce is made by yyutaka, short for Yutaka Yagiura, who seems to be Japanese. So why UTF16 (not UTF8)? Maybe these quotes explain that:
"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."

Update: the Textforce author said:

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.

So ... can you check that in the Textforce app?

Yes, I have changed the option in setting to use 8...let’s hooe all,is now resolved.

Many thanks for your help,

Steve