unable to connect to web GUI fresh install

crash987 · Jul 28, 2021

i have been installing proxmox v6.4 and v7 inside an unraid vm for testing use before deploying to a full metal computer and seem to have problems connecting to the web gui after multiple fresh installs. i have used both the vertio network adapter (in bridge mode) and have passed through a network adapter to still have no success. when going throw the install, this is all i am getting as an option for networking

after looking online on how to install it, a lot of videos are showing an option for IP, netmask, gateway and dns. am i missing something that i can not see or is it that i am missing an option during install. i have spent the last 3 days trying to get it working from all the other help post here with no success.

Thanks for all the help

dcsapak · Jul 29, 2021

the netmask is the '/8' part of the ip address (a /8 is equvalent to a 255.0.0.0 netmask)

what exactly is the problem? can you connect via ssh ? on the console? what does 'ss -tlpn' say after install?

crash987 · Jul 29, 2021

i am able to ping the server and server ping computer. i am able to ssh into the server from the computer. this is what i get from running the command


root@vm:~# ss -tlpn
State     Recv-Q    Send-Q       Local Address:Port        Peer Address:Port    Process
LISTEN    0         4096             127.0.0.1:85               0.0.0.0:*        users:(("pvedaemon worke",pid=876,fd=6),("pvedaemon worke",pid=875,fd=6),("pvedaemon worke",pid=874,fd=6),("pvedaemon",pid=873,fd=6))
LISTEN    0         128                0.0.0.0:22               0.0.0.0:*        users:(("sshd",pid=690,fd=3))
LISTEN    0         100              127.0.0.1:25               0.0.0.0:*        users:(("master",pid=858,fd=13))
LISTEN    0         4096               0.0.0.0:111              0.0.0.0:*        users:(("rpcbind",pid=599,fd=4),("systemd",pid=1,fd=36))
LISTEN    0         128                   [::]:22                  [::]:*        users:(("sshd",pid=690,fd=4))
LISTEN    0         4096                     *:3128                   *:*        users:(("spiceproxy work",pid=914,fd=6),("spiceproxy",pid=913,fd=6))
LISTEN    0         100                  [::1]:25                  [::]:*        users:(("master",pid=858,fd=14))
LISTEN    0         4096                     *:8006                   *:*        users:(("pveproxy worker",pid=910,fd=6),("pveproxy worker",pid=909,fd=6),("pveproxy worker",pid=908,fd=6),("pveproxy",pid=907,fd=6))
LISTEN    0         4096                  [::]:111                 [::]:*        users:(("rpcbind",pid=599,fd=6),("systemd",pid=1,fd=38))

if i try to connect to the server over http i get a "didn’t send any data. ERR_EMPTY_RESPONSE"
if i try to connect to the server over https i get "unexpectedly closed the connection"

crash987 · Jul 31, 2021

So i decided to download an old copy to test out (ve 5.4-1), as per normal installs fine and easy to set up. when i try to visit the gui web page, i get a timeout. i am in the middle of downloading ve 7.0 on a different computer to see if it was just downloaded incorrectly. If the new iso download still has the same problem, it might be how the os is setup and might need to be looked at

leesteken · Jul 31, 2021

HTTP is suposed to do nothing (as there is, correctly, nothing listening on port 80). HTTPS should work (but not on the default 443 port) as you have the correct software listening at the non-default port 8006. Does https://10.1.1.36:8006/ not give any response about an invalid/self-signed certificate? What does curl --insecure https://127.0.0.1:8006/ on the Proxmox host (console or ssh) return?

crash987 · Jul 31, 2021


