Thanks.
Odly, I can log into the demo server with no problem.
When I try to log into my own server, it doesnt seem to generate a specific warning in the log (though the log seems to be full of warnings about invalid argument and undefined offset etc, but not just after the login attempt occurs.
I just don´t know what could have been changed. I did use an owncloud installation before, so i had it working some time.
Do you use your own themes? Other modifications? Apps?
Invalid argument and undefined offset should not pop up. Such errors have been reported before (check the bugtracker) if you can find something similar (with solution). To get more information, can you fill out the issue template: https://raw.githubusercontent.com/owncloud/core/master/issue_template.md ? If it turns out to be a bug you can later do copy&paste to github.
Basically no themes (did change backround color though) and just apps like calendar, notes, task, adresses, but did not do anything with them so far.
started to fill out the issue template however it seems to be something i have to log into github and present publically since i am no developer i have to look into that.
strange thing is, again, it worked before with owncloud on same webserver and i can log into nextcloud test server - so i wonder if there is anything wrong with my installation moving to secure domain xxxx.xxx.de. Also, by the way, integrity checker is disabled, but i dont know if thats normal for nextcloud 10 beta?
Don’t use a beta version on a system you have so little control and expect it to work.
If installing a nextcloud 9xx has a good chance to solve the problem i am happy to try it. However, since the database is not filled yet and we are only about to start i thought it would be good to start with a completely fresh install of nc 10
Update: installing non beta 9053 doest change anything, still i am not able to log into the nextcloud installation with the desktop client, but a bunch of other errors and problems. starting to gro frustrated with the experience.
Can you do a direct webdav access via terminal (from a client):
curl -v https://example.org/nextcloud/remote.php/dav -u username -X PROPFIND
This command should give you a list of all files in the user’s directory. Check your Nextcloud and webserver (if possible) logfile (should be similar to owncloud: https://central.owncloud.org/t/how-to-find-webserver-or-oc-logfile-enable-php-logfile/808?u=tflidd).
If i read it right, its probably not allowed:
< HTTP/1.1 405 Method Not Allowed
< Date: Mon, 01 Aug 2016 10:11:14 GMT
< Server: Apache/2.4.20
< Strict-Transport-Security: max-age=15552000; includeSubDomains; preload“
< Allow: POST,OPTIONS,GET,HEAD,TRACE
< Content-Length: 323
< Connection: close
< Content-Type: text/html; charset=iso-8859-1
<
The requested method PROPFIND is not allowed for the URL /nextcloud/remote.php/dav.
Whats puzzling to me: after i did a complete fresh install of a stable nextcloud version and did not activate any apps or such - the client still wont work.
When i switch back to my old owncloud installation, client works immediately.
I keep trying to have a fresh start with nextcloud however, but it seems like there is something wrong here… no idea where to look.
There is a problem with your webserver configuration. Could be mod_rewrite, DAV enabled, HTTP verbs, … there is a more or less complete checklist: https://central.owncloud.org/t/how-to-fix-caldav-carddav-webdav-problems/852?u=tflidd
