help setting reverse proxy with nginx proxy manager with duckdns

Quote from Roeegg2o

done.

ok...

Now go to Portainer, click on Containers and put a check next to your swag container and click Restart at the top...

Watch the swag log to make sure it restarts to "server ready" without any issue.

Once that is done.

Go to your jellyfin stack and edit it. We need to adjust your network mode for jellyfin

You currently have this:

network_mode: swag

As we saw from the docker inspect command, your network_mode for swag is swag_default

So, adjust accordingly

network_mode: swag_default

Redeploy your jellyfin stack

Give it a minute or so, then go to https://jellyfin.your-subdomain.duckdns.org and you should have your jellyfin sign in screen, and at the top by the URL, is a padlock it is secured.

Quote from Roeegg2o

still doesnt work..
isnt there something I should change in the Jellyfin settings in the webgui?

um, I don't think so. Let me check real quick.

just to double check..

if you go to https://www.your-subdomain.duckdns.org

You do get the swag park page right.. and there's a padlock by the URL?

Quote from Roeegg2o

nope, i get a connection timed out error

well that's probably the problem.

First..

Try using a phone, tablet, etc.. something that has a data plan. Take it OFF YOUR WIFI, and see if you can get to jellyfin.your-subdomain.duckdns.org. If it works from a data enabled device, I'll try to explain the problem. If it doesn't, try this next step.

Second...

Log in to your duckdns account at duckdns.org

Next to your subdomain is a public IP address

now go to http://wwww.whatismyip.com

Do those IP's match?

Quote from Roeegg2o

yes (ipv4)

And when you read the log, you did get a cert, right

As mentioned earlier by Soma i think, it seems you put this on an ntfs drive so there may be a permission issue here (although honestly I would have thought the swag container would not have even deployed, or you'd get an error it couldn't write to the folder).

cd - /srv/dev-disk-by-uuid-2A8CD8058CD7C989/Configs/

then

ls -l

One thing I just noticed, in your jellyfin stack, you're using PUID/PGID 1000, and your swag stack you're using PUID 1002 and PGID 100

You do have a user assigned with PUID 1002/1000 right? 100 is the default group for users, so every user is in that group.

Also if you didn't try, can you get to https://www.your-domain.duckdns.org on a tablet/phone not on your wifi?

hmm, that's interesting.

I just edited my post.

Can you on a phone/tablet that's not on your wifi go to https://www.your-domain.duckdns.org . If you do that, can you see your swag park page?

Quote from Roeegg2o

yes i do have a user with puid of 1002
i couldt reach it on my phone (after dissconnecting from wifi)

OK.

Try this

I don't think it will matter, but.. we'll see

cd /srv/dev-disk-by-uuid-2A8CD8058CD7C989/Configs/

chown -R root:users swagConf

then do an ls -l again, and you should see swagConf is different now.

Instead of being root:root on permissions

it should say root:users

If that's the case, restart swag. Watch the log and make sure there's no errors.

When it's done, see if you can go to https://www.your-subdomain.duckdns.org (on a device w/o wifi) and get the swag page secured with a padlock.

Quote from Roeegg2o

still the same..

I can only assume that is the issue. I don't deal with ntfs partitions/filesystems on my server.. but I know they often hae permission issues (still strikes me as strange you're stack is deploying, apparently without error.. ). Did you check it before you restarted swag or was that after you restarted swag?

Quote from Roeegg2o

Sorry, I had to go for a while..
I restarted the whole server but my domain is still and reachable and it still writes root:root

I can jellyfin.mydomain.duckdns.org, just cant access it from web

Well, if you can't reach http://www.your-domain.duckdns.org and get the swag park page secured, you'r enot going to get to jellyfin.

Only thing I can assume is the permission issues Soma mentioned due to this being an ntfs partitioned drive. That chown command I gave you, should have given your user read/write on that folder, but it clearly did not.. which sort of makes sense, given the fact you're trying to put Linux permissions on an ntfs formatted drive.

Quote from Roeegg2o

so I can access the partition drive but cant change user premissions on it? How can I bypass that?

Again, as far as I know.. you can't (I'll repeat, I don't use ntfs, just going off what others have said). You're attempting to put Linux permissions on a Windows filesystem.

You can try this (I don't think it's gonna work if the last one didn't, but we'll see). You said you had a username on this system (whatever one is assigned to 1002)

First, go to Portainer, and stop your swag container.

SSH your server

cd /srv/dev-disk-by-uuid-2A8CD8058CD7C989/Configs/

execute the command below, and try to change the permissions to your user.... (substitute ken0201 for your username.. remember it's case sensitive)

chown -R ken0201:users swagConfig

That should change permissions on the folder.. Example (understand this was done on a Linux filesystem):

First command I made a directory called Test

Second I checked the permissions on it with ls -l

Third I changed the permissions with chown command

Fourth, I checked that the permissions were properly changed.

root@openmediavault:/srv/dev-disk-by-uuid-26cefdd5-3caf-4bb2-ac2e-2fa87ba6328e# mkdir Test
root@openmediavault:/srv/dev-disk-by-uuid-26cefdd5-3caf-4bb2-ac2e-2fa87ba6328e# ls -l
drwxr-xr-x   2 root root   4096 Mar 16 07:10 Test
root@openmediavault:/srv/dev-disk-by-uuid-26cefdd5-3caf-4bb2-ac2e-2fa87ba6328e# chown -R ken0201:users Test/
root@openmediavault:/srv/dev-disk-by-uuid-26cefdd5-3caf-4bb2-ac2e-2fa87ba6328e# ls -l
drwxr-xr-x   2 ken0201 users  4096 Mar 16 07:10 Test
root@openmediavault:/srv/dev-disk-by-uuid-26cefdd5-3caf-4bb2-ac2e-2fa87ba6328e# 

If the change takes successfully, restart swag in Portainer.