Comment on Caddy reverse proxy fails with a login page

a14o@feddit.org ⁨6⁩ ⁨days⁩ ago

login.router.lan {
    reverse_proxy 192.168.1.1:80 {
        header_up Host {upstream_hostport}
    }
}

• irmadlad@lemmy.world ⁨5⁩ ⁨days⁩ ago

  Semi related, you can check the validity of Caddy entries into the caddyfile:

  • sudo caddy fmt --overwrite /etc/caddy/Caddyfile
  • caddy validate --config /etc/caddy/Caddyfile

  Where /etc/caddy/Caddyfile points to your caddyfile.

  source
• xavier666@lemmy.umucat.day ⁨5⁩ ⁨days⁩ ago

  I have tried this, but unfortunately, it did not work. I have tried this suite of commands

  login.router.lan {
      reverse_proxy 192.168.1.1:80 {
          # Preserve original host and scheme
          header_up Host {upstream_hostport}
          header_up X-Forwarded-Proto {http.request.scheme}
          header_up X-Forwarded-Host {http.request.host}
          header_up X-Forwarded-For {http.request.remote.host}
  
          # Keep cookies intact
          header_up Cookie {http.request.header.Cookie}
          header_down Set-Cookie {http.response.header.Set-Cookie}
  
          # Preserve Origin/Referer for CSRF tokens
          header_up Origin https://{http.request.host}
          header_up Referer https://{http.request.host}{http.request.uri.path}
      }
  }
  

  Info: My caddy uses HTTPS but the router login page is HTTP. Not sure if this is relevant.

  source