Sonarr version (exact version): v220.127.116.1101
Mono version (if Sonarr is not running on Windows): 4.42
Debug logs: https://www.dropbox.com/sh/vx6g77osc0u2qek/AAC4P5FcXVf7z9Beg4P6kWsna?dl=0
Description of issue:
I changed Sonarr settings on Fedora to try and get reverse proxy working (changed enable SSL + URL base as per https://github.com/Sonarr/Sonarr/wiki/Reverse-Proxy) and now it seems that Sonarr refuses to start on my server (which is odd in and of itself).
Getting the following:
Redirecting to /bin/systemctl status sonarr.servicesonarr.service - Sonarr DaemonLoaded: loaded (/usr/lib/systemd/system/sonarr.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2019-03-10 00:32:28 GMT; 1s agoProcess: 20844 ExecStart=/usr/bin/mono /var/hda/web-apps/sonarr/html/NzbDrone.exe -nobrowser -data /var/hda/web-apps/sonarr (code=exited, status=1/FAILURE)Main PID: 20844 (code=exited, status=1/FAILURE)
Mar 10 00:32:26 localhost.localdomain systemd: Started Sonarr Daemon.Mar 10 00:32:27 localhost.localdomain mono: Press enter to exit…
Mar 10 00:32:28 localhost.localdomain systemd: sonarr.service: Main process exited, code=exited, status=1/FAILURE
Mar 10 00:32:28 localhost.localdomain systemd: sonarr.service: Unit entered failed state.Mar 10 00:32:28 localhost.localdomain systemd: sonarr.service: Failed with result ‘exit-code’.
After uninstalling and reinstalling Sonarr on Fedora and restoring the backups, if I run “/usr/bin/mono /var/hda/web-apps/sonarr/html/NzbDrone.exe -nobrowser -data /var/hda/web-apps/sonarr” sonarr starts with the correct settings and database.
Further note: Nginx is loaded on a raspberry pi, so no direct changes apart from the above have been done to the Amahi installation.
Sonarr logs only appear if I run things manually via /usr/bin/mono (which is when I can get it to work)
Any ideas on what I’ve cocked up?