Can't access to web interface or SSH after fresh install

xjvrz

New Member
Oct 22, 2025
13
0
1
Hello everyone,
I m totally new to proxmox and i m having trouble triying to access to the web interface or connecting via SSH. (I think it should be some router or firewall issue).
Here you have the displays of some comands.


Also:

Ping google.com OK
Ping another computer in network OK
Ping pve from another computer OK


Thx in advance.
 

Attachments

  • cap.png
    cap.png
    978.1 KB · Views: 17
Welcome to the Forum!
We don't know what is the IP address of your workstation. It's difficult to help you without it.

BTW, it's better to send information in textual form, not photos.
As you have the physical access to the host, you can copy the output of the commands to a text file, then insert some USB stick, mount it and copy the file to the stick.
 
curl -k localhost:8006 should be curl -k https://localhost:8006 The HTTPS is rather important as HTTP does not work and port 8006 does not have a default protocol.
Maybe 192.168.1.49 is inside the DHCP-range of your router and, since Proxmox does not use DHCP (except for the installer), it blocks the traffic? This is not that uncommon.
 
Welcome to the Forum!
We don't know what is the IP address of your workstation. It's difficult to help you without it.

BTW, it's better to send information in textual form, not photos.
As you have the physical access to the host, you can copy the output of the commands to a text file, then insert some USB stick, mount it and copy the file to the stick.
Hey thanks a lot for the tip!
The IP of the proxmox server is 192.168.1.49 and the router is 192.168.1.1.
Here are the outputs:

Code:
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 noprefixroute
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UP group default qlen 1000
    link/ether c4:34:6b:64:da:61 brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    altname enxc4346b64da61
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether c4:34:6b:64:da:61 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.49/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::c634:6bff:fe64:da61/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever

Code:
cat /etc/network/interfaces

auto lo
iface lo inet loopback

iface eno1 inet manual

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


