Hugo behind Proxy

support
1

I am trying to use Hugo behind the Caddy webserver.

Once i get caddy up and running, and hugo running behind it, it seems to work as expected except for the websocket connections. My browser keeps trying to connect to ws://example.com:1313/livereload when it should be using ws://example.com/livereload.

The Hugo server is bound to port 1313 which is not accessible, the caddy server is bound to 80/443 and is accessible publicly.
Why does my browser always try to use port 1313?

2

I’m not sure, but, that sounds like a recipe for problems. Hugo’s webserver is designed for local dev work, not production, so the workflow is more like: get the hugo output folder to whereever Caddy can serve it.

1 Like
3

ah, i gotcha. new to static site generators, i think i know what my problem is.