After Activating SSL, Can no longer access sonarr, even locally

Sonarr version (exact version):
The latest stable I think? I can’t access to find out
OS:
Windows 10
((Debug logs)):
Logs don’t seem to exist anymore? I was able to capture this output by running from the console though:
https://pastebin.com/L4kG3CWH

Description of issue:
So I went into settings, enabled advanced view, Switched SSL to on, replaced http port 38082 with port 38088, entered port 38082 for https, pasted my SSL cert fingerprint which has been added to the windows cert store, clicked save, clicked system, clicked tasks, clicked the power button, clicked restart.

Sonarr came back up on ports 38082 over https and 38088 over http, but i can no longer access them. Not even from the local machine. I just get the error localhost refused to connect.

I cannot access sonarr to remove ssl or do anything else. The logs folder doesn’t seem to exist anymore and I can’t find a config file to change anywhere (assuming settings are saved in the database)

Help? … is there a safemode or way to edit the settings externally?

EDIT: As an added bonus, I believe I gave sonarr the wrong fingerprint and I’m pretty sure I have the correct one now.

EDIT: After reboot, the config.xml showed back up and I was able to turn ssl off. No idea what happened. SSL still not working though. Failed to add certificate, no phantom spaces, cert is imported to the local machine

What do the logs show now when you enable SSL?
I’d recommend trying without swapping the ports around, that may cause issues with the URL registration.

I changed both the http and https port to something completely new and unused and now the http works and the https still doesn’t. I get the same error: http://imgur.com/a/MER6y

If you run the netsh command Sonarr is running yourself do you get an error? (you’ll need to use an admin command prompt)

Ran the command in elevated powershell, nothing seems to happen… which may mean it was successfull?

It may not run properly under powershell, but I forget the output when it is successful. If it’s been registered running Sonarr again should not try to register it again.

Doing it manually in elevated cmd it gives the same error. Cert add failed, error 1312. Spcified logon session does not exist. It may have already been termianted.

Alright. I re-followed the instructions and created a passworded pkcs#12 archive and added it to the store and started sonarr again. This time it seems that it succeeded based on the output here:
https://pastebin.com/vT3JbkCV

However, I still can’t actually connect to the webpage on https or http at all, locally or remotely. Using the ip or the domain.

EDIT: Changed the ports to new never-before used ports and it works now… go figure. Hopefully sonarr team will implement the ability to just identify a cert and key path like every other service.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.