-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Can not connect to nextcloud app account #1604
Comments
@desperateCoder we changed this specific part in the latest version, so I can even without stacktrace tell (thanks though for fetching the logs!), that this happend when calling @pern0x did you used the Deck Android app before? Is it possible that you changed settings like @pern0x does the output of {
"ocs": {
"meta": {
"status": "ok",
"statuscode": 200,
"message": "OK"
},
"data": {
"version": {
"major": 28,
"minor": 0,
"micro": 1,
"string": "28.0.1",
"edition": "",
"extendedSupport": false
},
}
}
} |
Thanks for the quick reply. I did use the deck app before, but I did not activte wifi only. I have delete the storage of the app and uninstall it complete. After both actions the same message was shown. |
The connection is not possible on mobile or on wifi |
Are you able to provide a temporary test account on your instance and send the credentials to info@niedermann.it ? This way we might be able to debug the cause. |
Hi @pern0x, I tried it myself with your provided credentials and also got an error. Seems like whoever is answering our request behaves quite strangely:
Whats interesting here are two parts:
and
The funny questionmarks aren't added by me or got added while copying, this is the actual response from the server. By the HTTP-Status of 520 I guess your server is hidden behind CloudFlare? No idea what magic they are doing here, but this often leads to problems of various manner. Bypassing Cloudflare / Turning it off should your issue. And I guess we'll never know why there are funny bytes in the Sadly we can't do anything on our apps side. If the infrastructure won't let us talk to the server, there's not much we can do about it. Does this help? |
What's really weird though: seems like CURL gets to the server. I'm not sure, but maybe there's actually an issue on our side. I'll have a deeper look at it as soon as I find some time. Would be really nice if we could keep the test account for an additional week or something. |
Hey @desperateCoder , |
@pern0x ok, I did some further research and found the following: when i
In that case the Is there a configuration on the server side setting this header? usually you'll find something like this in EDIT: In case this fixes your issue, feel free to close this issue and delete the test user (thanks for providing the user!) |
@desperateCoder thank you very much. It solves my issue. |
This issue respects the following points:
Describe the bug
Expected behavior
It should be possible to connect.
Deck Android version
1.24.1
Deck server version
1.12.2
Nextcloud Android version
3.28.0
Nextcloud version
28.0.3
Device
Pixel 8 Pro
Android Version
grapheneos 14
App Store
Stacktrace
The text was updated successfully, but these errors were encountered: