[SOLVED] Proxmox Backup Server installed on Proxmox VE timeout to connect to GUI port 8007

[ABaum]

Hello to all and sundry.
I am baffled by a new issue i don't understand.
I installed Proxmox VE then installed PBS via

# apt install proxmox-backup-server

I can connect to the GUI at 8006 but get a timeout at 8007

the systemctl status shows green and no error messages.
command line tools work

am I missing something?

 

[Chris]

Hi,
what is the status of systemctl status proxmox-backup.service proxmox-backup-proxy.service? Please also verify that the service is listening on port 8007 via e.g. ss -tlpen.

Further, note that since you did a co-installation of Proxmox VE and Proxmox Backup Server, the firewall of Proxmox VE might interfere with traffic to the PBS. Check it is disabled or has the necessary rules configured.
In general it is not recommended to have the PBS installed alongside PVE, as you have a single point of failure and might run into issue, e.g. when performing upgrades.

 

[ABaum]

Hello Chris
Command output requested is attached to this message.

Yes I know this parallel install is not recommended.
My plan is to pull sync to a baremetal install PBS over WAN to offsite and not have GB of traffic every night to backup my LXC containers. this brings me to 3-1-1 backup strategy beings I use only disks. But on local I want to use running copy on NMVe and backup to zfs pool. My backup box offsite at my house does have a tape drive so I can implement 3-2-1 with that then.

I do pay subscription either on PV or PBS on each machine.

Anyway how can we get 8007 to respond?

andrew@andrew-OptiPlex-990:~$ nc -v 192.168.0.3 8007
^C
andrew@andrew-OptiPlex-990:~$ nc -v 192.168.0.3 8006
Connection to 192.168.0.3 8006 port [tcp/*] succeeded!
^C
andrew@andrew-OptiPlex-990:~$ nc -v 192.168.0.3 8007
^C
andrew@andrew-OptiPlex-990:~$ nc -v 192.168.0.3 8006
Connection to 192.168.0.3 8006 port [tcp/*] succeeded!
^C 
andrew@andrew-OptiPlex-990:~$

 

[ABaum]

Hi,
what is the status of systemctl status proxmox-backup.service proxmox-backup-proxy.service? Please also verify that the service is listening on port 8007 via e.g. ss -tlpen.

Further, note that since you did a co-installation of Proxmox VE and Proxmox Backup Server, the firewall of Proxmox VE might interfere with traffic to the PBS. Check it is disabled or has the necessary rules configured.
In general it is not recommended to have the PBS installed alongside PVE, as you have a single point of failure and might run into issue, e.g. when performing upgrades.

the firewall in PVE is empty and strictly left as installed.

 

[ABaum]

the firewall in PVE is empty and strictly left as installed.

And the default firewall was the problem because PVE was joined to a cluster, (I setup a different box that did not need special rules however that one was not joined to a cluster and the backup was installed then PVE added. This one was the other way around.)
Is this rule appropiate? it did allow the connection.

 

[Chris]

And the default firewall was the problem because PVE was joined to a cluster
Is this rule appropiate? it did allow the connection.

View attachment 69656

There is no default rule for allowing traffic to PBS for the PVE firewall (since already mentioned that this is not a supported setup). So yes, you will have to add a rule which explicitly allows traffic to the PBS.

Above would allow all incomming tcp traffic on interface vmbr0 destined for port 8007 to pass, so vaild in your context.

 

[ABaum]

There is no default rule for allowing traffic to PBS for the PVE firewall (since already mentioned that this is not a supported setup). So yes, you will have to add a rule which explicitly allows traffic to the PBS.

Above would allow all incomming tcp traffic on interface vmbr0 destined for port 8007 to pass, so vaild in your context.

Thank you for your time.

 

[Chris]

Thank you for your time.

No worries, please mark the thread as solved for others to find a solution more easily, thanks.

 

[SamTzu]

Same here. FW had a link to old alias that no longer existed.
This was logged and gave an error but I did not link it to the problem at first.