Using different port than 8007

Dec 2, 2018
9
0
41
49
We use: Backup Server version: 3.4.0

Our infrastructure is behind a reverse proxy, and I want to use the "pull" function from a remote data center.
If I add the server to the remotes as backup.example.com:443, The sync starts, but I get the following error:

sync group vm/6000 failed - error trying to connect: error connecting to https://backup.example.com:443/ - DNS error: failed to look up address information: Name or service not known: error connecting to https://backup.example.com:443/ - DNS error: failed to look up address information.

What am I doing wrong?
 
In a strange way, there isn’t always an error. The synchronization works, it just throws an error sometimes. Of course, in the end, it still calls the whole thing faulty.

2025-04-17T22:49:34+02:00: got backup log file client.log.blob
2025-04-17T22:49:34+02:00: sync snapshot vm/3000/2025-02-22T01:00:03Z done
2025-04-17T22:49:34+02:00: percentage done: 54.22% (9/18 groups, 19/25 snapshots in group #10)
2025-04-17T22:49:34+02:00: sync snapshot vm/3000/2025-03-01T01:00:03Z
2025-04-17T22:49:34+02:00: sync archive qemu-server.conf.blob
2025-04-17T22:49:34+02:00: sync archive drive-virtio1.img.fidx
2025-04-17T22:49:59+02:00: downloaded 439.318 MiB (17.791 MiB/s)
2025-04-17T22:49:59+02:00: sync archive drive-virtio0.img.fidx
2025-04-17T22:50:01+02:00: downloaded 31.143 MiB (13.305 MiB/s)
2025-04-17T22:50:01+02:00: got backup log file client.log.blob
2025-04-17T22:50:01+02:00: sync snapshot vm/3000/2025-03-01T01:00:03Z done
2025-04-17T22:50:01+02:00: percentage done: 54.44% (9/18 groups, 20/25 snapshots in group #10)
2025-04-17T22:50:01+02:00: sync snapshot vm/3000/2025-03-08T01:00:03Z
2025-04-17T22:50:01+02:00: sync archive qemu-server.conf.blob
2025-04-17T22:50:01+02:00: sync archive drive-virtio1.img.fidx
2025-04-17T22:51:36+02:00: downloaded 1.71 GiB (18.483 MiB/s)
2025-04-17T22:51:36+02:00: sync archive drive-virtio0.img.fidx
2025-04-17T22:51:38+02:00: downloaded 28.38 MiB (18.675 MiB/s)
2025-04-17T22:51:38+02:00: got backup log file client.log.blob
2025-04-17T22:51:38+02:00: sync snapshot vm/3000/2025-03-08T01:00:03Z done
2025-04-17T22:51:38+02:00: percentage done: 54.67% (9/18 groups, 21/25 snapshots in group #10)
2025-04-17T22:51:38+02:00: sync group vm/3000 failed - error trying to connect: error connecting to https://backup.example.com:443/ - dns error: failed to lookup address information: Name or service not known: error connecting to https://backup.example.com:443/ - dns error: failed to lookup address information: Name or service not known
2025-04-17T22:51:38+02:00: sync snapshot vm/3010/2024-08-31T20:00:02Z
2025-04-17T22:51:38+02:00: sync archive qemu-server.conf.blob
2025-04-17T22:51:38+02:00: sync archive drive-virtio0.img.fidx
2025-04-17T22:52:34+02:00: downloaded 1.012 GiB (18.624 MiB/s)
2025-04-17T22:52:34+02:00: got backup log file client.log.blob
2025-04-17T22:52:34+02:00: sync snapshot vm/3010/2024-08-31T20:00:02Z done
2025-04-17T22:52:34+02:00: percentage done: 55.65% (10/18 groups, 1/61 snapshots in group #11)
2025-04-17T22:52:34+02:00: sync snapshot vm/3010/2024-09-30T20:00:03Z
2025-04-17T22:52:34+02:00: sync archive qemu-server.conf.blob
2025-04-17T22:52:34+02:00: sync archive drive-virtio0.img.fidx
2025-04-17T22:52:58+02:00: downloaded 422.122 MiB (18.161 MiB/s)
2025-04-17T22:52:58+02:00: got backup log file client.log.blob
2025-04-17T22:52:58+02:00: sync snapshot vm/3010/2024-09-30T20:00:03Z done
2025-04-17T22:52:58+02:00: percentage done: 55.74% (10/18 groups, 2/61 snapshots in group #11)
2025-04-17T22:52:58+02:00: sync snapshot vm/3010/2024-10-31T21:00:03Z
2025-04-17T22:52:58+02:00: sync archive qemu-server.conf.blob
2025-04-17T22:52:58+02:00: sync archive drive-virtio0.img.fidx
2025-04-17T22:53:18+02:00: downloaded 373.136 MiB (18.843 MiB/s)
 
And i my other(!) syinc from a "Backup Server 3.3.4" also not works with some groups(?) error. Unfortunetly i did not save the error logs. But after i upgraded the remote server from Backup Server 3.3.4 to Backup Server 3.4.1, the sync is working well.
 
that sounds like your DNS is flaky..
 
Check the output of cat /etc/proxmox-backup/remote.cfg. The host should be listed as backup.example.com, the port 443. If that is not listed correctly please adapt accordingly. The http client used for pulling is created based on these config settings.

How did you set up the remote? Via the WebUI or by editing the config directly?

Edit: Anyways, since this is an intermitten issue, how did you verify that the PBS wants to resolve backup.example.com:443?
 
Last edited:
No, the DNS is OK. I tested it. It's look like server want to check in the DNS the "backup.example.com:443" not just "backup.example.com"
if it works, then doesn't with a DNS resolution error, then works again - it can only be your DNS server or resolver messing up, as the clients for all those connections are created in the exact same fashion.