Did you open ports in docket for 80, 443 for nginx and a port for jellyfin (in docker compose under services add these but with tabs not spaces ports: - 443:443)
Do you have ufw or a firewall running? This might be blocking the ports for jellyfin and/or nginx.
It might be easier to create a bridge network called proxy (docker network create proxy) then in docker compose add the following under services networks: - proxy
And at the bottom of the compose file
networks: proxy: external: true
Then in your nginx setting redirect to jellyfin:8096 (service name in docker compose: internal port jellyfin uses I.e. right hand side of ports mapping. Are you using straight nginx or nginx proxy manager (might be worth using this).
Can you access jellyfin locally on your network (http://internal-ip-of-server:8096/ on a browser)?
Has your DNS been setup to point to the correct ip your router is on? Are you behind a dynamic IP or cgnat? If cgnat, you have to use cloudflare tunnels. If ddns look into cloudflared docker image.
Does your router forward those ports to the correct internal ip of your server? Have you fixed the internal IP of the server machine?
Don’t share your certificate details but you can share your docker compose with personal information redacted or replaced
It’s probably not a good idea to publish jellyfin to the internet. Look into tailscale or cloudflare tunnel with login security, or wireguard.


I don’t know how any company I’ve worked for would operate, especially when headquartered in another country. They’ll just have to fire everyone in that country rather than compromise their security