I'm transitioning to a new VPS since my current provider is shutting down. Unfortunately, my domain is still linked to my old server, so I can only access my applications on the new VPS using its IP address and the corresponding ports. Currently, I'm having issues accessing my containerized app, `my_app`, which is set to use ports 8018:80. Here's the relevant section from my Caddyfile:
111.222.333.444:8018 {
reverse_proxy my_app:80
}
I'm having trouble accessing [https://111.222.333.444:8018](https://111.222.333.444:8018) and I'm not sure if I should be using `reverse_proxy localhost:80` or something different. I want to get at least one Docker container running before I switch my domain over to the new IP. Any guidance would be appreciated!
3 Answers
Caddy is usually easy to configure for reverse proxying, but it looks like there might be a few things to verify.
* Are you running Caddy in a Docker container?
* Is your Caddy instance configured to accept connections on port 8018?
* And does your firewall allow traffic through that port?
It sounds like the issue might not be with Docker or Caddy itself. Have you checked to make sure your VPS firewall isn't blocking incoming connections? Also, consider editing your local hosts file to point the domain name to the new IP temporarily for testing.
It seems a bit confusing. Just to clarify, you have your domain pointing to your old VPS, right? And you're trying to reverse proxy to the new VPS using its IP? If that's the case, could you provide a bit more detail on what you're trying to achieve? Just need to confirm how everything's set up!
Yeah, I've definitely messed up simple setups before! But to clarify, I've been running Caddy with Docker for years without issues. The main problem now is that since I'm setting everything up on a new server that doesn't yet have a domain name pointing to it, I'm trying to confirm I'm set up correctly using just the IP for now.