Issue in running Web API reverse proxy with Caddy

[jei (Jeiman Jeya)]

@Whitestrake

There should be a message below this that explains how it failed (it couldn’t resolve DNS, the site refused the connection, the server timed out, etc). It’s important to know what actually isn’t working.

Ah you mean this: ERR_CONNECTION_REFUSED ?

@Whitestrake

Your first config was good. In fact, the five lines that you added are redundant with transparent - you’re essentially setting each header twice, which won’t cause any issues, but you can keep your Caddyfile nice and simple by just sticking with transparent . http:// is also implied and not strictly necessary.

Noted on this. I will revert those changes. Does it make a difference in using localhost or the internal ip address to build the server URL ? In most cases I have people simply use 0.0.0.0 along with the port.

@Whitestrake

No, this will start a new Caddy server instance. You can instead signal the existing instance with the USR1 signal to have it gracefully reload the new configuration with zero downtime (rolling back to the last good config if the new one has errors).

How do I go about doing this on a Ubuntu 18.04? Also, I am running Caddy using the One step installer bash script from the website.