Unfortunately I'm unable to post in the docker container support page (maybe I'm too new?)

 

I've spent the better part of the last 16 hours attempting to run through this guide:

 

https://emby.media/community/index.php?/topic/94566-guide-setup-emby-with-hw-transcoding-on-unraid-remote-access-through-reverse-proxy-using-swag/

 

I have followed everything to the letter half a dozen times, but when I get to the very end and attempt to test the domain, I get this message (pic attached) on the screen, where as it should be going directly to the Emby login page.

 

Can anyone help to troubleshoot why I'm having this issue? I'm at my wits end and have been troubleshooting and retrying this for the last 12 hours with no luck.

 

Diagnostics log is also attached.

maverick-diagnostics-20230323-1222.zip

Thats the screen that defaults for your domain once swag is setup.  Did you setup a subdomain for emby?  Did you edit the emby.subdomain.conf.sample file in SWAG and rename the file to emby.subdomain.conf with any edits that may be required?

Edited March 23, 20233 yr by Gragorg

34 minutes ago, Gragorg said:

Thats the screen that defaults for your domain once swag is setup.  Did you setup a subdomain for emby?  Did you edit the emby.subdomain.conf.sample file in SWAG and rename the file to emby.subdomain.conf with any edits that may be required?

 

Hey there,

 

Yes I followed the setup included in the link exactly. I created a subdomain using NO-IP.com having the domain hopto.org.

 

I edited the emby.subdomain.conf.sample file to reflect the subdomain I am using, as well as the adjusted docker name of "EmbyServer" instead of "emby". I resaved it as "emby.subdomain.conf". Should I be deleting the old sample file once I resave the new file?

 

Thanks for replying.

So "yourhostname".hopto.org will show you the swag screen.  When you type in emby."yourhostname".hopto.org (or whatever your subdomain is) it still takes you to the swag screen?  When you look in the SWAG log did it issue an ssl certificate for emby? 

Edited March 24, 20233 yr by Gragorg

4 hours ago, Gragorg said:

So "yourhostname".hopto.org will show you the swag screen.  When you type in emby."yourhostname".hopto.org (or whatever your subdomain is) it still takes you to the swag screen?  When you look in the SWAG log did it issue an ssl certificate for emby? 

Is that how it works though? My understanding was just that his subdomain he created was emby, not that it’s emby, then his subdomain, then the domain. 
 

If I try to go to emby.XXXX.hopto.org it just comes back saying “ip address cannot be found”, vs if I go to XXXX.hopto.org I still get the swag screen. 
 

Also yes I checked the logs and confirmed it is approving an SSL cert so I’m all good there, but I don’t know how I would confirm it’s for emby specifically?

This is the sample file for emby

 

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

    server_name emby.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app emby;
        set $upstream_port 8096;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_set_header Range $http_range;
        proxy_set_header If-Range $http_if_range;
    }
}

 

So normally where is says server_name it is showing "emby.*" which means "emby.XXXX.hopto.org" (no need to edit this if emby is your subdomain)

set $upstream_app is the name of your docker

$supstream_port is the port emby uses

 

I'm not really very familiar with noip as I use duckdns.org but usually you setup a domain and then use a subdomain for every docker you want a reverse proxy for.

 

In your swag setup are you specifiying a subdomain for emby

 

You dont own hopto.org you own XXXX.hopto.org

Edited March 24, 20233 yr by Gragorg

14 minutes ago, Gragorg said:

This is the sample file for emby

 

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

    server_name emby.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app emby;
        set $upstream_port 8096;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_set_header Range $http_range;
        proxy_set_header If-Range $http_if_range;
    }
}

 

So normally where is says server_name it is showing "emby.*" which is "emby.XXXX.hopto.org

set $upstream_app is the name of your docker

$supstream_port is the port emby uses

 

I'm not really very familiar with noip as I use duckdns.org but usually you setup a domain and then use a subdomain for every docker you want to us reverse proxy for.

 

In your swag setup are you specifiying a subdomain for emby

 

You dont own hopto.org you own XXXX.hopto.org

yes this is the conf file I adjusted and re-saved without the sample extension. 
 

the server name is adjusted from emby to your subdomain name you created. and the upstream app is adjusted from emby to match the docker, which when using the official app is EmbyServer. I have adjusted both those settings. The port is also correct. 

So what do you have listed for servername?  Also I assume you followed the custom docker network part and selected it when you set up your docker?

 

One other thing to check is that emby and swag are both setup using your custom docker network you created

Edited March 24, 20233 yr by Gragorg

2 hours ago, Gragorg said:

One other thing to check is that emby and swag are both setup using your custom docker network you created

 

2 hours ago, Gragorg said:

So what do you have listed for servername?  Also I assume you followed the custom docker network part and selected it when you set up your docker?

 

 

Currently it is set up as waltflix. So the custom domain I created is named that. 

 

In the adjusted sample file that is what I have the server_name set to, as that is what theh guide referenced.

 

I then have the set $upstream_app set to EmbyServer for the name of the docker container, and the $upstream_port set to 8096

 

EDIT: Yes I also went through setting up the custom docker network and just followed the same name he used in the guide. Both dockers are setup on that network.

Edited March 24, 20233 yr by Ezekial66
Additions

Normally you setup a domain with duckdns or noip and then use subdomains for every docker you want to proxy.  Maybe post a pic of swag docker setup and emby docker setup screen. 

Apologies on the delay, I was away for the weekend.

 

I thought the domain was the main 'no-ip' address (in this case hopto.org), as I don't own the domain, and my subdomain is the one I created in step one of the guide? (in this case, waltflix).

 

Going to pm you if that's alright as we're starting to get into more detailed info and I'm unsure of what should be kept confidential and what I can share.