Arch Linux

sweetthdevil

Member

Registered: 2009-10-20

Posts: 406

Re: Nextcloud 21.0.0.2-21.0.0.9 sevral issues, index in first post

Hello,

Sorry to revive an old post - but are all the issues now sorted?

dsreyes1014

Member

Registered: 2014-06-28

Posts: 56

Re: Nextcloud 21.0.0.2-21.0.0.9 sevral issues, index in first post

Curious to know the same. The updated wiki really screwed me up and now I'm not sure what caused the internal server error with nginx.

Last edited by dsreyes1014 (2022-04-05 00:47:35)

infinite-recursion

Member

Registered: 2016-09-27

Posts: 4

Re: Nextcloud 21.0.0.2-21.0.0.9 sevral issues, index in first post

Adding to this thread because I had the same problem...

I had set up a new system in May 2022 without any issues, running Nextcloud 23 on apache and php-fm.

Now, with the upgrade to Nextcloud 24.0.2, the server and desktop app kept working, but in the browser I was stuck on the login screen just like several previous posters.

In the log, I found "Error: session_regenerate_id(): Session ID cannot be regenerated", indicating a problem with the session storage.

After hunting around for the responsible configuration (there was no /var/lib/php folder, and the php-fpm.ini just specified /tmp), I was saved by the extensive installation notes I had kept this time:

install --owner=nextcloud --group=nextcloud --mode=700 -d /var/lib/nextcloud/sessions

i.e. the session information was supposed to be in /var/lib/nextcloud/sessions.

For some reason, the upgrade seems to have deleted this folder, and even though nextcloud owns /var/lib/nextcloud, it does not seem to be regenerated on the fly. After recreating the folder, everything works fine again.

I still cannot find in which configuration file the path /var/lib/nextcloud/sessions is stored, though...

capthookb

Member

Registered: 2007-12-10

Posts: 123

Re: Nextcloud 21.0.0.2-21.0.0.9 sevral issues, index in first post

I would like to also add a question on the information status of the wiki.
I was running Nextcloud v<21 on a raspberry with somewhat success (custom script for fixing permission issues etc) and I have been applying updates without noticing any issues. But after a hard disk failure, I decided to reinstall it from scratch, according to the wiki page and using apache + uwsgi. But I cannot get it to install.

I reach a point where everything seems ok, but I get a not found error (just those 2 words in the browser). I can access non php files located under the nextcloud folder, for example https://mydomain.com/robots.txt . Or simple test html pages that I create there, but no .php file is working.
The source code of the browser page is the following:

Not Found

which is not even a valid html file.
The log of the uwsgi@nextcloud.service prints:

Aug 19 10:36:04 rasp uwsgi[1273]: [pid: 1273|app: -1|req: -1/5] 2a02:c6 () {86 vars in 1776 bytes} [Fri Aug 19 10:36:04 2022] GET / => generated 9 bytes in 0 msecs (HTTP/1.1 404) 2 headers in 71 bytes (1 switches on core 0)
Aug 19 10:36:06 rasp uwsgi[1273]: [pid: 1273|app: -1|req: -1/6] 2a02:c6 () {82 vars in 1695 bytes} [Fri Aug 19 10:36:06 2022] GET /index.php/apps/photos/service-worker.js => generated 9 bytes in 0 msecs (HTTP/1.1 404) 2 headers in 71 bytes (1 switches on core 0)

Strange things happen. For example, service-worker.js is not a valid file under /usr/share/webapps/nextcloud/apps/photos/
httpd log do not report any errors.

Is uwsgi with php a viable solution or do you have any ideas why this happens?

I tried yesterday php-fpm as well, but I don't remember making it work either. But since I have been working on that issue for over 10 hours, my mind and memory was quite blurry. I will try again tomorrow. with php-fpm.

capthookb

Member

Registered: 2007-12-10

Posts: 123

Re: Nextcloud 21.0.0.2-21.0.0.9 sevral issues, index in first post

Well after, deleting everything related to the installation, and following the wiki again with php-fpm and apache combination, finally I managed to successfully install nextcloud!
I had an error, though, after installing nextcloud, and going to Admin->Settings->Administration->Overview, the checking script would produce an error. I didn't note it, but it had to do with the application of open_basedir that I had applied to both /etc/webapps/nextcloud/php.ini as well as /etc/php/php-fpm.d/nextcloud.conf as suggested by the wiki. I removed the error by leaving the open_basedir only in /etc/webapps/nextcloud/php.ini and removing it from the php-fpm pool conf file.