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

Proxy Configuration Warning

Scheduled Pinned Locked Moved Unsolved
Q&A
4
6
2.4k
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.
  • J
    jawaid.karim
    last edited by 13 Feb 2024, 16:39

    I have installed a test FusionAuth as a docker in Portainer, and am using NGINX Proxy Manager (also in Portainer) to proxy to it. The headers have been set, but am still getting the warning. It says to correct the origin, add the following request headers, which I have done - the only one it shows is X-Forwarded-Port: 443, this is set in the headers and can be seen when the headers are queried.

    the only difference between the Reported request origin and Actual request origin is that the latter one also shows the port number.

    I have looked at the other postings for this error, but no solution works.

    D 1 Reply Last reply 14 Feb 2024, 04:05 Reply Quote 0
    • D
      dan @jawaid.karim
      last edited by 14 Feb 2024, 04:05

      @jawaid-karim What headers have you set in NGINX to send to FusionAuth? What FusionAuth version are you running?

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

      J 1 Reply Last reply 14 Feb 2024, 16:17 Reply Quote 0
      • J
        jawaid.karim @dan
        last edited by 14 Feb 2024, 16:17

        @dan I have the following headers setup:

        X-Forwarded-Port 443
        X-Forwarded-Host fusion.mydomain.com
        X-Forwarded-Proto https
        X-Forwarded-For my_public_ip
        X-Forwarded-Server fusion.mydomain.com

        FusionAuth Version is 1.48.3

        D 1 Reply Last reply 6 Mar 2024, 20:39 Reply Quote 0
        • P
          pppp66535
          last edited by 26 Feb 2024, 10:42

          Dealing with proxy setups can be tricky. Have you tried adjusting the NGINX Proxy Manager settings to ensure it correctly forwards the port number in the request origin? Sometimes, it's a matter of fine-tuning those configurations.

          1 Reply Last reply Reply Quote 0
          • D
            dan @jawaid.karim
            last edited by 6 Mar 2024, 20:39

            @jawaid-karim Hmmm. Those all look good.

            So you are still seeing an error in the admin screen when you log in?

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

            S 1 Reply Last reply 8 Oct 2024, 23:04 Reply Quote 0
            • S
              skibirige @dan
              last edited by 8 Oct 2024, 23:04

              @dan Has there been any updates on this? I have my fusionauth application in cluster behind a proxy (nginx ingress controller) and I passing those same headers but I am getting a CSRF error. Please any help is more than welcome.

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