Koalaman 1 Posted ... 1 minute ago, cheapsheep said: No. The revese_proxy still has to point to 8096 which is Jellyfins port: xxx.duckdns.org:6969 { reverse_proxy 192.168.86.43:8096 tls { dns duckdns {DUCKDNSToken} } } And then access it by using https://xxx.duckdns.org:6969 Thanks, gotta knock off now, but will try this later! Quote Share this post Link to post
OpenSourcerer 1435 Posted ... OP can leave xxx.duckdns.org without the port. When forwarding a port, one can enter 443 as the local port. That way, the Caddyfile does not need to be touched. Accessing Jellyfin is then done using the remote port. Thanks to Mr. cheepsheep for the hint. I took reachability on port 443 for granted, but of course it's not possible with AirVPN. Quote Hide OpenSourcerer's signature Hide all signatures NOT AN AIRVPN TEAM MEMBER. USE TICKETS FOR PROFESSIONAL SUPPORT. LZ1's New User Guide to AirVPN « Plenty of stuff for advanced users, too! Want to contact me directly? All relevant methods are on my About me page. Share this post Link to post
flat4 79 Posted ... this is a master class on caddyfile... thank you 1 OpenSourcerer reacted to this Quote Hide flat4's signature Hide all signatures pFsense it works Share this post Link to post
OpenSourcerer 1435 Posted ... 4 minutes ago, flat4 said: this is a master class on caddyfile... thank you Wait till you are using Caddy as a Markdown-based CMS. It's nuts. Only downside is that you will need to write your own CSS, there are no themes. Quote Hide OpenSourcerer's signature Hide all signatures NOT AN AIRVPN TEAM MEMBER. USE TICKETS FOR PROFESSIONAL SUPPORT. LZ1's New User Guide to AirVPN « Plenty of stuff for advanced users, too! Want to contact me directly? All relevant methods are on my About me page. Share this post Link to post
cheapsheep 6 Posted ... 9 hours ago, OpenSourcerer said: OP can leave xxx.duckdns.org without the port. When forwarding a port, one can enter 443 as the local port. That way, the Caddyfile does not need to be touched. Accessing Jellyfin is then done using the remote port. Thanks to Mr. cheepsheep for the hint. I took reachability on port 443 for granted, but of course it's not possible with AirVPN. Yes, sure. I just wanted to make it more understandable. That's why i assumed local and remote port stay the same in client area. Also, it is important what OpenSourcer already mentioned: Make sure you do not try to access the service while being connected to the SAME vpn server. This won't work. Quote Share this post Link to post