Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Recently upgraded to 2.6.0. Now I can't get traffic on 443.

    Scheduled Pinned Locked Moved NAT
    1 Posts 1 Posters 538 Views
    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.
    • M
      Middge
      last edited by

      Good afternoon everyone. A few days ago I went ahead and updated to 2.6.0 (regret it so much now) and now I cannot get 443 traffic properly forwarded anymore.

      I have an nginx proxy manager, for which I created a rule to send all 443 and 80. I've been using this for well over a year now to proxy all of my local web apps without issue. I have split DNS so I can access these resources from LAN or WAN using the same certs and it was great.

      As soon as I updated to 2.6.0, this stopped working entirely. Every time I tried to hit any of my proxy hosts from LAN it would instead send me to my PFSENSE configurator, no matter which URL I used. I tried changing my configurator to use a different port and all that did was make it so my proxy hosts URLs led me to nothing at all.

      Lastly, I tried standing up an entirely new pfSense install @2.6.0 and load my config from backup. Same exact problem. At this point my only other solution is to try and roll back to 2.5.x and see if I can't get it up and running again.

      Does anyone else have any advise?

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.