Proxy issue (probably)

[odyslam]

This project is great and super easy to setup!

One issue we have is that it doesn't seem to work behind a caddy reverse proxy. They both are deployed a docker compose project. Directly accessing the faucet works just fine, but behind the caddy it just returns a blank screen.

I have tried setting --proxycount to 1,2,3,4 and still the same issue (was testing if docker networking is incorrectly assumed as another reverse proxy due to the routing)

Caddyfile is pretty standard:

   handle_path /eth-faucet/http {
    	uri strip_prefix /eth-faucet/http
    	reverse_proxy eth-faucet:6942 {
    		header_up X-Real-IP {remote_host}
     	}
  	}

and all the other services we run with the docker compose work just fine. I am really out of ideas here (also it doesn't log anything else than it listens to port 6942, so it's extra hard to debug)

[iczc]

Try removing X-Real-IP and setting X-Forwarded-For instead.

https://github.com/chainflag/eth-faucet/blob/main/internal/server/middleware.go#L85

[odyslam]

Hey, so I spent quite a few hours yesterday and I think (thanks to Claude) that probably the API + FE are not made to be able to behave under a different path. The html and static assets are loaded, but the screen is blank so probably the svelte app is not running correctly.

Would love to make it work, cause otherwise I will have to host it outside of the reverse proxy deployment.

Here is my Caddyfile

{
    # Global Caddy settings
    admin off
    auto_https off
    debug
}
	
:8888 {
   handle_path /eth-faucet/http/* {
    	reverse_proxy eth-faucet:6942 {
    		header_up X-Real-IP {remote_host}
    		header_up X-Forwarded-For {remote_host}
    		header_up X-Forwarded-Proto {scheme}
    		header_up Host {host}
     	}
  }

}