Unable to use web browser to configure server

S

Squam8s

New Member
Jun 29, 2025
6
0
1
Hello,

This is my first attempt at using proxmox and I am struggling immensely to get this off the ground, as you can probably tell by the title.

Initially, I tried to set up while using a USB wifi adapter as I have now learned was a terrible plan. Since then, I restarted completely, downloaded proxmox fresh while plugged directly into my router via ethernet. However, I am still facing the same issues. I am unable to use my browser to continue setup. See error message below:

1751222540067.png

In my attempts to solve this on my own, I saw that I should attempt to ping 8.8.8.8 and google.com to diagnose the problem. At one point, I was able to ping both of them, however, my attempted "solutions" now leaves me further behind than when I started.

When I ping 8.8.8.8 now, I receive "destination host unreachable" with 100% packet loss. And google.com now says "temporary failure in name resolution"

Honestly, I have lost track of what I have and have not edited, so i will attach images of my current setup for your viewing pleasure.

cat /etc/network/interfaces

IMG_2527.jpg

Please tell me what information you need from me to help advise further. Thank you in advance for any and all help.
 
The address in your browser is different than the one in your interfaces file. It's in a different subnet as well. What do you get if you run this on the node?
Bash: 
ifdown vmbr0; dhclient -v
 
What is the current output of ip a, so we can check the actual IP address and whether the cable is properly connected?
You set the IP address of the Proxmox host to 192.168.1.25 but tried connecting to 192.168.68.100. Have you tried https://192.168.1.25:8006/ ?
Is 192.168.1.25 outside of the DHCP range of your router? Is your router using 192.168.1.1/24?
 
Hello again,

I had life stuff get in the way, now I am back to work. I purchased a new HDD and replaced the one I previously had installed Proxmox on. This time, I did not change any settings from the start and left everything as default. I am still running into the same problem though. I have attached below images of outputs I believe to be useful for diagnosis. Thank you for your help in advance!!

cat /etc/network/interface
1753649115411.jpeg


cat /etc/hosts
1753649134833.jpeg

ip a
1753649198754.jpeg
 
Ip and gateway wise your config matches and looks okay to me and your node can speak to the router. Can you now reach https://10.0.0.86:8006?
If that still doesn't work I'd like to see the local ip of the device you use to access it and information about your network setup and how things are connected. Your device might not be in the same subnet or behind a different router or whatever. Hard to say but hopefully it was just that you used the wrong ip (192.168.86.100) initially to connect to a node configured with 10.0.0.86.
 
Last edited:
Sad. Can you ping 10.0.0.86 from your device? Please also share the information above.
 
The idea is to ping the node from your PC/laptop you use to access its webinterface. Having the node ping itself makes no sense.

As for the information
Impact said:
If that still doesn't work I'd like to see the local ip of the device you use to access it and information about your network setup and how things are connected.
Click to expand...

I'd also check these on the node but right now I suspect that this is a networking issue between your PC/laptop and the node, not a PVE service issue.
Bash: 
curl -Lkv localhost:8006
ss -lntp
systemctl status pveproxy
 
Last edited:
That all looks good. Pveproxy is listening on 8006, the node can reach its own GUI through that and you can ping the node.
I don't see a good reason why you can't reach the webinterface as well unless there's some firewalling going on or similar but perhaps I missed something.
Can you try this from the separate device too?
Bash: 
curl -Lkv --max-time 5 10.0.0.86:8006
traceroute -I4 10.0.0.86
 
Last edited:
You must log in or register to reply here.
Top Bottom