Hello!

I'm on the latest version of unRAID (6.6.6) and I followed @SpaceInvaderOne's guide on how to set up a reverse proxy with Letsencrypt. Both "rutorrent.domain.com" and "nextcloud.domain.com" works without any problems at all. But I also set up "sonarr.domain.com" and "radarr.domain.com", neither of these work. What happens is that it asks for the password and after I log in I get stuck in the loading screen. 

 

It still works fine when I enter the local ip address so I can still access it.

I'm using binhex's version of both of them, I have since updated all of the software being used; unraid, binhex-sonrr, binhex-radarr and letsencrypt.

Current version of Sonarr is 2.0.0.5252 and radarr is 0.2.0.1217.

came across your post while searching online with the exact same problems you are having.

 

I forgot to rename the sonarr name to binhex-sonarr in the "location ~ (/sonarr)?/api" section of the code in the sonarr.subdomaion.conf file. I only renamed it in the "location /" section. I made the change and everything works. Silly mistake that I should have never made. Hope this helps.

 

Here's my sonarr.subdomain.conf file:

 

# make sure that your dns has a cname set for sonarr and that your sonarr container is not using a base url

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name sonarr.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /login;

        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_sonarr binhex-sonarr;
        proxy_pass http://$upstream_sonarr:8989;
    }

    location ~ (/sonarr)?/api {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_sonarr binhex-sonarr;
        proxy_pass http://$upstream_sonarr:8989;
   }
}

 

@iamali

Damn, I did the exact same thing. Never would have thought about this, thanks for the help. 

@iamali Thanks!

On 12/25/2018 at 1:13 AM, iamali said:

came across your post while searching online with the exact same problems you are having.

 

I forgot to rename the sonarr name to binhex-sonarr in the "location ~ (/sonarr)?/api" section of the code in the sonarr.subdomaion.conf file. I only renamed it in the "location /" section. I made the change and everything works. Silly mistake that I should have never made. Hope this helps.

 

Here's my sonarr.subdomain.conf file:

 

# make sure that your dns has a cname set for sonarr and that your sonarr container is not using a base url

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name sonarr.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /login;

        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_sonarr binhex-sonarr;
        proxy_pass http://$upstream_sonarr:8989;
    }

    location ~ (/sonarr)?/api {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_sonarr binhex-sonarr;
        proxy_pass http://$upstream_sonarr:8989;
   }
}

 

Thank you, i had made the same mistake