Getting crazy!! fetching datastores - 500 Can't connect to

encrypted_

New Member
Oct 30, 2023
12
0
1
I have two PBS instances running on cloud servers / docker and acessible within my tailnet.

The image im using is this: ayufan/proxmox-backup-server:latest

Both were working flawlessly for months but now, one of them just stopped working with the following error:

fetching datastores - 500 Can't connect to SERVER IP

What I already tried:
  • Clean install of PBS twice
  • Changing IP of PBS instance
  • Pinging PBS instance (ok)
  • Web access of PBS instance (ok)
  • Creating new Datastore
  • proxmox-backup-client list --repository "admin@pbs@ip:datastore"
    Error: permission check failed.


Don't know what else to do.
 
Hi!
does the admin user exist? If not, use root@pam. Also those are two different errors, the first implies that your SERVER IP is not reachable, the second is a permission error.
 
it's getting even more weird

in the UI, when trying to add the PBS, I get the following:
error fetching datastores - 500 Can't connect to 100.100.100.1:8007 (500)

but retrying the command above in the shell, I was able to get the repository contents

root@macan:~# proxmox-backup-client list --repository admin@pbs@ 100.100.100.1:macan
┌────────┬─────────────────────────────┬──────────────┬────────────────────────────────────────────────────────┐
│ group │ last snapshot │ backup-count │ files │
╞════════╪═════════════════════════════╪══════════════╪════════════════════════════════════════════════════════╡
│ ct/100 │ ct/100/2024-10-20T10:12:19Z │ 1 │ catalog.pcat1 client.log index.json pct.conf root.pxar │
├────────┼─────────────────────────────┼──────────────┼────────────────────────────────────────────────────────┤
│ ct/102 │ ct/102/2024-10-20T11:34:02Z │ 1 │ catalog.pcat1 client.log index.json pct.conf root.pxar │
├────────┼─────────────────────────────┼──────────────┼────────────────────────────────────────────────────────┤
│ ct/103 │ ct/103/2024-10-20T11:51:05Z │ 1 │ catalog.pcat1 client.log index.json pct.conf root.pxar │
├────────┼─────────────────────────────┼──────────────┼────────────────────────────────────────────────────────┤
│ ct/104 │ ct/104/2024-10-20T11:52:01Z │ 1 │ catalog.pcat1 client.log index.json pct.conf root.pxar │
├────────┼─────────────────────────────┼──────────────┼────────────────────────────────────────────────────────┤
│ ct/107 │ ct/107/2024-10-20T12:05:48Z │ 1 │ catalog.pcat1 client.log index.json pct.conf root.pxar │
├────────┼─────────────────────────────┼──────────────┼────────────────────────────────────────────────────────┤
│ vm/101 │ vm/101/2024-10-20T10:13:54Z │ 1 │ client.log drive-sata0.img index.json qemu-server.conf │
├────────┼─────────────────────────────┼──────────────┼────────────────────────────────────────────────────────┤
│ vm/105 │ vm/105/2024-10-20T11:53:53Z │ 1 │ client.log drive-scsi0.img index.json qemu-server.conf │
 
It seems like the tcp connection cannot be established... What does your network between client and server look like (If you have any firewall check the rules as well)? You can try running tcpdump (tcpdump -vvi any) on both sides while running the command and check if something weird happens.
 
I'm using Tailscale in a docker LXC and I have a route mapping all the Tailnet to the LXC container. Besides this situation, every other host works flawlessly.
 

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!