Search results

Although installing PVE using the PVE ISO is usually preferred. Using a non-preferred installation method just to avoid having to spend a few minutes clicking 'Next' in the PVE installer is probably not a great idea.

How is that possible? Do you not have any backups on another machine than your Proxmox machine?

Can you actually use the storage on those nodes? Or is it just pvestatd complaining?

I would use IPv6 :p (and probably not a VPN tunnel for cluster communication...).

This is probably better suited for the "Proxmox VE: Networking and Firewall" forum.

Unless you can only reproduce this issue on a VM running on Proxmox VE, I think it would make more sense to ask this question on NextCloud's GitHub.

Proxmox VE is pretty stateless when it comes to node-specific configurations. I think you'd be better off implementing configuration management.

That doesn't sound like a Proxmox issue.

I think the pricing page at https://proxmox.com/en/proxmox-ve/pricing answers your question pretty well: In other words: yes, not having a subscription for testing is fine, because you don't need reliable software updates and security enhancements in that case. You may need technical help and...

PVE Admin Guide, chapter 5.9 No. Note that systems like Ansible don't remove keys if they don't explicitly have the 'absent' state. Also, you can add a file to OpenSSH's 'AuthorizedKeysFile' and do key management as usual there.

If you let your watchdog handle events for all files in that directory, do you see temporary files? I think there's some cases where cp'd files aren't picked up.

Ack all that. My point is: I think it's confusing for 'the average user'.

I understand, and while that is technically true, I think the message is confusing from a practical standpoint :). See here the first question about this message: https://forum.proxmox.com/threads/first-backup-of-pve-vm.82871/#post-364565

When creating a backup of a VM not previously backed up to PBS, 'backup was done incrementally' is almost always shown: INFO: backup is sparse: 2.83 GiB (1%) total zero data INFO: backup was done incrementally, reused 4.91 GiB (2%) I take it 'incremental' means space was 'reused' as the backup...

Node A thought node B was master. Node B thought node B was master. Node C thought node C was master...

Yes, just fixed the clustering situation. 'Use SPF' is now disabled on all nodes, and works as expected. Thank you!

Looks like /etc/pmg/pmg.conf is out of sync on one cluster node (which happens to be the one I'm testing on), indeed... Not an issue for this topic.

What do you mean by "checks if they arrive on the internal port (default 26)"? Does it do or not do the SPF check when 'Use SPF' is disabled on the internal port or the external port? Context: I set "Use SPF" to "No", but am still seeing "Recipient address rejected: Rejected by SPF:" for mail...

Create a cluster and use any cluster node's web interface.

Use defaults unless you have reasons not to :).