Support Forum

Sab started at 07:40 Accessed via https at 07:40 after start up tried to access via https at 07:42 and did not work accessed via http at 07:44 OK, I've had a look at your log (thank you), and I can see access entries for 7:40 and 7:44 but not the attempted TLS access at 7:42. ??? Can you please con...

Getting these errors quite a lot. The bad certificate one seems new. [06/Mar/2021:15:04:55] ENGINE Error in HTTPServer.serve Traceback (most recent call last): File "/opt/lib/python3.9/site-packages/cheroot/server.py", line 1810, in serve self._connections.run(self.expiration_interval) Fil...

Puzzled wrote: ↑March 4th, 2021, 1:17 pm Which browser are you using? Have you tried other browsers?

I’ve tried chrome and safari on my phone.

Also various apps

That hasn’t worked. If anything it’s worse. Only access on https for a few mins Bah! :( We don't use pyOpenSSL in SABnzbd! So that won't change anything. Ah, no worries. Thank you. :) @GTunney, are you able to post your entire SABnzbd log, and indicate the timestamps for each of your HTTPS access a...

A Google search for that error line gives this suggestion: https://stackoverflow.com/questions/65469633/sslerror-bad-key-share Nice find @Puzzled. :) I've just modified sherpa to use the PIP 'pyopenssl' package instead of the IPKG 'python3-pyopenssl' package provided by Entware. Let's see if it sol...

Including this from the QNAP forum in-case it's relevant: Not sure if this is something that might help with my SSL issue, just saw this in the logs from today. 2021-03-01 16:07:01,625::INFO::[notifier:122] Sending notification: Error - [01/Mar/2021:16:07:01] ENGINE Error in HTTPServer.serve Traceb...

Uptime with the QNAPclub 3.2.0 was over 24 hours and could still access via https.

I've now downgraded the sherpa package to 3.1.1 and will monitor.

I've run a clean and it's still doing the same issue. OneCD I'm happy to speak privately on the QNAP forums if you want to do some testing? No, let's keep the discussion here for now - it's easier to track the issue if everything is in one place. ;) No probs, thought I'd just update with some extra...

My understanding from @GTunney on the QNAP forum is that this only started when they upgraded to SAB 3.2.0. There were no problems prior to that with HTTPS. This didn't require an updated QPKG to be released - just a 'git pull' from within the existing package is sufficient. But, I guess a refresh ...

Yup, really need to know if any permissions change when the problem occurs. BTW: if you're only accessing SAB via your LAN (or via your local VPN server instance when outside your LAN), there's no-need for HTTPS. Any reason you're using it? ;) I don't know if the SAB login UI is safe to expose to t...

So, after you set 777 on [.qpkg/SABnzbd/config/admin], that settings is applied. Are you applying a recursive change to admin and all files or just the admin directory? You then restart SAB to generate new certs, everything works fine for a while, then you're unable to login via HTTPS, and the perm...

OneCD wrote: ↑February 28th, 2021, 3:38 pm Good.

When this problem occurs, are the permissions for the [.qpkg/SABnzbd/config] directory reset? Or is it only the [.qpkg/SABnzbd/config/admin] directory? What permissions are being assigned?

Not from what I can see. I gave it full access 777.

OneCD wrote: ↑February 28th, 2021, 3:09 pm

GTunney wrote: ↑February 28th, 2021, 1:38 pm ... and just randomly happens after a certain amount of time.

@GTunney, are you running Qboost by any chance?

No I’ve had it turned off since they first released it.

I tell a lie it’s still doing it

Really annoying now that it’s doesn’t list anything in the logs and just randomly happens after a certain amount of time.

That is bad. That means SABnzbd has no writing rights to ~/.sabnzbd/admin/ where it wants to create server.cert and server.key You have to solve that. SABnzbd can't do that for you. That actually looks like its done the trick, Sab now working with my sectigo cert after changing CHMOD on the admin d...