[SOLVED] New PVE Install Unreachable

[ferhoodl]

Hello. This is my first time installing Proxmox. I looked at the installation docs and watched two youtube videos to ensure I installed it correctly. The machine boots up, and when I go to the address for the web interface, 'https://192.168.0.200:8006', I cannot reach the page. I am also not able to ping the address. The machine cannot ping servers like 8.8.8.8. I even tried scanning the network with Angry IP Scanner on another machine, and nothing shows up on the ip (192.168.0.200).

The output of 'ip a' and 'cat /etc/network/interfaces' are attached.

The settings I am using during the install:

Management Interface: enp3s0 - 04:7c:16:42:dd:43 (r8169)
Hostname (FQDN): normandy.local
IP Address (CIDR): 192.168.0.200 / 24
Gateway: 192.168.0.1
DNS Server: 192.168.0.1

I checked my router to see if it was blocking traffic on that ip address, thinking '. . .200' might be too high, but that does not seem to be the case.

The machine can ping itself, so it does not look like something is fundamentally wrong with the install.

I have installed it over 10 times trying different ip addresses, dns servers, etc.

One thing that might be useful is that the defaults loaded into the Hostname/IP address/gateway/DNS screen are these:

IP Address: 192.168.100.2
Gateway: 192.168.100.1
DNS Server: 127.0.0.1

I would use the defaults like the tutorials I have seen, but my network is on 192.168.0.XXX, not 192.168.100.XXX

Any help would be appreciated.

EDIT: Typos.

 

[bbgeek17]

Can you show corresponding IP configuration output from your workstation? If windows : ipconfig /all , arp

Also from PVE: lspci | egrep -i --color 'network|ethernet'

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Dunuin]

Looks fine so far.
Whats the output of ss -tulpn, systemctl status pveproxy.service pvedaemon.service and curl https://localhost:8006 -k | grep title?
Maybe another r8169 problem?

 

[bbgeek17]

You may be affected by : https://www.reddit.com/r/Proxmox/comments/11elzu4/help_r8169_fails_after_a_few_minutes_in_use/
Do a search on "proxmox r8169"

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[ferhoodl]

Thank you for the replies. I attached the results of the commands you gave me. I guessed on the flag for the 'arp' command on my windows machine, so tell me if you wanted a different one. I skimmed some information on the r8169 problem, and I'll look into it more.

 

[Dunuin]

192168.0.1

I guess that is a typo and not in your actual network config? Otherwise all is looking fine.

 

[ferhoodl]

I guess that is a typo and not in your actual network config? Otherwise all is looking fine.

That's right. Fixed them.

 

[ferhoodl]

You may be affected by : https://www.reddit.com/r/Proxmox/comments/11elzu4/help_r8169_fails_after_a_few_minutes_in_use/
Do a search on "proxmox r8169"

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

If it looks like everything is fine, I can try installing Proxmox on Debian, which is a suggested fix from the reddit post. Tell me if that is a good course of action. I'd like to use my motherboard's ethernet port and save a pcie slot if I can (as opposed to buying a NIC).

Edit: Deleted question from misread specs.

 

[ferhoodl]

Solved. It turned out that what I was told was ethernet was actually the signal straight from the ISP and not the decoded/routed signal from the modem/router. Plugging into actual ethernet fixed the problem.