root@pve:~# curl --insecure https://127.0.0.1:8006/
<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
    <title>pve - Proxmox Virtual Environment</title>
    <link rel="icon" sizes="128x128" href="/pve2/images/logo-128.png" />
    <link rel="apple-touch-icon" sizes="128x128" href="/pve2/images/logo-128.png" />
    <link rel="stylesheet" type="text/css" href="/pve2/ext6/theme-crisp/resources/theme-crisp-all.css" />
    <link rel="stylesheet" type="text/css" href="/pve2/ext6/crisp/resources/charts-all.css" />
    <link rel="stylesheet" type="text/css" href="/pve2/fa/css/font-awesome.css" />
    <link rel="stylesheet" type="text/css" href="/pve2/css/ext6-pve.css?ver=7.0-8" />
    <link rel="stylesheet" type="text/css" href="/pwt/css/ext6-pmx.css?ver=3.2-4" />

    <script type='text/javascript'>function gettext(buf) { return buf; }</script>

    <script type="text/javascript" src="/pve2/ext6/ext-all.js"></script>
    <script type="text/javascript" src="/pve2/ext6/charts.js"></script>

    <script type="text/javascript" src="/pve2/js/u2f-api.js"></script>
    <script type="text/javascript" src="/pve2/js/qrcode.min.js"></script>
    <script type="text/javascript">
    Proxmox = {
        Setup: { auth_cookie_name: 'PVEAuthCookie' },
        defaultLang: 'en',
        UserName: '',
        CSRFPreventionToken: 'null'
    };
    </script>
    <script type="text/javascript" src="/proxmoxlib.js?ver=3.2-4"></script>
    <script type="text/javascript" src="/pve2/js/pvemanagerlib.js?ver=7.0-8"></script>
    <script type="text/javascript" src="/pve2/ext6/locale/locale-en.js"></script>

    <script type="text/javascript">
    if (typeof(PVE) === 'undefined') PVE = {};
    Ext.History.fieldid = 'x-history-field';
    Ext.onReady(function() { Ext.create('PVE.StdWorkspace');});
    </script>

  </head>
  <body>
    <!-- Fields required for history management -->
    <form id="history-form" class="x-hidden">
    <input type="hidden" id="x-history-field"/>
    </form>
  </body>
</html>

from the looks of it, it is hosting the webpage

leesteken · Aug 1, 2021

Good, the web GUI itself is working. What does ip r and ip a on the host report? What is the IP-address and netmask of your client machine that you use to navigate to https://10.1.1.36:8006/?

crash987 · Aug 1, 2021

the client pc is setup as follows
IP: 10.1.1.2
SUBNET MASK: 255.0.0.0

i have also used my tablet to test the connection aswell getting the same problem
IP: 10.1.1.37
SUBNET MASK: 255.0.0.0
DHCP ACCINED


root@pve:~# ip r
default via 10.1.1.1 dev vmbr0 proto kernel onlink
10.0.0.0/8 dev vmbr0 proto kernel scope link src 10.1.1.36


root@pve:~# ip a
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
       valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 52:54:00:23:05:98 brd ff:ff:ff:ff:ff:ff
3: ens1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 74:d4:35:ee:4f:d2 brd ff:ff:ff:ff:ff:ff
    altname enp2s1
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 7e:f6:30:67:85:9a brd ff:ff:ff:ff:ff:ff
    inet 10.1.1.36/8 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::7cf6:30ff:fe67:859a/64 scope link
       valid_lft forever preferred_lft forever

leesteken · Aug 1, 2021

Does curl --insecure https://10.1.1.36:8006/ "work" on any of your VMs connected to vmbr0?
Is vmbr0 (from which the host is reachable) connected to ens1? It should be, since you are able to SSH to 10.1.1.36. What does your /etc/network/interfaces look like?
If https://10.1.1.36:8006/ does not work from you clients, then either they fail because of the self-signed certificate (silently apparently) or a firewall somehwere in between is blocking the connection (possibly silently, which sound much more likely). What do /etc/pve/firewall/cluster.fw and /etc/pve/local/host.fw look like? Can you check your router/firewall at 10.1.1.1?

crash987 · Aug 1, 2021

from my understanding is that vmbr0: is the passthrough ethernet controller and the vm network drive.

i have removed the vm network drive so the only network device that is on the system is the passthrough ethernet device.

there is no VM setup within proxmox as all i can do is install proxmox to a drive and then that's it


