Hi,
thank you for the hint I tried this just now.
No luck there.
I also had our firewall team add a temporary exception for the server. With this the errormessage changed.
Apparently proxmox-backup-manager also won't work with our CA (harica)...
Have you founded a workaround?
Maybe add it to the service?
systemctl edit proxmox-backup-proxy.service
[Service]
Environment="HTTP_PROXY=http://your-proxy-ip:port"
Environment="HTTPS_PROXY=http://your-proxy-ip:port"...
Unfortunately, we do not have a separate test lab where the issue can be reproduced.
The problem is sporadic and only occurs on the production PVE host. We have not found a workload or test that can reliably trigger it, which makes controlled...
Does it make a difference if you restarted pveproxy and pvedaemon?
systemctl restart pveproxy pvedaemon
If thats doesnt help as well, check for residual iptables rules that may have been added during cluster setup and are blocking port 8006...
A tool is what you make it.
Whilst Proxmox VE won't do what you want out of the box, you can certainly create template VMs and clone them off.
Given its linux under the hood, If you need to expand things, you can always use scripting to achieve...
It is best to give it a try in your lab really quickly
The official documentation is informative:
https://pve.proxmox.com/pve-docs/
Also ensure to check:
https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE
For windows the used storage and...
My hunch was wrong, based on the shared config, the mtu is default to 1500.
For the second mentioned issue where you see connection to PBS fails, does Ping to pbs works from the affected host?
You can check also using the command:
root@pve ~#...
Could you share the network configs from 2 nodes where you observed the migartion issue and PBS connection problem:
cat /etc/network/interfaces
Just a hunch maybe its related to:
https://pve.proxmox.com/wiki/Roadmap#9.0-known-issues
I think a workaround might be possible via pfSense, I just looked and found the option Ignore Client Identifiers:
I have not test myself. just a thought
If you have a requirement to implemented, then maybe you can try as mention in the aforementioned thread:
"
The alternative would be some proxy server that sets that for you. See the guide in the wiki [2].
[2]...
The solution is:
[Service]
Type=oneshot
ExecStart=
ExecStart=/usr/bin/pmgreport --timespan today --auto
Add this ExecStart= to the /etc/systemd/system/pmgreport.service.d/override.conf
As mentioned above by @AntonJ , this behavior already mentioned in the documentation [0]:
I think at the moment thy only way is using SAVC, hopefully it will marked stable in near future,
[0]...