[SOLVED] New install - can't connect to web GUI

[bawjaws]

Greetings all!!!

I'm just starting out on my Proxmox journey, and it's not been a flying start so far

I've done a fresh install on my pc (i5 9th gen, 64gb ram), and get through to the bit where it suggests going to the webgui to complete the setup. However, I can't connect to it at all.

I can ping the pve machine and it can ping everything else on the LAN. On the PVE machine, curl shows that an http response is sent when testing localhost:8006 and 192.168.1.90:8006. But when doing this from any other device on the LAN it fails.

I've looked at the open ports, and it seems that it's only listening on 8006 on the ipv6 address. Furthermore, the /etc/network/interfaces output seems to suggest that it has taken the ipv4 address I entered at the install stage (192.168.1.90) and turned it into an ipv6 address.

So it seems that the install has assumed it is on an ipv6-only network, but it's actually an IPv4 only network.

It's there a way to get proxmox to set up for an IPv4 only network?

 

[pille99]

run

ss -tlpn

and post the output plz
as i understand it listen to ipv4 and ipv6 as standard setting

 

[Dunuin]

So it seems that the install has assumed it is on an ipv6-only network, but it's actually an IPv4 only network.

To disable IPv6 entirely you could add net.ipv6.conf.all.disable_ipv6 = 1 to "/etc/sysctl.conf" and reboot.

 

[bawjaws]

run

ss -tlpn

and post the output plz
as i understand it listen to ipv4 and ipv6 as standard setting

Yeah that's what I thought too... Here's the output (sorry it's across 3 photos)

 

[leesteken]

192.168.1.90/32 can't be right, can it? Try 192.168.1.90/24 since your router is at 192.168.1.1.

 

[pille99]

192.168.1.90/32 can't be right, can it? Try 192.168.1.90/24 since your router is at 192.168.1.1.

you are right, i havent seen it.

 

[bawjaws]

192.168.1.90/32 can't be right, can it? Try 192.168.1.90/24 since your router is at 192.168.1.1.

How did I miss that?! Thinking back to the initial setup, I don't think I put a mask in next to the address so it's obviously assumed it was a /32.

What a complete numpty I am. Thanks for spotting it and helping! (It's now working, as you can probably tell )

 

[leesteken]

How did I miss that?! Thinking back to the initial setup, I don't think I put a mask in next to the address so it's obviously assumed it was a /32.

In my experience it does not and you have to type in 255.255.255.255 manually to get this effect (instead of 255.255.255.0) or DHCP did not function as expected.

What a complete numpty I am. Thanks for spotting it and helping! (It's now working, as you can probably tell )

Good to hear that it works now!