Support Forum

Ok, I will. Thanks! Consider this as solved. :-)

It looks like that is a binary file. When opening with vi or something like that, I can not read anything useful.

When I am right, it can't be solved that easy. But I can not remember what the cause is. :-D

Can I find out by looking up the errors in sabnzbd.log?

When I look at the logging, sabnzbd.log is rotated. Is it possibkle to add something like that for sabnzbd.error.log also? Or is it already there, and didn't I see it?

Thanks! I will play with that parameter.

Hi, Last days I see this warning a lot in the log: 2019-02-01 11:51:47,171::INFO::[assembler:91] Decoding /volume1/downloads/incomplete/Nice Movie (2018)/Nice Movie (2018).part01.rar yenc 2019-02-01 11:51:50,743::INFO::[directunpacker:143] Too many DirectUnpackers currently to start Nice Movie (2018...

I have no idea what happens ie with Chinese characters. No idea what the chardet package is.

You still want m to create a pull request? (Did not look into it yet.)

@safihr: I will @OneCD: yes, it is Maybe there is an easier way, but I created a script called all.psy (.sh is probably a better extension) that I start as postprocess-script, it contains : #!/bin/sh python /usr/local/sabnzbd/var/scripts/CharTranslator.py "$@" python /usr/local/sabnzbd/var...

I am using several postprocess-scripts. One of them is CharTranslator.py ( https://github.com/SynoCommunity/spksrc/blob/master/spk/sabnzbd-testing/src/CharTranslator.py ). This is getting rid of some terrible characters that are allways hard to handle at the prompt. Is it possible to integrate the '...

I can ignore it. I just want to be sure nothing is broken. It looks like everything works as expected.

> And is SAB reachable from Internet?
Yes, and off course not the default port

> SAB expects more input from that client, but the input is not coming, and it results in a timeout.
Can I find out what is going wrong? I really have no idea how, if possible, to fix this.

Yes, I have. This is the cause?

Every few days I get an error like this: Traceback (most recent call last): File "/volume1/@appstore/sabnzbd/share/SABnzbd/cherrypy/_cprequest.py", line 663, in respond self.body.process() File "/volume1/@appstore/sabnzbd/share/SABnzbd/cherrypy/_cpreqbody.py", line 989, in proces...

To be complete: opening port 80 was sufficient. It works now!

I created a certificate by using DSM on Synology, I exported this certificate and used it for SABnzbd. This is valid. :-)

Thanks! Now I understand. :-)

I am going to look at Let's Encrypt. Last question: should I only open port 80 during the creation of the certificate, or should it be open 'for ever'?