Reverse Proxy "Closed Ports" [PARTIALLY SOLVED]
I'm having an issue where I can't access my dashboard over https.
According to the docs of Jellyfin, for HTTPS requests they use port 8920 instead of 8096, so I also tried defining both in my Domains tab.
However inside Jellyfin I can't activate HTTPS, because it asks for a path to a PKCS-#12 certificate. But even the letsencrypt certificate that should be provisioned via traefik, does not seem to work, because when I visit
mydomain.com
, I get an invalid certificate warning and I can't open the certificate.

7 Replies
I have the same certificate issue with my dokploy dashboard as well. Is there maybe a port blocked that traefik/letsencrypt uses for certificate provisioning?
seems like it, but those ports are open in my firewall and everything 🤔

1. Jellyfin should not care about https. Let traefik deal with that
2. Do you have an A record point to your vps with that domain?
1. Alright. Mostly just did that, since just using the default 8096 with https enabled did not work either.
2. Yes, I do. Weirdly enough when entering
IP:3000
or IP:8096
, nothing happens
Also I use a homeserver, but all ports should be exposed.All using TCP protocol and I just added 3000 and 8096 for testing, but normally I obviously don't need to expose these.

I just set it up with the template and changed the domain tab to my own domain and it worked. Try to just use the template to do the inital setup
I did. Did no changes.
Just added my volume. Will try anyway tho.
@Henrik however traefik also fails to get a certificate for my dokploy dashboard. so it's probably something else.
i got ratelimited now, but even without that it failed with a 400 status code
ufw has 80, 8080 and 443 open, my router has these ports forwarded as well
I switched off Traeffik and manually do reverse proxies via Caddy now. Works fine-ish.