Can't Connect to Proxmox Webinterface After Reboot

aptiger

New Member
Dec 3, 2024
2
0
1
Hi all, I've searched around and found this is somewhat of a common issue, but of the various threads here and else where, and trying vaious solutions, I still can't get connected.

I can't ping it from any computer on my netowrk. I CAN ping it from my router.

I'm pretty new at this. I'm sorry if I overlooked something! Here are my outputs. Any help is appreciated!

https://192.168.140.215:8006/

IP A
Code:
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: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether cc:28:40:46:2b:c2 brd ff:ff:ff:ff:ff:ff
3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 94:bb:a3:41:fc:e0 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 cc:28:40:46:2b:c2 brd ff:ff:ff:ff:ff:ff
    inet 192.168.140.215/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::ce28:40ff:fe46:2bc2/64 scope link
       valid_lft forever preferred_lft forever

/etc/network/interfaces

Code:
auto lo
iface lo inet loopback

iface enp4s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.140.215/24
        netmask 255.255.255.0
        gateway 192.168.140.1
        bridge-ports enp4s0
        bridge-stp off
        bridge-fd 0
        
iface wlo1

source /etc/network/interfaces.d/*

/etc/host

Code:
127.0.0.1 localhost.localdomain localhost
192.168.140.215 pve.example.com pve
 
Replying here for anyone else possibly facing this issue.

I left out some crucial info, which I'm not sure why I didn't think to mention it in the first place.

Anyhow, I had recently installed Tailscale in a container advertising subnet routes and being used as an exit node.

So if you did that, and are having trouble connecting to your proxmox server's GUI after a reboot, it's possible your new tailscale container is not running!

I had to have access to the physical machine. Login as root.

Type "pct list" to get your list of containers ("qm list" lists VMs) - This lists your containers IDs, Status, and Name.

Type "pct start VMID" (eg. pct start 101) - This still start the container. You should now be able to connect to the WebGUI.

Once you're in, please select your container -> Options -> enable start at boot.
 

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!

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!