Thank you!!
My internet provider use CGNAT so i cannot enable port forwarding on my router, therefore in order to give my friends access to my Jellyfin server i need either to explain them how tailscale works and get it installed on their devices, or use tailscale funnel command to expose Jellyfin port on the public internet through Tailscale relay server
Tailscale funnel only works on port 8443 (and some more) so this is why I needed to have Jellyfin https listening on that port
Mind that i am already using tailscale serve command to redirect https to port 5000 where the tailscale certificate is provided, as in port 5001 the synology DDNS certificate replies by default
What would you recommend me doing?
By the way, further down there is a section named "require https" but i did not want to force it, i just wanted it work in parallel with http
It says "If checked, the server will automatically redirect all requests over HTTP to HTTPS"
I also read "Custom SSL certificate path" and "Path to a PKCS #12 file containing a certificate and private key to enable TLS support on a custom domain." which are requests not very comprehensible to me. :-(
My internet provider use CGNAT so i cannot enable port forwarding on my router, therefore in order to give my friends access to my Jellyfin server i need either to explain them how tailscale works and get it installed on their devices, or use tailscale funnel command to expose Jellyfin port on the public internet through Tailscale relay server
Tailscale funnel only works on port 8443 (and some more) so this is why I needed to have Jellyfin https listening on that port
Mind that i am already using tailscale serve command to redirect https to port 5000 where the tailscale certificate is provided, as in port 5001 the synology DDNS certificate replies by default
What would you recommend me doing?
By the way, further down there is a section named "require https" but i did not want to force it, i just wanted it work in parallel with http
It says "If checked, the server will automatically redirect all requests over HTTP to HTTPS"
I also read "Custom SSL certificate path" and "Path to a PKCS #12 file containing a certificate and private key to enable TLS support on a custom domain." which are requests not very comprehensible to me. :-(