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

    [Solved] Accessing port 441 over HTTPS locally?

    Scheduled Pinned Locked Moved NAT
    5 Posts 2 Posters 718 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.
    • T Offline
      truetype
      last edited by

      My unraidserver is running nginx (letsencrypt) on port 441 since 443 is in use by unraid itself now in the latest update 6.4.0… Before the update I run nginx at port 443 with no issues, but now I had to change it to another port and I choose 441 and now I cannot get it to work locally. :(

      I have setup portforwarding in NAT to my server (192.168.1.8 ) from 443 to 441 and I can reach my server from outside my network.
      But locally I cannot reach it... I have tried as much as I could think of but with no success... :(

      Please help me out, see attached screenshots for my settings.

      portforward.PNG
      portforward.PNG_thumb

      1 Reply Last reply Reply Quote 0
      • V Offline
        viragomann
        last edited by

        How have you tried to reach the server? https://192.168.1.8:441 should work.

        Do you have multiple internal interfaces or just only LAN?

        1 Reply Last reply Reply Quote 0
        • T Offline
          truetype
          last edited by

          @viragomann:

          How have you tried to reach the server? https://192.168.1.8:441 should work.

          Do you have multiple internal interfaces or just only LAN?

          I have LAN, WLAN and OPT2 (vpn).

          The thing is I am running nextcloud (444) via reverse proxy through nginx (441) and I've setup to only reach my nextcloud via the domain "https://nextcloud.mydomain.com" so I cannot reach it by the local IP.

          Sorry, should've written that from the start.

          EDIT
          For temporary fix I changed Unraid's port (inside unraid OS) from 443 to 441 and changed back nginx from 441 to 443 so now it's working as it should, but I prefer having Unraid using it's default port if possible.

          1 Reply Last reply Reply Quote 0
          • V Offline
            viragomann
            last edited by

            So NAT reflection could be a solution for you. You can select a NAT reflection method in the corresponding NAT rule. Try if "pure NAT" works, otherwise try "NAT + proxy".

            1 Reply Last reply Reply Quote 0
            • T Offline
              truetype
              last edited by

              @viragomann:

              So NAT reflection could be a solution for you. You can select a NAT reflection method in the corresponding NAT rule. Try if "pure NAT" works, otherwise try "NAT + proxy".

              Sorry for late reply, been sleeping and working.

              That didn't work for me unfortunately.. I'll guess I'll go with the solution where I changed unraids port, I can't see that it would do any difference.

              Thanks to you anyways!

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