Ok, so following those logs, it seems that the app is retrieving correctly the capabilities and the file list from the server, but then doing a POST to share the file returns a 500. In any case, those logs are not from the Android app, which can be useful for us to see the cause of the problem here. So I can’t conclude anything yet.
If you want, please provide us with those app logs. Also, be careful what you post here since this is a public site (your IP is being shown in the logs ). I created a private folder for your logs in our internal cloud:
I was checking a bit and seems that the server is returning a 500 error due to CSRF check failed, so my initial guess is that the request is being rejected for security reasons (maybe because of the origin of the request, that the server considers as suspicious). Do you have any middleware in-between or any security setting in your server that could collide with this? For further research, logs from the server would be needed now that we know it’s the backend the one which returns the error and the reason… But that would be for the backend team, which you can ask in this same forum as well. In any case, check any middleware, proxy or security settings you have now in your server and let’s see if you find something useful.
Let me know if you find any problem that I can help you with!
Hi @dslthomas! It seems server logs are going to be needed to take a deeper look and figure out why the 500 response. Could you upload them to the same link as the other day? I also add @jvillafanez to the thread, he will be able to help you with server logs better than me
It might be a hard crash… could you also check the apache error logs?
There is a 500 in the apache access logs, but I don’t see anything weird in the ownCloud logs. If there isn’t enough memory for PHP it might make sense for the request to crash. This case might explain the “sudden” stop of ownCloud log messages for the request, as well as the abnormal 500 error code in apache.
There are also some other tests you could do in order to narrow down the options:
Check if you can create shares from different clients using the same account (iOS, desktop or web)
Since you’re login with a token (app password maybe), try to login with the usual username and password for the account and retry.
Try with a different LDAP account.
Try with a different regular (local) account.
If the problem is somehow related to LDAP, we’d probably need the LDAP configuration. You can use occ ldap:show-config (make sure there is no security info visible)
). I created a private folder for your logs in our internal cloud:
