Or maybe even a different approach:
how can i - not being tec savy - upgrade my owncloud 9 installation on my webserver to nextcould - prefereably of course while the system is running keeping all my settings, but if that is not advisable, i´d rather set up a new installation.
By now, I have set up a complete new installation on our webhoster, which ran pretty smooth but i get some error messages in the log - anything i should take care of or should i just ignore those warnings?
Error PHP opendir(/tmp): failed to open dir: Permission denied at /kunden/16XXXX0_XXXXX/nextcloud/lib/private/TempManager.php#188 2016-07-24T19:34:49+00:00 –
Error PHP opendir(/tmp): failed to open dir: Permission denied at /kunden/16XXXX_XXXX/nextcloud/lib/private/TempManager.php#188 2016-07-24T19:33:10+00:00 –
Error PHP opendir(/tmp): failed to open dir: Permission denied at /kunden/16XXX_XXX/nextcloud/lib/private/TempManager.php#188
You’ve just got some permission problems. Just do a quick search on this forum for one of the bunch of posts about setting file and directory permissions for all of the files in your install.
I did a search for setting the permissions, since i didnt get a real result out of it for me, I tried to contact my webhoster support, but now it really gets tricky for me: what path should I set?
Wir haben die von Ihnen übermittelte Fehlermeldung geprüft und können Ihnen
mitteilen, dass die Komplikationen bezüglich des tmp-Verzeichnisses auftreten, da die
Session-Dateien im Verzeichnis /tmp gespeichert werden und Sie dort nur
eingeschränkte Rechte besitzen.
Daher ist es empfehlenswert die Session-Dateien nicht in diesem Verzeichnis zu
speichern, sondern innerhalb Ihres Webspaces. Um dies zu tun, können Sie in der
php.ini den ‘Session.save_path’ setzen. Dieser Pfad sollte sich in Ihrem
Kundenverzeichnis befinden, damit Sie ausreichende Berechtigungen besitzen. Beachten
Sie bitte, dass es unbedingt notwendig ist, dass diese Dateien regelmäßig gelöscht
werden, um Komplikationen auf Grund der Datenmenge zu vermeiden.
Nähere Informationen zu Sessions und dem “Session.save_path” finden Sie zum Beispiel
auf folgender Webseite:
http://www.php-resource.de/handbuch/ref.session.htm
http://de.php.net/session_save_path
Um die php.ini anzupassen empfehlen wir Ihnen den PHP.INI-Editor zu verwenden. Diesen
erreichen Sie im Kundenmenü unter “https://admin.df.eu”. Hier klicken Sie nach dem
Einloggen auf der linken Seite im “Auftragscenter” im Bereich “Für Profis” auf “PHP-
Einstellungen”.
It’s perhaps already enough to set this in your config/config.php:
You can just use any folder (must be under your control), e.g. /kunden/16XXXX0_XXXXX/nextcloud-tmp
Thanks for your advice, with the help of my webhoster i was able to do it.
However, is there a way to check, test or rescan if the problem persistsor if it is no more a problem for the system?
thanks
Next problem occurs: owncloud client will not connect to new nextcloud installation as i did connect before with owncloud installation… its like milking mice…
Hi lex,
I’m sorry to learn about the many problems you run into. Sounds a bit like you started migrating 4 weeks too early: Nc has just started so there a quite a lot of loose ends yet to tighten on various levels. Perhaps too many for your needs right now?
I know that I’m not helping, but if it is an option for you, why not wait 2 or 3 weeks rather than trying to fix yourself what might not be an issue anymore, once the Devs had the chance to tie things together on the various ends: in this concrete case this would mean: wait for an Nextcloud client to use 
John
Without detailed error messages, nobody can help you. Debugging in hosted environments is difficult, so it is perhaps better to follow the advice of @John and stay a bit longer with owncloud.
When experiencing problems with the client, it can be worth trying the nextcloud-demo-server.
Thanks for the tipp on the demo server - didnt find anything about it, can you point me there?
About error message the owncloud app just says “Zugang vom Server nicht erlaubt. Klicken Sie hier zum Zugriff…” (Login not allowed by server. klick hier to check if you can log in with a browser…") - did so, login with browser is possible.
thanks
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
