Can't access my proxmox server URL

A

argjerryl

New Member
Jun 25, 2026
3
0
1
Hi everyone, new to using proxmox.
I dual booted my old computer now in the process of being setup as the homelab
I went through the inital setup process.
I tried accessing it the URL but my computer doesn't seem to pick up on it.
I assume it's a double NAT issue or I could be wrong.
Does anyone know what the issue and how to resolve it?
I put a couple of pictures if that helps
 

Attachments

  • IMG_7033(1).jpeg
    IMG_7033(1).jpeg
    576.7 KB · Views: 4
  • IMG_7035(1).jpeg
    IMG_7035(1).jpeg
    254.1 KB · Views: 4
  • IMG_7031(1).jpeg
    IMG_7031(1).jpeg
    166.5 KB · Views: 4
Hi @argjerryl , welcome to the forum.

What exact URL are you trying to access and what is the exact error you are receiving?

Could you answer these questions please:
  • What is the IP of your workstation?
  • Can you ping the PVE server?
  • Can you ssh into PVE server?
  • What is the output from your workstation? (ipconfig /all ; ip a)


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
  • Like
Reactions: leesteken
Your local network is probably not 192.168.100.0/24. The Proxmox installer picks 192.168.100.2 when DHCP does not give any IP address. Is the network controller supported by Linux? Is the cable attacked to your local router? Please check the subnet and router IP from another computer on your local network. The suggestions by @bbgeek17 will also help people discover what went wrong. This is a very common issue (not being able to connect because of not knowing your local network setup and/or not knowing Linux) and there are lots of similar threads on the forum.
 
  • What is the IP of your workstation?
[jerryarg@fedora]~% ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether e8:6a:64:c3:d4:88 brd ff:ff:ff:ff:ff:ff
altname enxe86a64c3d488
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 3e:c3:ac:4c:e2:5e brd ff:ff:ff:ff:ff:ff permaddr d4:3b:04:eb:0d:66
altname wlxd43b04eb0d66
inet 192.168.1.212/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp3s0
valid_lft 86150sec preferred_lft 86150sec
inet6 2600:4040:aa6d:d200:e708:47d9:d3e3:77b2/64 scope global dynamic noprefixroute
valid_lft 7017sec preferred_lft 7017sec
inet6 fe80::d818:495a:3fa1:5ad6/64 scope link noprefixroute
valid_lft forever preferred_lft forever
  • Can you ping the PVE server?
[jerryarg@fedora]~% ping 192.168.100.2
PING 192.168.100.2 (192.168.100.2) 56(84) bytes of data.
^C
--- 192.168.100.2 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4125ms

[jerryarg@fedora]~%
  • Can you ssh into PVE server?
[jerryarg@fedora]~% ssh root@192.168.100.2
^C
[jerryarg@fedora]~%
  • What is the output from your workstation? (ipconfig /all ; ip a)
[jerryarg@fedora]~% ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether e8:6a:64:c3:d4:88 brd ff:ff:ff:ff:ff:ff
altname enxe86a64c3d488
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 3e:c3:ac:4c:e2:5e brd ff:ff:ff:ff:ff:ff permaddr d4:3b:04:eb:0d:66
altname wlxd43b04eb0d66
inet 192.168.1.212/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp3s0
valid_lft 86150sec preferred_lft 86150sec
inet6 2600:4040:aa6d:d200:e708:47d9:d3e3:77b2/64 scope global dynamic noprefixroute
valid_lft 7017sec preferred_lft 7017sec
inet6 fe80::d818:495a:3fa1:5ad6/64 scope link noprefixroute
valid_lft forever preferred_lft forever
  • What is the output of "curl -k https://127.0.0.1:8006" when run directly from PVE (over SSH or physical console?)
[jerryarg@fedora]~% curl -k https://127.0.0.1:8006
curl: (7) Failed to connect to 127.0.0.1 port 8006 after 0 ms: Could not connect to server
  • What is the output of "curl -k https://<CHANGE_THIS_TO_YOUR_PVE_IP>:8006" when run directly from PVE (over SSH or physical console?)
[jerryarg@fedora]~% curl -k https://192.168.100.2:8006
^C

*All those with the "^C" I exited out of cause it was taking to long too respond believing that there is not a response.
 
argjerryl said:
inet 192.168.1.212/24
Click to expand...
As @leesteken mentioned, your existing subnet is different from the one you used on the PVE. You need to re-IP your PVE to place it in 192.168.1.0/24.
Pay particular attention to your existing DHCP ranges to avoid further conflicts

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
You must log in or register to reply here.
Top Bottom
Back