Can't access WebUI

W

Wozar

New Member
Dec 23, 2024
6
1
3
Hi There,

I am new to proxmox and I have spent hours on these forums trying to solve an issue where my brand new, fresh install of Proxmox (which seems to be running fine) won't allow me to connect using the WebUI.

I have re-installed multiple times, changed static IP addresses and every other tip I can find but still no luck.

I can ssh to the machine with no problems.
I can ping it from every device in the house
It is coming up as the correct hostname in the Unify console.

Here is all the info I have; if someone could cast their eye over this and point out where I have gone wrong, I would very much appreciate it.

Static IP Address on my local network is set to 192.168.1.168

I used the hostname pve1.pve.lan

IP - a gives me
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
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether 10:62:e5:16:dd:38 brd ff:ff:ff:ff:ff:ff
altname enp0s31f6
3: wlx90de80b42029: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 90:de:80:b4:20:29 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 10:62:e5:16:dd:38 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.168/22 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::1262:e5ff:fe16:dd38/64 scope link
valid_lft forever preferred_lft forever

From my machine i get the following:

C:\Users\Warre>curl https://192.168.1.168/8006 -k
curl: (7) Failed to connect to 192.168.1.168 port 443 after 2039 ms: Could not connect to server

It is connected via Ethernet cable to my main switch with all other devices on it.


I have tried with multiple browsers.

One thing I am sure of is that it is something I have done. I see lot's of "can't connect to webUI" posts and it always turns out to be a config issue, I just can't see where I have gone wrong.
 
What is the output of cat /etc/network/interfaces? What is the IP of your local router/gateway? Are you sure /22 is correct and it should not be 192.168.1.168/24 instead?
 
Here is the output

auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.1.168/22
gateway 192.168.1.1
bridge-ports eno1
bridge-stp off
bridge-fd 0

iface wlx90de80b42029 inet manual


source /etc/network/interfaces.d/*


changing to /22 was one of the trouble shooting tips I found that was to extend the range of available IP's
 
Please make sure that 192.168.1.168 is not in the DHCP-range of the router. Some routers block traffic from devices in the DHCP-range that do not use DHCP (like Proxmox).
Does your curl command work on the Proxmox host itself? Can you ping or connect to 192.168.1.1 from the Proxmox host? Are the PVE services running (systemctl status pve*)?
 
System ctl results:

Loaded: loaded (/lib/systemd/system/pve-query-machine-capabilities.service>
Active: active (exited) since Mon 2024-12-23 19:43:56 AEDT; 51min ago
Process: 543 ExecStart=/usr/libexec/qemu-server/query-machine-capabilities >
Main PID: 543 (code=exited, status=0/SUCCESS)
CPU: 1ms

Dec 23 19:43:56 pve1 systemd[1]: Starting pve-query-machine-capabilities.servic>
Dec 23 19:43:56 pve1 systemd[1]: Finished pve-query-machine-capabilities.servic>

● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; preset: ena>
Active: active (running) since Mon 2024-12-23 19:43:59 AEDT; 51min ago
Process: 860 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCE>
Main PID: 880 (pvestatd)
Tasks: 1 (limit: 38140)
Memory: 146.6M
CPU: 16.254s
CGroup: /system.slice/pvestatd.service
└─880 pvestatd

Dec 23 19:43:58 pve1 systemd[1]: Starting pvestatd.service - PVE Status Daemon.>
Dec 23 19:43:59 pve1 pvestatd[880]: starting server


I will look into making sure the ip address is not in the DHCP range - It is a unify network so there must be documentation on this somewhere.

Can ping the gateway from the proxmox instance no problem.
 
ssh into your node, and do ss -lnp | grep 8006 it should list pveproxy worker running on port 8006. If not, the service is not running. Check for details with service pveproxy status . Also check ss -lnp | grep 8006 to see if the port is allowed through the firewall.
 
Here is the result - not sure what this tells me? is it running?

root@pve1:~# ss -lnp | grep 8006
tcp LISTEN 0 4096 *:8006 *:* users:(("pveproxy worker",pid=907,fd=6),("pveproxy worker",pid=906,fd=6),("pveproxy worker",pid=905,fd=6),("pveproxy",pid=904,fd=6))



Also get:
root@pve1:~# service pveproxy status
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: ena>
Active: active (running) since Mon 2024-12-23 19:44:01 AEDT; 1h 23min ago
Process: 899 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited,>
Process: 901 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCE>
Main PID: 904 (pveproxy)
Tasks: 4 (limit: 38140)
Memory: 170.4M
CPU: 1.756s
CGroup: /system.slice/pveproxy.service
├─904 pveproxy
├─905 "pveproxy worker"
├─906 "pveproxy worker"
└─907 "pveproxy worker"

Dec 23 19:44:00 pve1 systemd[1]: Starting pveproxy.service - PVE API Proxy Serv>
Dec 23 19:44:01 pve1 pveproxy[904]: starting server
Dec 23 19:44:01 pve1 pveproxy[904]: starting 3 worker(s)
Dec 23 19:44:01 pve1 pveproxy[904]: worker 905 started
Dec 23 19:44:01 pve1 pveproxy[904]: worker 906 started
Dec 23 19:44:01 pve1 pveproxy[904]: worker 907 started
Dec 23 19:44:01 pve1 systemd[1]: Started pveproxy.service - PVE API Proxy Serve>
 
ss is showing that the service is listening on port 8006, which is the port you should be connecting to, so that's good. service shows that the process behind it is running, which is good too. my 2nd. ss was a mistake, that should be iptables -L -n | grep 8006 - that should show a line showing that the firewall let's it through.
 
Here are the iptables result

root@pve1:~# iptables -L -n
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
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom