No web gui to access

[feroz]

Hello Proxmox members.

i am past 2 hours struggle to open Web gui it not getting open, went through several Proxmox forums but no luck. i am currently connect through SSH,

any suggestion would be appreciated.

--------------------------------------------------------------------------------
root@Risk-Dataenergyaksa:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface eno1 inet manual

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

iface eno2 inet manual


source /etc/network/interfaces.d/*
root@Risk-Dataenergyaksa:~#



------------------------------------------------------------------------------------
root@Risk-Dataenergyaksa:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=115 time=59.7 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=115 time=57.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=115 time=59.9 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=115 time=56.1 ms
^C
------------------------------------------------------------------------------------------
TEST PC
C:\Users\Test>ping 192.168.100.22 -t

Pinging 192.168.100.22 with 32 bytes of data:
Reply from 192.168.100.22: bytes=32 time=1ms TTL=64
Reply from 192.168.100.22: bytes=32 time=1ms TTL=64
Reply from 192.168.100.22: bytes=32 time=1ms TTL=64
Reply from 192.168.100.22: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.100.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
Control-C
-----------------------------------------------------------------------------------------------



root@Risk-Dataenergyaksa:~# systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: ena>
Active: active (running) since Wed 2024-01-03 12:58:19 +03; 17min ago
Process: 1614 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited>
Process: 1616 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCC>
Main PID: 1620 (pveproxy)
Tasks: 3 (limit: 38411)
Memory: 142.1M
CPU: 1min 5.139s
CGroup: /system.slice/pveproxy.service
├─1620 pveproxy
├─2395 "pveproxy worker"
└─2396 "pveproxy worker"

Jan 03 13:15:50 Risk-Dataenergyaksa pveproxy[1620]: starting 1 worker(s)
Jan 03 13:15:50 Risk-Dataenergyaksa pveproxy[1620]: worker 2395 started
Jan 03 13:15:50 Risk-Dataenergyaksa pveproxy[2395]: /etc/pve/local/pve-ssl.key:>
Jan 03 13:15:50 Risk-Dataenergyaksa pveproxy[2393]: worker exit
Jan 03 13:15:50 Risk-Dataenergyaksa pveproxy[2394]: worker exit
Jan 03 13:15:50 Risk-Dataenergyaksa pveproxy[1620]: worker 2393 finished
Jan 03 13:15:50 Risk-Dataenergyaksa pveproxy[1620]: starting 1 worker(s)
Jan 03 13:15:50 Risk-Dataenergyaksa pveproxy[1620]: worker 2394 finished
Jan 03 13:15:50 Risk-Dataenergyaksa pveproxy[1620]: worker 2396 started
lines 1-23...skipping...

 

[cheiss]

Hi,

did you try to connect to port 8006, i.e. https://192.168.100.22:8006?
The web UI (and API, FWIW) runs on port 8006, not on the standard HTTP(S) ports.

If yes, what's the exact error message/code from the web browser? What browser do you use?

 

[feroz]

The connection has timed out

An error occurred during a connection to 192.168.100.22:8006.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.

 

[feroz]

Hi,

did you try to connect to port 8006, i.e. https://192.168.100.22:8006?
The web UI (and API, FWIW) runs on port 8006, not on the standard HTTP(S) ports.

If yes, what's the exact error message/code from the web browser? What browser do you use?

tried three broswer Edge, Firefox and chrome,
also with Https & http

 

[cheiss]

Is there maybe some (corporate-)firewall between the test-machine and the Proxmox VE node, which would block access?
Maybe only to non-standard ports? Unfortunately, this is rather common in some environments.

Can you try running curl -k "https://192.168.100.22:8006" on the test-machine on the commandline and see what that says?
(curl should be pre-installed on any modern Windows AFAIK)

Also please provide the output of pveversion -v, ip a and ip r from the Proxmox VE host, in codetags please!

 

[feroz]

i am currently check on production environment, and yes, there is firewall but it doesn't block any ports, even no deny logs on firewall.

root@Risk-Dataenergyaksa:~# pveversion -v
proxmox-ve: 8.1.0 (running kernel: 6.5.11-4-pve)
pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15)
proxmox-kernel-helper: 8.0.9
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
proxmox-kernel-6.5: 6.5.11-4
ceph-fuse: 17.2.7-pve1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx7
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.4
libpve-rs-perl: 0.8.7
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.0.4-1
proxmox-backup-file-restore: 3.0.4-1
proxmox-kernel-helper: 8.0.9
proxmox-mail-forward: 0.2.2
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.2
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-1
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.1.2
pve-qemu-kvm: 8.1.2-4
pve-xtermjs: 5.3.0-2
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.0-pve3
root@Risk-Dataenergyaksa:~#
root@Risk-Dataenergyaksa:~# pveversion -ip
Unknown option: ip
USAGE: pveversion [--verbose]
root@Risk-Dataenergyaksa:~# pveversion -ip a
Unknown option: ip
USAGE: pveversion [--verbose]
root@Risk-Dataenergyaksa:~#
root@Risk-Dataenergyaksa:~# pveversion -ip r
Unknown option: ip
USAGE: pveversion [--verbose]
root@Risk-Dataenergyaksa:~#


------------------------------------------------------------------------------
C:\Users\Test>curl -k https://192.168.100.22:8006
stuck on finding

 

[feroz]

i even tired direct connection from server to my pc, it doesn't work.
the icmp work fine.

 

[LeoBarreiro]

I have the same problem, it gives me a username and password error in the gui but through ssh I connect perfectly, this happens to me in recently installed proxmox 8.1

 

[feroz]

I have the same problem, it gives me a username and password error in the gui but through ssh I connect perfectly, this happens to me in recently installed proxmox 8.1

but here in my lab, i can't even see the web gui. only have access to Ssh.

 

[bbgeek17]

What is the output of this command "curl -k https://192.168.100.22:8006" when run via SSH directly on proxmox host?

what about:

ip a

ip r

---

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

 

[feroz]

What is the output of this command "curl -k https://192.168.100.22:8006" when run via SSH directly on proxmox host?

what about:

---

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

all those cmd are not working.

root@Risk-Dataenergyaksa:~# pveversion ip a
USAGE: pveversion [--verbose]
root@Risk-Dataenergyaksa:~#
root@Risk-Dataenergyaksa:~#
root@Risk-Dataenergyaksa:~#
root@Risk-Dataenergyaksa:~#
root@Risk-Dataenergyaksa:~# pveversion ip r
USAGE: pveversion [--verbose]
root@Risk-Dataenergyaksa:~#


root@Risk-Dataenergyaksa:~# curl -k https://192.168.100.22:8006

 

[bbgeek17]

all those cmd are not working.

There is no "pveversion" anywhere in my reply. Run the commands as shown , omitting the quotes.

---

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

 

[feroz]

sorry my mistake.

root@Risk-Dataenergyaksa:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul t 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 mq master vmbr0 state UP group default qlen 1000
link/ether 78:2b:cb:3d:77:61 brd ff:ff:ff:ff:ff:ff
altname enp1s0f0
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 78:2b:cb:3d:77:62 brd ff:ff:ff:ff:ff:ff
altname enp1s0f1
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP grou p default qlen 1000
link/ether 78:2b:cb:3d:77:61 brd ff:ff:ff:ff:ff:ff
inet 192.168.100.22/22 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::7a2b:cbff:fe3d:7761/64 scope link
valid_lft forever preferred_lft forever
root@Risk-Dataenergyaksa:~#
root@Risk-Dataenergyaksa:~#
root@Risk-Dataenergyaksa:~#
root@Risk-Dataenergyaksa:~# ip r
default via 192.168.100.1 dev vmbr0 proto kernel onlink
192.168.100.0/22 dev vmbr0 proto kernel scope link src 192.168.100.22
root@Risk-Dataenergyaksa:~#
root@Risk-Dataenergyaksa:~#

 

[bbgeek17]

What happens when you run from PVE host: curl -sk https://localhost:8006

Please use CODE tags when posting output. The option to do so is located in the menu bar of the reply with </> icon.

Examine "journalctl -n 100" for any errors.

Are you certain that you have /22 mask on the network?

---

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

 

[feroz]

What happens when you run from PVE host: curl -sk https://localhost:8006

it doen't show anything

Please use CODE tags when posting output. The option to do so is located in the menu bar of the reply with </> icon.

Examine "journalctl -n 100" for any errors.

Are you certain that you have /22 mask on the network?

---

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

i am use to the form,i will correct from next post, and yes i have subnet /22

 

[bbgeek17]

Open two ssh terminals.
In the first one run: journalctl -f
In the second: systemctl try-reload-or-restart pvedaemon pveproxy pvestatd pvescheduler
Second: netstat -na |grep 8006
Second: curl -sk https://localhost:8006

Report the results, and if netstat and curl fail, then the output of the first one wrapped in code or spoiler tags.

---

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

 

[Dunuin]

Is 192.168.100.0/24 actually your subnet your clients are using and 192.168.100.1 the IP you use to access your routers webUI?

Because usualky when people use that default subnet they forgot to change it to the existing network infrastructure.

 

[news]

Hello,
i installed yesterday Proxmox 8.1 new, make all Updates and have no bind on IPv4 Port 8006. IPv6 Port 8006 was there. And many problems with the bootloader over grup, efi boot.

 

[bbgeek17]

i installed yesterday Proxmox 8.1 new, make all Updates and have no bind on IPv4 Port 8006. IPv6 Port 8006 was there.

Next time please open your own thread, as your question is not related to Ops issue:
Google search query : why am i seeing a bind on ipv6 but not ipv4 netstat
https://unix.stackexchange.com/questions/237731/why-are-ipv4-tcp-connections-showing-as-tcp6

---

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

 

[news]

Next time please open your own thread, as your question is not related to Ops issue:
Google search query : why am i seeing a bind on ipv6 but not ipv4 netstat
https://unix.stackexchange.com/questions/237731/why-are-ipv4-tcp-connections-showing-as-tcp6

---

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

No, i don't need help. Its only a new information about the problems with the current Proxmox 8.1 installer.