proxmox unable to connect to internet following first restart

gd0048

New Member
Mar 8, 2024
3
0
1
Hey guys,
i spent some time reading the forums here but i keep struggling with access to the web gui upon first restart after installation.
So I installed proxmox yesterday, I went in and configured the bios first, set up pass through, did some restarts everything was good. I shutdown and I added the Sata controller board, installed truenas scale. All good,
Today i still needed to add a nic - since then i have had problems. Pc Boots to the console. But i cannot connect to the web gui. So i am not sure if it switched to the new nic or what happened.
Well anyways i planned to move everything to a big ssd, so i did a clean install. got everything set up. Created the truenas vm again.
So i was reading that only upon the install will proxmox will issue its self an ip address. i have a tp link omado router, so i went ahead an reserved the address to make sure it always had access to that IP address, After everything was set up, i restarted the pc to test. And again no access to the webgui.

I am not sure if its related to the new nic, all of the problems started upon the install of it, so it makes me think it is. I'd assume if it was my router it would happen upon the install. But i currently have the system running and havent shut it off lol. So any advice on things i should look at and any guesses would be appreciated!

I am new to proxmox. I just like to learn and expirement with this stuff. So I probably do things the incorrect way, feel free to call me out on it. Just remember this server is not critical to my day to day. Id love for it to be reliable but hey if its not i get to learn alot more solving problems lol.
System
asrock x570
Ryzen 5700x
 
Welcome to the Proxmox community! :)

to be sure: You have an onboard NIC and added some PCI card with a further NIC?
Can you login at the console? If yes, the output of ip addr would be interesting.
Thank you!
So yes, the motherboard has a built in NIC and i added another PCI nic for passthrough to another VM.
192.168.0.3/24 is the Ip i have reserved at the router for the server. So I currently have it running, I am just afraid to test it by restarting the pc and end up not being able to access the webgui for the forth time.
Now when I was unable to access the webgui, i was still able to long on the console on the pc.


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
3: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether 9c:6b:00:13:96:81 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 9c:6b:00:13:96:81 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.3/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::9e6b:ff:fe13:9681/64 scope link
valid_lft forever preferred_lft forever
5: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr100i0 state UNKNOWN group default qlen 1000
link/ether 0a:52:f8:b5:5f:b7 brd ff:ff:ff:ff:ff:ff
6: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 92:e6:2b:46:b6:4b brd ff:ff:ff:ff:ff:ff
7: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether d2:1b:df:1c:48:9e brd ff:ff:ff:ff:ff:ff
8: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
link/ether 92:e6:2b:46:b6:4b brd ff:ff:ff:ff:ff:ff
17: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr101i0 state UNKNOWN group default qlen 1000
link/ether 5a:78:cc:45:c5:d3 brd ff:ff:ff:ff:ff:ff
18: fwbr101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 2a:43:c8:ba:55:9d brd ff:ff:ff:ff:ff:ff
19: fwpr101p0@fwln101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 96:db:d7:c5:67:87 brd ff:ff:ff:ff:ff:ff
20: fwln101i0@fwpr101p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP group default qlen 1000
link/ether 2a:43:c8:ba:55:9d brd ff:ff:ff:ff:ff:ff
 
Specifically, if PCI configuration has been changed - compare the output of "cat /etc/network/interfaces" to "ip addr", and confirm that the former has proper name of the interface, as it could have changed.



Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
The ip address shows the same. It is currently running(3rd reinstall). I will restart the system tomorrow. Nothing has changed so I assumed i upon the restart I will be unable to access the Webgui again. If so, i will recheck this information to see if anything has changed.
Thank you!

auto lo
iface lo inet loopback

iface enp5s0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.0.3/24
gateway 192.168.0.1
bridge-ports enp5s0
bridge-stp off
bridge-fd 0

iface enp3s0 inet manual
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!