root@pve:~# ip a
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
       valid_lft forever preferred_lft forever
2: ens1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 74:d4:35:ee:4f:d2 brd ff:ff:ff:ff:ff:ff
    altname enp2s1
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 7e:f6:30:67:85:9a brd ff:ff:ff:ff:ff:ff
    inet 10.1.1.36/8 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::7cf6:30ff:fe67:859a/64 scope link
       valid_lft forever preferred_lft forever


auto lo
iface lo inet loopback

iface ens1 inet manual

iface enp4s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 10.1.1.36/8
        gateway 10.1.1.1
        bridge-ports ens1
        bridge-stp off
        bridge-fd 0

the firewall files would be system defaults and no changes made to them. the router at 10.1.1.1 has had no system changes to it other then port forwarding for some minecraft servers. i will try and remove the self-signed certificate to see if that might help

leesteken · Aug 1, 2021

The self-signed certificate is on the Proxmox host and is needed for https (http is not supported) and should not be a problem for browsers, only a warning and confirmation dialog. I would advise not to mess with it becasue if you remove it, the https connection will no longer work.
You network configuration looks fine. The only thing I have not seen before on my systems is the altname enp2s1 for ens1.
Sorry to ask this, but just to rule out a mistake that I made myself once: you do include the :8006 when you browse to https://10.1.1.36:8006/?
If you are not getting a response from port 8006 on 10.1.1.36 then that is either a network routing issue (packets are not reaching or not returning) or a firewall issue. What do cat /etc/pve/firewall/cluster.fw and cat /etc/pve/local/host.fw look like?

crash987 · Aug 1, 2021

trying to connect to the server web page, i am making sure it is https and with port 8006. running the commands for the firewall is coming back with "No such file or directory". if i was to run a netstat command i get the following


root@pve:~# netstat -an | grep 8006
tcp6       0      0 :::8006                 :::*                    LISTEN

i might be wrong but is this showing that port 8006 is looking for an IPv6 connection not an IPv4 connection

leesteken · Aug 1, 2021

crash987 said:
trying to connect to the server web page, i am making sure it is https and with port 8006. running the commands for the firewall is coming back with "No such file or directory". if i was to run a netstat command i get the following
root@pve:~# netstat -an | grep 8006 tcp6 0 0 :::8006 :::* LISTEN

i might be wrong but is this showing that port 8006 is looking for an IPv6 connection not an IPv4 connection

It shows the same here, but I am connected using IPv4 (and I use no IPv6 in my local network or at my ISP).

crash987 · Aug 1, 2021

when i get some free time later, i will try installing it on a real pc and see if its just something a virtual install is not setup correctly

crash987 · Aug 2, 2021

so last night i fired up my threadripper system and installed proxmox on a free hdd, to my surprise the system is working. it would be interesting to find out why proxmox can't be installed in a virtual test environment first

leesteken · Aug 2, 2021

Surprised, really? I tend to think that it works for most of its users (including virtualized test setups).
Can you tell us your unRAID version, network configuration and VM configuration on which you ran Proxmox?

crash987 · Aug 2, 2021

my unraid server is running version 6.9.2 on an intel i7 4790K. Network adaptor was using the onboard intel ethernet controller passthrough to the guest VM (controller unavailable to the unraid host to use) also tried using the virtual network adapter both in vertio-net and vertio, network bridge was set to br0 (bridge to onboard network controller (Qualcomm Atheros Killer E220x)). For VM template i used Debian and Ubuntu. The only setting changed was ram and cpu cores. no other under the hood changes (as i have no idea what im changing or going to edit)

Search

Search

unable to connect to web GUI fresh install

crash987

Member

dcsapak

Proxmox Staff Member

crash987

Member

crash987

Member

leesteken

Distinguished Member

crash987

Member

leesteken

Distinguished Member

crash987

Member

leesteken

Distinguished Member

crash987

Member

leesteken

Distinguished Member

crash987

Member

leesteken

Distinguished Member

crash987

Member

crash987

Member

leesteken

Distinguished Member

crash987

Member