Cannot connect to new install through web GUI

mokaa

New Member
Jan 7, 2025
5
0
1
I am very new to this so expect some mistakes and give any suggestions.

I installed Proxmox 7.4 (8.3 installer was getting stuck on drivers)

I have a console on the machine I installed with a web address and the port. When I try to use my other pc to connect to that address it says
"

This site can’t be reached myIP took too long to respond.​

I tried changing the default ip to one similar to my pc. but no luck.
 
What does the command "ip a " on your Proxmox machine yield?
 
on "ip a" command ip a.jpg

But I have tried to change the ip address in the /etc/network/interfaces to a different ip
(I saw this on another post telling to do on this forum)
netwk.jpg

also this is what was on the final screen at initial setup (email is redacted)
WhatsApp Image 2025-01-07 at 14.46.03_738319e3.jpg
 
on "ip a" command
The text at the top (...100.2) is irrelevant, it is just text.
But I have tried to change the ip address
That did work, the first screenshot shows that vmbr0 is using that address.

Net steps in my FabU: "ip route ..." and the "ping"-tests.
 
  • Like
Reactions: Johannes S
The text at the top (...100.2) is irrelevant, it is just text.

That did work, the first screenshot shows that vmbr0 is using that address.

Net steps in my FabU: "ip route ..." and the "ping"-tests.
1736243582985.png
I may have messed up the ping.


However, I searched about the problem and found out that I need the IP to be in the range of my DHCP server.
The IP address pool my router shows is 192.168.0.2--192.168.0.249.

I have now reserved the .... .55 IP for the proxmox machine but it still isn't working
 
I may have messed up the ping.
Yeah, you cannot ping "http:"...

You should be able to ping your gateway, if ".1" is correct:
Code:
~# ping 192.168.0.1

If the gateway is pingable now, it should route traffic to the outside world:
Code:
~# ping 1.1.1.1

Only if the above is ok, let's check DNS
Code:
~# ping one.one.one.one


...that I need the IP to be in the range of my DHCP server.
After reserving that .55 this is fine. (Without reservation it is not.) It must be in that same network. If it is not, it could not reach the gateway at .1
 
Yeah, you cannot ping "http:"...
My bad. But now I can ping to the .... .55 IP. But not .... .55:8006
You should be able to ping your gateway, if ".1" is correct:
Yes I can ping to the gateway.
If the gateway is pingable now, it should route traffic to the outside world:
And I can ping 1.1.1.1
Only if the above is ok, let's check DNS

~# ping one.one.one.one
Works on my windows machine but not on the proxmox one
 
And visiting 192.168.100.2:8006 doesn't show anything in a browser on your Windows machine?
 
And visiting 192.168.100.2:8006 doesn't show anything in a browser on your Windows machine?
I just checked and it worked now. IDK how but it is somehow working now. Between yesterday and today I didn't do anything. Maybe the restart might have to do something with it
 
I just checked and it worked now. IDK how but it is somehow working now. Between yesterday and today I didn't do anything. Maybe the restart might have to do something with it
It worked because that IP is the IP on your local network. If you attempt to access that IP from inside your local network, it will always work. I'm glad it worked now. :)