I’ve been running Nextcloud without this issue for a few years, but I’ve recently run into a connection issue using the desktop client when attempting to connect using TOR.
I’ve completed the steps here and successfully connected using the LAN address. I’ve completed steps 1 & 2 of the TOR setup, however when I attempt to connect the desktop client in step 3 I get the following error:
Failed to connected to Nextcloud at https://(TOR address).onion: An unexpected error occurred. Please try syncing again or contact contact your server administrator if the issue continues.
While I’ve bee able to connect to the same .onion URL using my browser without any issue, I have not had any success in getting the desktop client to open the authentication page to link the account.
I’ve tried a few potential solutions to this issue without finding success:
Reinstall of the Nextcloud desktop client.
Restart of the Nextcloud service on the server (the server is what is now called the “Server Pure” but when I purchased it a few years ago was called “Embassy Pro”)
Restart of StartOS on the server.
Running a system rebuild of StartOS on the server.
I’m at a loss for what to try next, any suggestions would be greatly appreciated.
I made some progress on this, rolling back to version 3.16.6 of the desktop client resolved it. However I’ve still not been able to get it to connect using 3.17.0 and beyond (3.17.1 as of the time of this writing).
Very recently, and for a whole version over 6 weeks, the Android client was broken and wouldn’t automatically upload files. This was literally an issue with the client target then with Nextcloud or StartOS. The latest version fixed the bug.
Your description of the problem, assuming you’re running the latest version of Nextcloud, sounds like a client issue to, especially since rolling back fixes it. It could be specific to Tor. Did you see if the error happens with the .local too?
The .local connection was working fine, including when using 3.17.1. However I haven’t had a chance to test it after rolling back to 3.16.6, though there were no issues with that connection that I ran into last month when that was the latest release.
Makes me wonder if they messed up something specific that breaks Tor. I haven’t been using it for a while with Tor, and you appear to be on Windows, so I’m not sure I can accurately reproduce.
Strangely enough, some of my Windows machines using NC over Tor stopped working, while other didn’t with the update to 3.17.0. This is how I discovered the missing proxy settings, as I was attempting to remove the account, and add it back again. I also had an issue on my Linux mint machine, where the new appimage wouldn’t run. Haven’t investigated that one yet. 3.16.6 worked well, so I resorted back to that, and disabled automatic updates. The NC team seems a bit to zealous on their client releases for my taste. They need an LTS channel, as the “stable” channel feels more like a beta, channel to me.