Caddy in docker on synology not resolving

[ryanbas21 (Ryanb)]

So my post is very similar to this post: Caddy in Docker on Synology NAS - #18 by Amyrc

I just haven’t really figured it out, so I do apologize for a similar looking post.

I have caddy running in a docker image on synology, i have an A record setup on my domain, and i’ve fowarded on my router ports 8443 and 8080 / 443 & 80 (picture attached)

I have my caddy file like so:

{
    http_port 8080
    https_port 8443
}

home.domainhere.com {
    reverse_proxy 192.168.1.21:5000
}

registry.domainhere.com {
    reverse_proxy 192.168.1.21:4873
}

plex.domainhere.com {
    reverse_proxy 192.168.1.21:32400
}

The only A record right now is registry though so i would expect errors on the others.

If I curl my expected url, i get the following

curl -v https://registry.domainhere.com                                                                                                        ✔  6944  21:12:11
* Host registry.domainhere.com:443 was resolved.
* IPv6: (none)
* IPv4: myip
*   Trying myip:443...
* connect to `myip` port 443 from 192.168.1.15 port 52395 failed: Connection refused
* Failed to connect to registry.domainhere.com port 443 after 13 ms: Couldn't connect to server
* Closing connection
curl: (7) Failed to connect to registry.domainhere.com port 443 after 13 ms: Couldn't connect to server

So it feels (to me, not a networking expert at all) that i am missing a fowarded port?

Here are the ports for the docker image:
(wont let me post more than one image)

Local Port: 2019 TCP
Local Port 443 TCP/UDP
Local Port 80 TCP

[francislavoie]

Why are you using different ports for Caddy? Just use 80 and 443 (the defaults)

To me this just looks like a networking issue in front of Caddy, you’ll need to figure that out for yourself. I don’t see a problem with Caddy itself.

[ryanbas21 (Ryanb)]

Its because i think synology takes over the 443/80 ports i’ve read.