[SOLVED] Error: error trying to connect: error connecting to <ip> - TCP connect error: deadline has elapsed

Darkniss

New Member
Mar 22, 2022
6
1
3
We have a cluster of various nodes set up in our workspace, and we are trying to set up a back up server. When I try to back up I get the following error. I already tried setting up a new datastore. Still nothing. Any Ideas?


Code:
INFO: run: lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client backup --crypt-mode=none pct.conf:/var/tmp/vzdumptmp3739656_101/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found --exclude=/tmp/?* --exclude=/var/tmp/?* --exclude=/var/run/?*.pid --backup-type ct --backup-id 101 --backup-time 1647983908 --repository root@pam@192.168.0.101:backups
INFO: Starting backup: ct/101/2022-03-22T21:18:28Z
INFO: Client name: pve-node2
INFO: Starting backup protocol: Tue Mar 22 16:18:28 2022
INFO: Error: error trying to connect: error connecting to https://192.168.0.101:8007/ - tcp connect error: deadline has elapsed
ERROR: Backup of VM 101 failed - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client backup '--crypt-mode=none' pct.conf:/var/tmp/vzdumptmp3739656_101/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' --backup-type ct --backup-id 101 --backup-time 1647983908 --repository root@pam@192.168.0.101:backups' failed: exit code 255
INFO: Failed at 2022-03-22 16:18:39
INFO: Backup job finished with errors
TASK ERROR: job errors


I also noticed when im making a back up job, pbs avail and capacity are at 0. How could I fix that?
1648066676020.png
 
looks like the network to the pbs is not stable?
 
can you connect to 8007 in a timely manner? the error:

says that it runs into a timeout while trying to connect
1648740029089.png
I made some changes adding 8007 to the firewall because I thought maybe the port 8007 was being blocked still nothing. I ran curl -v https://pbs:8007 on one of the nodes in the cluster and I got a SSL certificate problem. Any Ideas?
 
does your firewall anythings special? it must let http2 pass through for the backup api to work
 
does your firewall anythings special? it must let http2 pass through for the backup api to work
To my knowledge, it's not blocking http2, but I did notice that when I was using proxmox my cluster does show it using http/1.1
 
To my knowledge, it's not blocking http2, but I did notice that when I was using proxmox my cluster does show it using http/1.1
the "normal" api uses http/1.1 only the backup/restore api of pbs uses http2
 
If im running proxmox virutal enviorment 6.3.2, and have proxmox back up server 2.0 would that be an issue connecting?
while that should work fine, i still recommend upgrading to at least the latest 6.4 there may be some bug fixes in the backup-client. an upgrade to 7.x would be even better. also note that 6.4 support ends sometime this year
 
while that should work fine, i still recommend upgrading to at least the latest 6.4 there may be some bug fixes in the backup-client. an upgrade to 7.x would be even better. also note that 6.4 support ends sometime this year
I got the issue fixed, The issue was I was connecting the pbs to one of the vlans, so what I did is got an ip from the cluster and applied it to it statically. and I was able to see it on my virtual environment. Thank you for your help!
 
  • Like
Reactions: dcsapak

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!