I am opening a new thread in a follow up to this conversation Problems installing @ webhoster - #29 by tflidd , because after everything else seems to be working one problem remains consinstent:
the mac os x client for own cloud does (in my case) not work with nextcloud.
did a fresh install on the hosted webspace of nextcloud, no beta version, latest stable version of 9xxx.
we repaired all the rights, installed a tmp directory. error messages now appearing are minor and have also been appearing with owncloud.
when i use this very domain with owncloud, the desktop client will log in the account and start transfer.
when i use this domain with nextcoud, i will always always get an error message that the server doesnt allow access. (see image)
When i follow the link to login with the same passwort / username via webbrowser, i will log into nextcloud with no problems.
also, no error is visible in the log from the login attempt.
Also, I will get an error saying some files didnt pass integrity check:
Technical information
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.
Webhosters Support wrote me that there are some files missing, where the system wants to write to user.ini, which doesnt seem to exist:
Wir können Ihnen bestätigen, dass es serverseitig kein Problem diesbezüglich besteht. Wie bereits mitgeteilt, haben wir die in dem Forum beschriebene Direktive mod_rewrite in der .htaccess eingefügt haben. Die eigentliche Fehlermeldung sagt aus, dass Owncloud das Upload Limit in /kunden/XXX/kumo/tmp/oc_tmp_Ur5hjg-folder/.user.ini schreiben will. Die Datei existiert nicht.
Die folgendene Fehlermeldung besagt, dass die Datei /kunden/XXXXX/kumo/.user.ini in der /kunden/163850_80799/kumo/lib/private/integritycheck/checker.php aufgerufen wird:
Error PHP copy(/kunden/163850_80799/kumo/.user.ini): failed to open stream: No such file or directory at /kunden/XXXX/kumo/lib/private/integritycheck/checker.php#189
Please check the configuration of your apache or nginx installation. I had the same error a few months back when it was still just owncloud and solved it by checking my nginx configuration against the documentation. I do not know what changed in the requirements.
This link might help you though:
In short, check the rewrite rule if you are using Apache. Or similar configuration settings for nginx.
The link says something about self signed certificates, and OS X I had it on Ubuntu 16.04 with Lets Encrypt certificates, but I am fairly certain that will give you the needed hint. If you are running Apache, check your .htaccess
I have asked support from my webhoster about this and they actually tell me its a known bug in owncloud/nextcloud and the error message doesnt really pose any problem, can be switched off - correct?