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

    Getting a this site can't be reached error to Proxmox web interface

    NAT
    2
    5
    1.5k
    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.
    • S
      SugaredAxe
      last edited by

      I just switched to pfsense from a UDM Pro and can no longer get to my Proxmox web interface. I have all of my servers on a separate vlan. I created a port forward to so I should be able to get to that interface.

      When I try to ping the address of my proxmox server, I do get a successful ping, so I am not sure why I am getting that error.

      Wireless LAN adapter Wi-Fi:

      Connection-specific DNS Suffix . : home.arpa
      Link-local IPv6 Address . . . . . : fe80::c85f:9995:b5f0:2ddb%8
      IPv4 Address. . . . . . . . . . . : 192.168.10.68
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Default Gateway . . . . . . . . . : 192.168.10.1
      PS C:\Users\tripl> ping 192.168.20.45

      Pinging 192.168.20.45 with 32 bytes of data:
      Reply from 192.168.20.45: bytes=32 time=1ms TTL=63
      Reply from 192.168.20.45: bytes=32 time=1ms TTL=63
      Reply from 192.168.20.45: bytes=32 time=1ms TTL=63
      Reply from 192.168.20.45: bytes=32 time=1ms TTL=63

      Ping statistics for 192.168.20.45:
      Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
      Approximate round trip times in milli-seconds:
      Minimum = 1ms, Maximum = 1ms, Average = 1ms

      I am not sure what I am doing wrong.

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

        @sugaredaxe said in Getting a this site can't be reached error to Proxmox web interface:

        I created a port forward to so I should be able to get to that interface.

        So you're accessing the Proxmox WebGUI though pfSense by forwarding the packets?

        What exactly do you get in the browser?

        If the same did work with the UDM Pro, could it be that it did masquerading the source address?

        1 Reply Last reply Reply Quote 0
        • S
          SugaredAxe
          last edited by

          I was using Opera, Chrome and Firefox and got the same error. I'm not sure why there is a difference. Here is the error that I am seeing:
          7e62c6cd-48df-45b2-b15c-75e224bfab10-image.png

          And how I have it set up in pfsense:
          9c556520-8dec-4809-9724-3e18e65851ed-image.png
          b234f4b3-dd14-4b6a-bcf2-d2c4e359d84d-image.png

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

            @sugaredaxe
            Still not clear, how you're trying to access Proxmox.

            Your browser show 192.168.20.45 and you have the same IP in the port forwarding for redirection target.
            So what? Do you type in 192.168.20.45 in the browsers address line directly? Or do you type in the pfSense WAN address?

            What is the shown interface? The one connected to Proxmox?

            Is the port correct? 8003 is not the standard port for Proxmox.

            1 Reply Last reply Reply Quote 0
            • S
              SugaredAxe
              last edited by

              @viragomann
              OMG I feel so stupid. I forgot that I had to put in https in the address instead of http. Thanks for all of your help.

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