NextCloud Installation Q & A

  • Thanks, Stramm, but like i said, I fixed it by editing my fastcgi_pass $socket; to something else. I am just trying to understand why set $socket "unix:/var/run/fpm-xxxxxxxxxxxx.sock was incorrect on my second attempt at this.


    Zitat von tinh_x7

    set $socket ...... in the /etc/nginx/sites-available/zzz-omv-nginx) is auto generated for you, no need to modify that.

    ... yeah, and mine was "autogenerated" wrong.

  • Maybe delayed deploy? Did you try to switch release channel to 'beta' and back to stable? Worked for me a couple times with earlier upgrades.

    Chaos is found in greatest abundance wherever order is being sought.
    It always defeats order, because it is better organized.
    Terry Pratchett

  • I had a lot of problems with my NC13 installation after updating to OMV4 but it was my own fault in the end.
    I reconfigured a new pool and server but this did not fix my issues as i still got internal server errors.


    My Problem, i didnt check the nextcloud logs.


    I still had the memcache APCu Settings in my config.php



    Code
    'memcache.local' => '\\OC\\Memcache\\APCu',

    So i disabled this line and it finally started again :)


    After i installed the apcu modul using:



    sudo apt-get install php7.0-apcu
    I could enable this option again now my nextcloud server is running happily again like before.
    Only thing missing is fail2ban

  • Hey
    I have a problem with NC installation using OMV / Docker. As I am a new Raspberry user, I do everything like in tutorials, and everything is OK. I installed the NC from the terminal according to the advice on the OMV website and I succeeded. At the next RP I wanted to do it with the help of Docer - and the server did not work. After downloading the image and running - error 404. Can anyone tell you how to set Modify Container? Clean installation of the OMV (the newest) system, server running, I added Docer repositories.

  • OMV version: 3.0.99
    Nextcloud version: 13.0.1


    I am stuck in step 7 of the installation guide. I go to http://<ip>:90 and keep getting 404 error. Error log says "Primary script unknown" while reading response header from upstream.


    I followed the exact same steps but did not turn SSL on yet. This is my server extra options:


    To debug, I added the following to http block of nginx.conf:

    Code
    log_format scripts '$document_root$fastcgi_script_name > $request';

    And this to the site's server block:

    Code
    access_log /var/log/nginx/scripts.log scripts;


    I then tried to access the site and found this in this log I created:

    Code
    /srv/dev-disk-by-label-DATA/www/nextcloud/core/templates/404.php > GET / HTTP/1.1


    I am unable to figure out the problem? Please help...

  • Can you post your NextCloud's Nginx setup screenshot ?

    I upgraded OMV from 3 to 4 now and reinstalled mysql and nginx and set up everything again. I am still facing the 404 not found error. Here is the screenshot you requested. Thank you!



    Here is also screenshot of permissions inside the nextcloud folder:


  • Your 'PHP: Default Config" is turned OFF.


    Turn it ON, and try again.

    Thanks for the reply. Ok I am very confused now. Should I use the php default config like you mentioned or use the pool that we create in earlier step? I dug in more and found out that, for some reason (this bug needs to be investigated), the .conf and .sock file was not created for the pool that we created and hence fastcgi_pass $socket wasn't working like @z-vap had faced. I saved the pool config again, and this time .conf and .sock were created for the pool. So after that, I changed it back to fastcgi_pass $socket and I didn't face 502 Bad Gateway. Now back to my bigger problem, if we're using the pool, we shouldn't use the PHP default config right?

  • @mrboki, I think I am facing the same problem. Were you able to fix the 404 error?

    Hello, no I did not as I got no response. The problem is that the installation guide is not working.


    "2. Un-check the "default config' option in the PHP section. (Credit to @Zocker1996)"


    I tried with checked but it's not working either... same 404 error. Did you solve this with .conf and .sock?

  • Hello, no I did not as I got no response. The problem is that the installation guide is not working.
    "2. Un-check the "default config' option in the PHP section. (Credit to @Zocker1996)"


    I tried with checked but it's not working either... same 404 error. Did you solve this with .conf and .sock?

    Nope. What I was explaining was the cause behind 502 Bad Gateway error. I tried checked and unchecked too and getting same 404 error. I think I am giving up and going to try with docker. This is too much of a mess.

  • Ensure your Nginx and PHP are running.
    Some users have the same issue like yours.
    It could be incorrect socket.


    You can try to turn off the PHP default configure option, and do the followings:


    Replace fastcgi_pass $socket with fastcgi_pass /run/php/php7.0-fpm.sock;


    service nginx restart
    service php7.0-fpm restart

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    5 Mal editiert, zuletzt von tinh_x7 ()

  • I had luck with this change and could install nextcloud 13 on omv4 successfully. Thanks for your hard work and investigation!
    Now I have checked my server against the ssllabs servertest and got - i think - a https-redirection-loop.



    Do you experience the same with your config or have an idea what the cause could be?



    My nginx config:

  • Thanks for the reply. Ok I am very confused now. Should I use the php default config like you mentioned or use the pool that we create in earlier step? I dug in more and found out that, for some reason (this bug needs to be investigated), the .conf and .sock file was not created for the pool that we created and hence fastcgi_pass $socket wasn't working like @z-vap had faced. I saved the pool config again, and this time .conf and .sock were created for the pool. So after that, I changed it back to fastcgi_pass $socket and I didn't face 502 Bad Gateway. Now back to my bigger problem, if we're using the pool, we shouldn't use the PHP default config right?

    This is an interesting observation. I will need to save this for the future.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!