Recent content by longer

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" Environment="NO_PROXY=localhost,127.0.0.1"

Could you provide: - network config from pve host: cat /etc/network/interfaces - Share vm config: qm config [VMID] - Share network config from the vm.

Np. You can check journalctl/access.log in the destination nodes, while you are attempting to connect from your management node.

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 from external subnets. Also ensure the clean up...

Do you have test lab where the same issue observed? I wanted to suggest to even try with Kernel 6.x, it's seems something specific with your hardware.

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 selected config plays vital roles, therefore check...

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 ~# proxmox-backup-client status --repository...

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

At the moment this isn't fixed yet. If you want, you can CC yourself on the bug report to stay updated on the progress.

For the comment issue, I think its the below bug: https://bugzilla.proxmox.com/show_bug.cgi?id=6943

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] https://pve.proxmox.com/wiki/Web_Interface_Via_Nginx_Proxy "

See: https://forum.proxmox.com/threads/enabling-hsts.115040/post-498043

Perfect, thanks for sharing :)

Hmmm did you manage to get some findings?