journalctl -b -u proxmox-backup-proxy
? You can pipe it into a file too (using journalctl -b -u proxmox-backup-proxy >proxmox-backup-proxy.log
) and simply attach the file here.Swears that he cannot connect to the datastore, this is an error that cannot affect the web interfaceHi,
the API proxy seems to fail to parse some configuration file, but unfortunately the messages are cut off.
Can you post the (full) output ofjournalctl -b -u proxmox-backup-proxy
? You can pipe it into a file too (usingjournalctl -b -u proxmox-backup-proxy >proxmox-backup-proxy.log
) and simply attach the file here.
Did you change anything in some configuration file before this started happening?
cat /etc/proxmox-backup/datastore.cfg
.datastore: <name>
./etc/proxmox-backup/dadastore.cfg
and change the contents to:datastore: backups
comment
gc-schedule monthly
path /var/backups
Unfortunately it didn't help. web interface is still not available, the error that scolded the datastore is gone, but the problem remainsAs suspected, the datastore configuration is indeed invalid. All datastores must have a name, placed afterdatastore: <name>
.
Thus simply edit/etc/proxmox-backup/dadastore.cfg
and change the contents to:
Code:datastore: backups comment gc-schedule monthly path /var/backups
journalctl -b
)?https://172.16.133.126:8007
exactly? Also, might there be any firewalls/etc. between you and the Proxmox Backup Server host?I suppose the datastore was initially calledAs suspected, the datastore configuration is indeed invalid. All datastores must have a name, placed afterdatastore: <name>
.
Thus simply edit/etc/proxmox-backup/dadastore.cfg
and change the contents to:
Code:datastore: backups comment gc-schedule monthly path /var/backups
PVE_NFS
and not backups
...Yeah, good point.I suppose the datastore was initially calledPVE_NFS
and notbackups
...
PVE_NFS
, as Chris suggested. Also, please try to not edit older posts of yours with more information after someone already answered - that person might not see that afterwards (as in this case ..)