So this was it the entire time!!! Thank you so much!!! It is working now. So now I just need to get back to my docker container so Im not using precious RAM in my ESXi server.
So on my docker image I am using Portainer as a crutch. Basically I am running it with a few mapped volumes and ports but not much else.
My ports are
My volumes are:
HOST: /opt/caddy/Caddyfile to Caddy: /etc/Caddyfile
HOST: /opt/caddy/.caddy to Caddy: /root/.caddy
HOST: /opt/caddy/srv to Caddy: /srv
Of course. My luck and the docker container doesnt work…I’m getting a 502 Bad Gateway.
Both my Caddy and Hassio are on the same docker host. I used the exact same Caddyfile, except for changing the listening URL from test-hassio to hassio.
EDIT: Sorry for the delay in replying, apparently I hit some limit and had to wait since I am a new account EDIT-EDIT: I tried proxy’ing to another service. It works on my Caddy VM but not my docker image…
The Docker network controller provides recursive DNS services, usually.
Does Portainer let you create a Docker network and select it for use when you create a container? If so, give that a try, rather than the default network. I believe services on a custom network resolve each other by service name. This is certainly true of Compose projects.
Having your interface naming scheme as “enpXsY” rather than “ethX” is a feature of newer distros using systemd, I believe. I’m pretty sure it’s not a sign of the suitability of the hardware. Linux tends not to care too much about how cheap or old your gear is.
I won’t rule out a host DNS issue, though. I tend to like Compose projects because they set up a project-specific Docker network for you and it’s quite reliable on the inside. Downside is there’s still no hostname that resolves to the Docker host itself, though…