Web UI times out after install

[isaacngym]

Somehow my proxmox install borked itself, so i tried reinstalling 2 days ago.

My router is configured not to assign IPs outside 192.168.72.4 to 192.168.72.180. Used Balena to image 8.2-1 to a thumbdrive, booted into it, installed it. all good. Then I configured the installer to use 192.168.192/27, so that's 192-223. Installation finished, rebooted, was instructed to go to 192.168.72.192:8006.

https://192.168.72.192:8006 timed out on me.

Thinking i did something wrong, I reinstalled proxmox again. Still the same result. I tried to ssh into my proxmox box from another laptop, only to find that that didn't work (SSH used to work fine).

SSH from proxmox to my other linux machine works fine. Both machines can ping one another.

running `wget --no-check-certificate 192.168.72.192:8006" on the proxmox machine works. Running it from my other linux box does not.

nmap shows that port 8006 is not open.

running iptables -L shows this:

root@pve:~# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination


Chain FORWARD (policy ACCEPT)
target prot opt source destination


Chain OUTPUT (policy ACCEPT)
target prot opt source destination

and pveproxy status says running.

I'm puzzled - when I installed tailscale on my device on one of my reinstalls, and exposed localhost:8006 via tailscale serve i could access the admin console. good ol’ ssh worked fine when i would try connect to the tailscale IP address.


no idea what else the issue is - could anyone help me?

 

[esi_y]

Somehow my proxmox install borked itself, so i tried reinstalling 2 days ago.

This was because of the tailscale? (Reading from bottom up.)

My router is configured not to assign IPs outside 192.168.72.4 to 192.168.72.180. Used Balena to image 8.2-1 to a thumbdrive, booted into it, installed it. all good. Then I configured the installer to use 192.168.192/27, so that's 192-223. Installation finished, rebooted, was instructed to go to 192.168.72.192:8006.

Your 192.168.72.192/27 - I believe that's .193 to .222 for hosts. .192 is network address.

If you like these numberings, I suggest doing 10.x.y.z networks instead.

PS You can actually use DHCP too: https://forum.proxmox.com/threads/d...-only-no-static-reservation-necessary.155125/

 

[bbgeek17]

My router is configured not to assign IPs outside 192.168.72.4 to 192.168.72.180.

Is this because you are assigning IPs statically from that range?

192.168.192/27

Is your router configured to understand routing between 192.168.72 and 192.168.192 ?

It seems to me that you overcomplicated your network. Also some essential information is missing, i.e. netmask of 192.168.72 and how the two networks are supposed to talk to each other.

As usual, start with basics - check via curl against "localhost" and local IP whether PVE services are up directly from PVE.
Move on to checks from the host in the same network. Continue with more complex routing checks.

In the end, none of this is PVE specific or related to "Proxmox VE: Installation and configuration" , its basic networking and Linux management.

---

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

 

[esi_y]

Is your router configured to understand routing between 192.168.72 and 192.168.192 ?

I believe that was just a typo from the OP, it's all 192.168.72.192/27.

 

[bbgeek17]

I believe that was just a typo from the OP, it's all 192.168.72.192/27.

Anything is possible. In that case as you pointed out x.y.z.192 is the network address and not a valid setting for PVE's IP.
Additionally, we dont know what OP's client IP is, if it is outside the specified /27 range, is the router able to handle it.

In any case, if this is a home setup - its overcomplicated testing ground. Op should drop back to using /24 and make his network experiments in VMs.

---

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

 

[esi_y]

Additionally, we dont know what OP's client IP is, if it is outside the specified /27 range, is the router able to handle it.

I believe, as you ...

In any case, if this is a home setup

... he is doing all the hocus pocus just to satisfy having DHCP and some tiny safe-from-DHCP portion on the same route. Most home routers would not do custom routing tables.

Op should drop back to using /24 and make his network experiments in VMs.

But this is a genuine problem of the Installer, it e.g. allows you to set 10.10.10.0/24 just fine, should not be happening.

EDIT: Filed as https://bugzilla.proxmox.com/show_bug.cgi?id=5757