In the 'post-change', my router still cannot find the proxmox server. And the Proxmox server cannot ping to anything. The new url is correct with https

https://192.168.1.98:8006

I tried untagged port 5, but no result.

I manually added the server's mac address vmbr0 & the new IP Address into my router's reservation. There is no other device using the 98 address.

I checked if I had misspell anything, and the only typo was 'wl01' (zero) when it should be 'wlo1' (lowercase O-letter).

However, no result in any of the above methods. How could this proxmox's Linux VLAN suddenly cause the server to be hidden? 

Did the router's tagged VLAN 20 somehow conflicts with the Proxmox's Linux VLAN's vmbr0.98? Does the ID # have to be the same?

Just following along. So you changed to the suggested config and still can't access, but didn't get errors on the ifreload -a command?

That's right. No access, but no error too. 

The suggested config with "ip link show" result: 

Io, status unknown

emp60s0, status up

wl01, status down

vmbr0, status up

vmbr0.98@vmbr0, status up

Also, have you made sure you have your switch tagged upstream where your proxmox host is uplinked?

The switch is tagged correctly (I think).

Untagged Port 1 is between my router & switch.

Tagged port 5 is between the proxmox host & switch.

Are you trying to access the server from the same VLAN or different VLAN? To simplify things and rule out routing, I always start testing on the same VLAN just to establish you have connectivity.

A different vlan, 20. Not using the native. 

These were pretty much the same setting during the 'pre-changes'. 

Btw, does this old line matter:

iface wlo1 inet manual

Also, have you made sure you have your switch tagged upstream where your proxmox host is uplinked? Are you trying to access the server from the same VLAN or different VLAN? To simplify things and rule out routing, I always start testing on the same VLAN just to establish you have connectivity.

Usually when you can't access IPs associated with VLANs, this usually comes down to a tagging problem.

Hello and welcome to the forums! 

Thank you.

One of the first things I would do is look and see what the actual interface names are:

ip link show

This was the result:

Io, status unknown

emp60s0, status down

wl01, status down

vmbr0, status unknown

vmbr0.98@vmbr0, status up

So, if I am following what your original config looked like your correct config might look something like this:

auto lo
iface lo inet loopback

iface enp60s0 inet manual

auto vmbr0
iface vmbr0 inet manual
        bridge-ports enp60s0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

auto vmbr0.98
iface vmbr0.98 inet static
        address 192.168.1.98/24
        gateway 192.168.1.1

source /etc/network/interfaces.d/*

Then you can reload your interfaces

ifreload -a

Pretty much, because I was just following the YT (and a comment). I did experimented, like with the 2nd code I posted earlier on eno1; and updated the "/etc/hosts" with the new 98 IP Address. 

Btw, I cannot access the Proxmox Web GUI anymore (cannot be ping), after the failed Linux VLAN changes. So, now I need to input the cmds directly into the Proxmox machine's terminal. 

ip link show

So, if I am following what your original config looked like your correct config might look something like this:

auto lo
iface lo inet loopback

iface enp60s0 inet manual

auto vmbr0
iface vmbr0 inet manual
        bridge-ports enp60s0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

auto vmbr0.98
iface vmbr0.98 inet static
        address 192.168.1.98/24
        gateway 192.168.1.1

source /etc/network/interfaces.d/*

Then you can reload your interfaces

ifreload -a

Let me know if this helps?

Thanks Dan!

Brandon