I've got binhex-sonarr,binhex-radarr,binhex-sabnzbget all using the container network of binhex-delugevpn for vpn with the argument "--net=container:binhex-delugevpn".

 

I've got nextcloud,OnlyOfficeDocumentServer,tautulli,binhex-plex running through a reverse proxy using letsencrypt. Their network is 'proxynet'.

 

Now I would I go about accessing sonarr or radarr through the reverse proxy as well. I can't just change their network from none to 'proxynet' can I? My goal is to access these containers from sonarr.* and radarr.* from the internet.

I've done this by just using the containers IP address/port in the letsencrypt conf file for each service. 

1 minute ago, Mathervius said:

I've done this by just using the containers IP address/port in the letsencrypt conf file for each service. 

Could you post an anonymous sample.conf. I'm fairly new to the game.

8 minutes ago, bigbangus said:

Could you post an anonymous sample.conf. I'm fairly new to the game.

So in your conf file you have something like this:

location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_whatever <IP_ADDRESS>;
        proxy_pass http://$upstream_whatever:<PORT_NUMBER>;
		
        proxy_set_header Range $http_range;
        proxy_set_header If-Range $http_if_range;
    }

You will use the containers IP address instead of its name. In your case you would use the VPN containers IP address and whatever port you use to access the service locally.

 

Don't forget to enable some sort of security if you are exposing these services to the web. Most of the conf files have something like this that you can use to get basic http auth setup at least:

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

 

Edited July 22, 20205 yr by Mathervius
further clarification

How do you determine the IP of the container? Is it something you have to set statically?

 

Here is my sonar config. it's network is passing through binhex-delugevpn in extra parameters.

OK I see now they are listed in the docker tab while the container is running. Are these static or will they change as I add/remove containers over time?

37 minutes ago, Mathervius said:

Don't forget to enable some sort of security if you are exposing these services to the web. Most of the conf files have something like this that you can use to get basic http auth setup at least:

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

 

So the security built into the sonarr docker GUI isn't sufficient?

Got it working by using 'binhex-delugevpn' in the sonar.subdomain.conf. Thanks again. Now just a question of security like you said...

    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 /ldaplogin;

        # enable for Authelia
        #include /config/nginx/authelia-location.conf;

        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_app binhex-delugevpn;
        set $upstream_port 8989;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    }

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

   }
}

 

For reference I was able to set the password in letsencrypt by opening a console window on the container:

htpasswd -c /config/nginx/.htpasswd <user>
New password: *********
Re-type new password: *********
Adding password for user <user>

Thanks again for the help. I guess it's up to me to choose between the container auth or the nginx auth.

I think you could go either way but I prefer using the letsencrypt container for it.

Would there be any updates to this?  I tried using both binhex-delugevpn and the local ip address in the sonarr.subdomain.conf file but neither one of them lets me through.  I still have the network type in the sonarr docker image set as None so that it goes through the binhex-delugevpn.

 

Suggestions are welcome!

This doesn't seem to work for me either. Not using the VPN container name or it's IP address.