[Bug]: Per-account connections settings don't apply/work after reboot

[smcgu]

⚠️ Before submitting, please verify the following: ⚠️

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

Configuring an account proxy configuration does not work after reboot until the user manually changes the proxy selection.

The connection settings are still shown in the UI and the nextcloud.cfg file still contains the proxy configuration, but the connection does not appear to be using them. So, for some reason, after reboot the Nextcloud Desktop agent is not using its global or the account connection settings.

Steps to reproduce

1. Configure account to "Use global settings" (that has a proxy configuration)
2. Reboot system
3. Connection is broken
4. Open account connection settings
5. Confirm that it is configured to "Use global settings"
6. Confirm that nextcloud.cfg contains the proxy configuration
7. Switch account to "No proxy" -> Connection restored
8. Switch account to "Use global settings" -> Connection restored, still

Expected behavior

Account connection settings should work after reboot without manually reapplying.

Which files are affected by this bug

All files

Operating system

Linux

Which version of the operating system you are running.

Ubuntu 22.04

Package

Distro package manager

Nextcloud Server version

28.0.7.4

Nextcloud Desktop Client version

3.14.2

Is this bug present after an update or on a fresh install?

Updated to a major version (ex. 3.3.6 to 3.4.0)

Are you using the Nextcloud Server Encryption module?

Encryption is Enabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

N/A

Additional info

No response

[smcgu]

Related to #6890

[smcgu]

To be additionally clear, after reboot I copied and diff'd the nextcloud.cfg file before and after reapplying the connections settings in the GUI.

1. Reboot system
2. Observe broken connection
3. Copy nextcloud.cfg to nextcloud-before.cfg
4. Reapply connection proxy settings -> connection restored
5. Exit Nextcloud Desktop (to ensure updated nexctloud.cfg file)
6. diff nextcloud-before.cfg nexctloud.cfg -> no difference

[smcgu]

Bump.

This problem still exists in the latest package.

Package: nextcloud-desktop
Version: 3.15.3-20250107.145041.a595d5bcb-1.0~jammy1

[smcgu]

This bug still exists in 3.16.3daily (Ubuntu)

Package: nextcloud-desktop
Version: 3.16.4-20250429.181655.0febbee77-1.0~jammy1

[smcgu]

The nextcloud.cfg file appears to have a proper account proxy and global proxy config, but neither are loaded or set after reboot. In this situation, I don't care whether the account profile uses its proxy config or the global proxy configuration, as they are the same. I just need one of them to be loaded and applied.

The only way to get either to work, is to:

1. Open the Nextcloud Desktop client GUI
2. Navigate to the account proxy network tab
3. Toggle from "Use global settings"/"Manually specify proxy" to "No Proxy" (or any other option really)
4. Toggle back to "Use global settings"/"Manually specify proxy" -> connectivity established

...snip...
1\networkProxyHostName=127.0.0.1
1\networkProxyNeedsAuth=false
1\networkProxyPort=8080
1\networkProxySetting=0
1\networkProxyType=1
1\networkProxyUser=
...snip...
[Proxy]
host=127.0.0.1
needsAuth=false
port=8080
type=1
user=

[smcgu]

The buggy behavior has now changed with the release of 3.17.0. As reported in #8602, proxy functionality is now completely broken. There is no longer a way to configure system proxy configurations for the Nextcloud Desktop application and the original workaround of switching between proxy connection options no longer restores connectivity.

The new broken behavior includes:

1. Proxy settings selection (e.g., "No proxy") is not saved/persisted
2. Manual proxy type is not saved/persisted

Steps to replicate:

1. Add account
2. Navigate to "Connection settings"
3. Select "Manually specify proxy"
4. Enter values (e.g., SOCKS5, 127.0.0.1, and 8080) -> Broken ([Bug]: 3.17.0 Proxy Handling Broken #8602)
   .
5. Restart Desktop application
6. Navigate to "Connection settings"
7. Observe that proxy settings have changed to "Use system proxy" .
8. Switch to "Manually specify proxy"
9. Observe that the proxy type has been changed from "SOCKS5 proxy" to "HTTP(S) proxy" .