Connection Failed Appears From My Transmission-Daemon Web Interface | Caddy | Reverse Proxy

[eeriemyxi]

I lost everything I wrote when I clicked "Preview" (cloudflare security check and then boom, empty input). This site needs an update. 30 minutes wasted.

I am sorry if this is a duplicate topic, but I have already tried several times to search "connection failed", but it didn't return anything even after waiting two minutes.

I also a novice when it comes to networking, I am sorry if anything I said does not technically make sense.

I am trying to reverse-proxy various locally hosted services using Caddy. I also use a dynamic DNS provider because my ISP does not give any static IP address.

This is the configuration file of Caddy (Caddyfle):

Code: Select all

:9090

reverse_proxy /jellyfin/* localhost:8096

reverse_proxy /radarr/* localhost:7878
reverse_proxy /sonarr/* localhost:8989
reverse_proxy /prowlarr/* localhost:9696

reverse_proxy /transmission/* localhost:9091

The issue is that the local instance of Transmission at http://localhost:9090/transmission/ works fine:

However, when I try to access it from the hostname provided by my dynamic DNS provider, say, http://eeriemyxi.example.com:9090/transmission/, I get this error:


This is the settings.json of my transmission-daemon: https://pastefy.app/w8wWD7ry

[darmok]

If you DIG at the external domain name, does it come back to you properly?

[eeriemyxi]

If you DIG at the external domain name, does it come back to you properly?

I tried the command, and the answered IP was different from my public address (same ISP though). So I went to the DNS provider's dashboard and manually updated the IP such that it would match my 32 bit public IP (IPv6 matches). Then I tried doing the command again to confirm - now the answer was my public address. So I went to see if it resolved the issue, but it didn't, I was still getting the same issue.