-
Notifications
You must be signed in to change notification settings - Fork 815
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nextcloud - Could not parse the JSON returned from the server: illegal value #1915
Comments
###Fixed: Closing ticket. |
As @jhenin mentioned in #2226, this issue still persists:
@jhenin Could you please provide all version information:
And please also client (and if possible, server) logs? :) |
Thank you @misch7 ! The client version that is currently giving me the error is 2.6.5, using the AppImage on Ubuntu 18. |
thanks @misch7 to reopen this issue as i - similarly to @jhenin - regularly see this problem with university owncloud installations. besides the buttons "Re-open Browser" and "Copy Link" not working in PureOs (a debian variant using wayland), i guess the problem lies within the single-sign-on-solution that my providers have implemented (i guess its something with SAML). in my case, the url the nextcloud client is trying to access is returning an HTML instead of a JSON (the single-sign-on website). hope this helps developing the issue? how can i help further? |
I have the described issue. System:
Error message is the same as described previously The workaround worked for me:
Yet, it looks like the error occurs every time the client is restarted. |
Same problem here... I would like to add that I use a nextcloud-instance privately on my home-server and that I would love to use only one client to manage both accounts. Honestly speaking I trust the official client more in terms of features and security fixes. |
Same problem here... Client: AppImage Version 3.0.1 (Ubuntu). |
I have the same problem. Purging the client and reinstalling fixes the problem for a single login but then the problem reoccurs. |
It seems that the owncloud client works... not sure if this helps. |
I have been using the owncloud client before but now it is rejected by the server as being too old ("it" being the version bundled with Ubuntu 20.04, possibly a more recent one would work). So possibly development of owncloud/nextcloud has diverged to become incompatible? |
Clearly they diverged and you can expect that to increase over time.
Well, you'd have to enable logs on the server indeed and it's best if you look at the documentation for that. Likewise it's likely a good idea to provide debug client logs (using --logdebug and --logfile on the command line). |
I have a client-side debug log of the incident. Is that any help? I don't see anything obviously informative there but I don't know precisely what to look for. Here is the part that seems relevant to me:
|
That helps locate the place in the code at least, although for now I'm unsure why it does so. |
For anyone stumbling across this, an easy workaround is mentioned in this comment :
|
@jhenin this brings nextcloud sync to my owncloud server back, thank you so much
|
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you! |
This occurs when trying to authenticate to a Nextcloud 11.0.2 server on the 2.6.4.15215 client for Windows. I am able to authenticate using the browser, but the above error occurs and it does not continue. No other use in this organization is experiencing this issue.
Expected behaviour
I sign in and Nextcloud continues as normal
Actual behavior
I cannot sign in and a red error that says "Could not parse JSON returned from the server: illegal value" pops up. Every other person in this organization can do so without issue.
Steps to reproduce
Client configuration
Client version: 2.6.4.15215
Operating system: Windows 10 1909
OS language:
Installation path of client:
Server configuration
Nextcloud version: 11.0.2
The text was updated successfully, but these errors were encountered: