After upgrade from 4.0.0 to 4.2.0 backups to internal S3 don't work

[justsomeuser]

Hi,
apparently after the upgrade the behaviour concerning http proxy settings has changed leading to problems when using internal s3 storage.
It looks like the fix for bug 6716 broke things for customers, that want apt updates and subscription checks over http proxy but don't want to use proxy for s3 access (internal s3).
The documentation is also incomplete and doesn't state that this configuration would be used for other stuff:

Once configured this proxy will be used for apt network requests and for checking a Proxmox Backup Server support subscription

I'd welcome a solution, where such proxy settings can be set separately.

My workaround for now was to copy `/etc/apt/apt.conf.d/76pveproxy` (with proxy settings on) to `/etc/apt/apt.conf.d/76pveproxycustom`. Then remove the proxy settings.
Now subscription checks don't work.

 

[Chris]

Yes, this is indeed not ideal. While the opt-in flag was added for connections to remote PBS instances, it was not for S3 client connections. Will provide a patch to provide such a flag for the S3 endpoint configuration.

Edit: send patches adding an opt-in flag for using the node's proxy config on individual S3 endpoints https://lore.proxmox.com/pbs-devel/20260511151924.901315-1-c.ebner@proxmox.com/T/