source /etc/network/interfaces.d/*

Code:
cat /etc/hosts

127.0.0.1 localhost.localdomain localhost
192.168.1.49 pve.serverProx pve

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
 
curl -k localhost:8006 should be curl -k https://localhost:8006 The HTTPS is rather important as HTTP does not work and port 8006 does not have a default protocol.
Maybe 192.168.1.49 is inside the DHCP-range of your router and, since Proxmox does not use DHCP (except for the installer), it blocks the traffic? This is not that uncommon.
Hi!

Yeah the DHCP range of my router goes from 192.168.1.1 to 192.168.1.150.
¿Should i assign an IP out of the DHCP range (Like 192.168.1.151) to the server?
 
Yeah the DHCP range of my router goes from 192.168.1.1 to 192.168.1.150.
¿Should i assign an IP out of the DHCP range (Like 192.168.1.151) to the server?
Yes of course! Otherwise you might get a duplicate IP address on your local network. Also change /etc/hosts accordingly.
 
Buuut, it is pingleable but still no access.
You can also use nmap -p1-8006 <ip> to list open ports.

Is the issue that the web interface is not running at all (i.e. curl -v -k https://localhost:8006 fails on the server) or just that you can't reach it from your workstation?
 
You can also use nmap -p1-8006 <ip> to list open ports.

Is the issue that the web interface is not running at all (i.e. curl -v -k https://localhost:8006 fails on the server) or just that you can't reach it from your workstation?
Hi!

The issue is that i cant reach it from my workstation, i also tried proxmox mobile app to access.

Code:
nmap -p1-8006 <ip>

Starting Nmap 7.95 ( https://nmap.org ) at 2025-10-23 17:01 CEST
Nmap scan report for pve.serverProx (192.168.1.151)
Host is up (0.0000030s latency).
Not shown: 8002 closed tcp ports (reset)
PORT     STATE SERVICE
22/tcp   open  ssh
111/tcp  open  rpcbind
3128/tcp open  squid-http
8006/tcp open  wpl-analytics

Nmap done: 1 IP address (1 host up) scanned in 0.14 seconds

Code:
CURL ->

<!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?ver=7.0.0" />
    <link rel="stylesheet" type="text/css" href="/pve2/ext6/crisp/resources/charts-all.css?ver=7.0.0" />
    <link rel="stylesheet" type="text/css" href="/pve2/fa/css/font-awesome.css" />
    <link rel="stylesheet" type="text/css" href="/pve2/font-logos/css/font-logos.css" />
    <link rel="stylesheet" type="text/css" href="/pve2/css/ext6-pve.css?ver=9.0.3" />
    <link rel="stylesheet" type="text/css" href="/pwt/css/ext6-pmx.css?ver=v5.0.4-t1754316706" />
    <link rel="stylesheet" type="text/css" media="(prefers-color-scheme: dark)" href="/pwt/themes/theme-proxmox-dark.css?ver=v5.0.4-t1754316706" />
    
    <script type='text/javascript'>
        function gettext(message) { return message; }
        function ngettext(singular, plural, count) { return count === 1 ? singular : plural; }
    </script>
    
    <script type="text/javascript" src="/pve2/ext6/ext-all.js?ver=7.0.0"></script>
    <script type="text/javascript" src="/pve2/ext6/charts.js?ver=7.0.0"></script>
    
    <script type="text/javascript" src="/pve2/js/u2f-api.js"></script>
    <script type="text/javascript" src="/qrcode.min.js"></script>
    <script type="text/javascript">
    Proxmox = {
        Setup: { auth_cookie_name: 'PVEAuthCookie' },
        defaultLang: 'en',
        NodeName: 'pve',
        UserName: '',
        CSRFPreventionToken: 'null',
        ConsentText: ''
    };
    </script>
    <script type="text/javascript" src="/proxmoxlib.js?ver=v5.0.4-t1754316706"></script>
    <script type="text/javascript" src="/pve2/js/pvemanagerlib.js?ver=9.0.3"></script>
    <script type="text/javascript" src="/pve2/ext6/locale/locale-en.js?ver=7.0.0"></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>
 
In the PVE please install "tcpdump" package ( apt-get update ; apt-get install tcpdump ) (unless it's already installed - I don't remember).
Check what your workstation's IP address is (may have changed in the meantime because of DHCP).
Then execute tcpdump -n -i any host ip.address.of.workstation (and don't Ctrl-c until the end of the experiment from the workstation).
Ping for a few seconds from the workstation to the PVE. You should see ICMP traffic in tcpdump output.

Try to connect to the PVE using ssh. Is there any output of tcpdump?
Try to connect to the PVE's web interface. Is there any output of tcpdump?
If not, something in the network doesn't let your connections to the PVE and we will try to pinpoint it later.

Edit: or something doesn't let the packets returning to the workstation...
Edit 2: added -n in tcpdump command.
 
Last edited:
In the PVE please install "tcpdump" package ( apt-get update ; apt-get install tcpdump ) (unless it's already installed - I don't remember).
Check what your workstation's IP address is (may have changed in the meantime because of DHCP).
Then execute tcpdump -n -i any host ip.address.of.workstation (and don't Ctrl-c until the end of the experiment from the workstation).
Ping for a few seconds from the workstation to the PVE. You should see ICMP traffic in tcpdump output.

Try to connect to the PVE using ssh. Is there any output of tcpdump?
Try to connect to the PVE's web interface. Is there any output of tcpdump?
If not, something in the network doesn't let your connections to the PVE and we will try to pinpoint it later.

Edit: or something doesn't let the packets returning to the workstation...
Edit 2: added -n in tcpdump command.
Yeah, i got ouputs triying to connect via SSH or Web:

Code:
22:18:15.874019 eno1  In  IP 192.168.1.20.51066 > 192.168.1.151.22: Flags [P.], seq 4170255141:4170256573, ack 997982235, win 255, length 1432
22:18:15.874025 vmbr0 In  IP 192.168.1.20.51066 > 192.168.1.151.22: Flags [P.], seq 0:1432, ack 1, win 255, length 1432
22:18:15.874047 vmbr0 Out IP 192.168.1.151.22 > 192.168.1.20.51066: Flags [R], seq 997982235, win 0, length 0
22:18:15.874051 eno1  Out IP 192.168.1.151.22 > 192.168.1.20.51066: Flags [R], seq 997982235, win 0, length 0
22:18:21.020029 vmbr0 Out ARP, Request who-has 192.168.1.20 tell 192.168.1.151, length 28
22:18:21.020037 eno1  Out ARP, Request who-has 192.168.1.20 tell 192.168.1.151, length 28
22:18:21.076889 eno1  In  ARP, Reply 192.168.1.20 is-at b8:1e:a4:f0:fd:49, length 46
22:18:21.076894 vmbr0 In  ARP, Reply 192.168.1.20 is-at b8:1e:a4:f0:fd:49, length 46
22:18:22.037784 eno1  In  ARP, Request who-has 192.168.1.151 (c4:34:6b:64:da:61) tell 192.168.1.20, length 46
22:18:22.037790 vmbr0 In  ARP, Request who-has 192.168.1.151 (c4:34:6b:64:da:61) tell 192.168.1.20, length 46
22:18:22.037798 vmbr0 Out ARP, Reply 192.168.1.151 is-at c4:34:6b:64:da:61, length 28
22:18:22.037801 eno1  Out ARP, Reply 192.168.1.151 is-at c4:34:6b:64:da:61, length 28

22:18:55.206706 eno1  In  IP 192.168.1.20.52902 > 192.168.1.151.8006: Flags [.], ack 2035807393, win 255, length 0
22:18:55.206712 vmbr0 In  IP 192.168.1.20.52902 > 192.168.1.151.8006: Flags [.], ack 1, win 255, length 0
22:18:55.206734 vmbr0 Out IP 192.168.1.151.8006 > 192.168.1.20.52902: Flags [R], seq 2035807393, win 0, length 0
22:18:55.206738 eno1  Out IP 192.168.1.151.8006 > 192.168.1.20.52902: Flags [R], seq 2035807393, win 0, length 0
22:18:55.206743 eno1  In  IP 192.168.1.20.62407 > 192.168.1.151.8006: Flags [.], ack 207313155, win 255, length 0
22:18:55.206743 vmbr0 In  IP 192.168.1.20.62407 > 192.168.1.151.8006: Flags [.], ack 1, win 255, length 0
22:18:55.206746 vmbr0 Out IP 192.168.1.151.8006 > 192.168.1.20.62407: Flags [R], seq 207313155, win 0, length 0
22:18:55.206747 eno1  Out IP 192.168.1.151.8006 > 192.168.1.20.62407: Flags [R], seq 207313155, win 0, length 0
22:19:00.444022 vmbr0 Out ARP, Request who-has 192.168.1.20 tell 192.168.1.151, length 28
22:19:00.444030 eno1  Out ARP, Request who-has 192.168.1.20 tell 192.168.1.151, length 28
22:19:00.498828 eno1  In  ARP, Reply 192.168.1.20 is-at b8:1e:a4:f0:fd:49, length 46
22:19:00.498834 vmbr0 In  ARP, Reply 192.168.1.20 is-at b8:1e:a4:f0:fd:49, length 46
 
22:19:26.313873 eno1  In  IP 192.168.1.20.57841 > 192.168.1.151.8006: Flags [.], ack 3069751237, win 255, length 0
22:19:26.313878 vmbr0 In  IP 192.168.1.20.57841 > 192.168.1.151.8006: Flags [.], ack 1, win 255, length 0
22:19:26.313899 vmbr0 Out IP 192.168.1.151.8006 > 192.168.1.20.57841: Flags [R], seq 3069751237, win 0, length 0
22:19:26.313903 eno1  Out IP 192.168.1.151.8006 > 192.168.1.20.57841: Flags [R], seq 3069751237, win 0, length 0
22:19:26.313964 eno1  In  IP 192.168.1.20.58077 > 192.168.1.151.8006: Flags [.], ack 389731784, win 255, length 0
22:19:26.313966 vmbr0 In  IP 192.168.1.20.58077 > 192.168.1.151.8006: Flags [.], ack 1, win 255, length 0
22:19:26.313970 vmbr0 Out IP 192.168.1.151.8006 > 192.168.1.20.58077: Flags [R], seq 389731784, win 0, length 0
22:19:26.313972 eno1  Out IP 192.168.1.151.8006 > 192.168.1.20.58077: Flags [R], seq 389731784, win 0, length 0
22:19:31.676021 vmbr0 Out ARP, Request who-has 192.168.1.20 tell 192.168.1.151, length 28
22:19:31.676029 eno1  Out ARP, Request who-has 192.168.1.20 tell 192.168.1.151, length 28
22:19:31.683320 eno1  In  ARP, Reply 192.168.1.20 is-at b8:1e:a4:f0:fd:49, length 46
22:19:31.683326 vmbr0 In  ARP, Reply 192.168.1.20 is-at b8:1e:a4:f0:fd:49, length 46

Also checking my router firewall config tab i saw that it is currently in medium mode ->

"The firewall blocks all incoming connections. Outgoing traffic is allowed except for Netbios services. This is the recommended mode."

I tried to add a NAT/PAT rule to it but i dont know if it is well configured ->

Application / service -> Internal port -> external port -> protocol (TCP and UDP) -> IPv4​

1761252026902.png

And really thanks for your time <3.
 

Attachments

  • 1761251198428.png
    1761251198428.png
    6.1 KB · Views: 7
Last edited:
Hi,

Could you check that your workstation mac is "b8:1e:a4:f0:fd:49" ?

Also post screen of the error you get when connecting.

Best regards,
 
Hi,

Could you check that your workstation mac is "b8:1e:a4:f0:fd:49" ?

Also post screen of the error you get when connecting.

Best regards,
Hello!

Yeah MAC addres on workstation is b8:1e:a4:f0:fd:49.

The errors are time outs :

Code:
ssh root@192.168.1.151
ssh_dispatch_run_fatal: Connection to 192.168.1.151 port 22: Connection timed out

Web -> https://192.168.1.151:8006/

1761290477332.png
 
If the netmasks in the devices are proper and both the workstation an the PVE are in the same network (in the IP addressing meaning), then theoretically there should be no _router_ between them.
Anyway, seems that something (a firewall?) blocks the traffic. Most likely the returning traffic.

To narrow searching, I would (temporarily) set a static address in the workstation and connect the workstation directly to the PVE host with one cable (no devices between them). And check if it works then.
 
If the netmasks in the devices are proper and both the workstation an the PVE are in the same network (in the IP addressing meaning), then theoretically there should be no _router_ between them.
Anyway, seems that something (a firewall?) blocks the traffic. Most likely the returning traffic.

To narrow searching, I would (temporarily) set a static address in the workstation and connect the workstation directly to the PVE host with one cable (no devices between them). And check if it works then.
By one cable u are referring to an eth cable no?

So then it will be ->

Workstation (Windows 11 with Static IP and Connected via wifi to router) to -> Poxmox server (Only 1 eth port, actually connected to the router, so we should change it to the Workstation)

Am I missing something?
 
Hi,

What is the complete IP configuration of your workstation ?

Have you tried with your workstation connected with ethernet ?

Best regards,
 
By one cable u are referring to an eth cable no?
Yes.
So then it will be ->

Workstation (Windows 11 with Static IP and Connected via wifi to router) to -> Poxmox server (Only 1 eth port, actually connected to the router, so we should change it to the Workstation)
No :-). Disconnect WiFi in the PC.
Start from the most simple setup. No WiFi, no router, no switch. Only:
PC ------- ethernet_cable -------- PVE
 
  • Like
Reactions: xjvrz