FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login

    Reverse proxying doesn't work

    Scheduled Pinned Locked Moved
    Q&A
    0
    2
    615
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      narayan.dreamer
      last edited by

      Reverse proxying via caddy doesn't work. It gives 502

      CaddyFile Content As below

      # replace :80 with your domain name to get automatic https via LetsEncrypt
      https://<your_domain> {
        reverse_proxy fusionauth:9011
      }
      
      • fusionauth is service running in docker
      • caddy is running as service running in docker with above CaddyFile
      1 Reply Last reply Reply Quote 0
      • danD
        dan
        last edited by

        Looks like you got some help over in the FusionAuth containers project.

        I'm not super familiar with caddy, but you can also see other reverse proxy configurations (including which headers they forwarded) here: https://github.com/FusionAuth/fusionauth-contrib/tree/master/Reverse Proxy Configurations

        If you get it figured out, please consider submitting a PR to that repo with the caddy config so that others can benefit from your findings.

        --
        FusionAuth - Auth for devs, built by devs.
        https://fusionauth.io

        1 Reply Last reply Reply Quote 0
        • First post
          Last post