Goofed up SSL, can no longer access Jellyfin remotely. - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access) +---- Thread: Goofed up SSL, can no longer access Jellyfin remotely. (/t-goofed-up-ssl-can-no-longer-access-jellyfin-remotely) Pages:
1
2
|
RE: Goofed up SSL, can no longer access Jellyfin remotely. - TheDreadPirate - 2023-12-07 That is. 1900 is DLNA, 7359 is the "auto discovery" function for local Jellyfin clients. Can you share your server logs with us? RE: Goofed up SSL, can no longer access Jellyfin remotely. - CoraBorealis - 2023-12-10 Sorry, for the delayed response! I was actually able to get it working by using Caddy as a reverse proxy with a domain from DuckDNS. The caddyfile wasn't nearly as scary is I initially thought it would be! HTTPS doesn't seem to want to work though, but I'm okay with that for now. At least I don't just have to give people a bare IP address for them to connect! |