Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

  • what ssl error you got?

    Code
    nginx: [emerg] no "ssl_certificate" is defined for the "listen ... ssl" directive in /config/nginx/site-confs/default.conf:9

    that one? was solved by deleting /config/nginx/nginx.conf... but i think you mean some other error?


    NC 25 works just fine here ... just could slap my own for over motivated "update your image" after vacaition today ... without that i would run NC 25 without problems ... now i'm on a 26.0.2 and can't update cause the servers are down .. my cron-job will not work and some files are not integer <-- what ever NC will tell me with this ...

    so i will just hang on - hope the servers are back online soon and after all updates are done everything will work as it should *fingers cross*

    ___________________________
    OMV5@AsRock j3455 8GB RAM

    • Offizieller Beitrag

    I'm gonna probably switch to AIO, which means I"ll probably have to switch to npm

    Here are the proxy options tested with Nextcloud AIO and the configuration in each case. https://github.com/nextcloud/a…your-reverse-proxy-config

    I found Nginx Proxy Manager to be especially easy. RE: OMV Quick Configuration Guide

    But there are others.

    • Offizieller Beitrag

    what ssl error you got?

    Code
    nginx: [emerg] no "ssl_certificate" is defined for the "listen ... ssl" directive in /config/nginx/site-confs/default.conf:9

    that one? was solved by deleting /config/nginx/nginx.conf... but i think you mean some other error?


    NC 25 works just fine here ... just could slap my own for over motivated "update your image" after vacaition today ... without that i would run NC 25 without problems ... now i'm on a 26.0.2 and can't update cause the servers are down .. my cron-job will not work and some files are not integer <-- what ever NC will tell me with this ...

    so i will just hang on - hope the servers are back online soon and after all updates are done everything will work as it should *fingers cross*

    There's another one...

    • Offizieller Beitrag

    what ssl error you got?

    Code
    nginx: [emerg] no "ssl_certificate" is defined for the "listen ... ssl" directive in /config/nginx/site-confs/default.conf:9

    that one? was solved by deleting /config/nginx/nginx.conf... but i think you mean some other error?


    NC 25 works just fine here ... just could slap my own for over motivated "update your image" after vacaition today ... without that i would run NC 25 without problems ... now i'm on a 26.0.2 and can't update cause the servers are down .. my cron-job will not work and some files are not integer <-- what ever NC will tell me with this ...

    so i will just hang on - hope the servers are back online soon and after all updates are done everything will work as it should *fingers cross*

    Once we got that error fixed, this one started (it was easy to resolve)...


    Code
    48CB5DB3877F0000:error:1200006C:random number generator:rand_new_drbg:error instantiating drbg:crypto/rand/rand_lib.c:601:
    s6-rc: warning: unable to start service init-keygen: command exited 1

    That one, they spent almost 2hrs trying to figure out. They tried a sort of hacky solution to fix it, but it didn't work. I was tired at that point and went to bed.

  • update servers back online ... so now i'm on 27.0.2 (but on the "older" docker image)


    Cron-Job still don't work?!

    Database / Memcache

    PHP - sysvsem


    Code
    still on the "problem" list. 
    
    
    Es gibt einige Fehler bei deiner Systemkonfiguration.
    
        Letzte Cron-Job-Ausführung: Vor 10 Stunden. Check the background job settings ↗.
    
        Die Datenbank wird zum Sperren von Transaktionsdateien verwendet. Um die Leistung zu verbessern, richte bitte, sofern verfügbar, Memcache ein. Weitere Informationen findest du in der Dokumentation ↗.
        Dieser Installation fehlen einige empfohlene PHP-Module. Für bessere Leistung und bessere Kompatibilität wird dringend empfohlen, diese zu installieren.
            sysvsem

    anyone? - i just don't get it -.-

    ___________________________
    OMV5@AsRock j3455 8GB RAM

  • ok ...

    cron.php is done - changed the path in

    Code
    nextcloud/config/crontabs/root

    file to match location - i think something just messed up here with my upgrade fail


    sysvsem problem was solved with nextcloud 26.0.2 image (i just forgot image upgrade after all ....)

    still on list: Transactional file locking - can someone help me on this plz?

    ___________________________
    OMV5@AsRock j3455 8GB RAM

    • Offizieller Beitrag

    Todays update broke my omv, it just displays loading... and gets stuck. Any way to resolve this issue?

    I finally got mine going again (Have no idea what was wrong, as I did exactly what I've done for years). Spent another 45min or so with the dev's in discord. This is the 3rd time I've gotten a bricked install (one I recovered from w/ a backup, the other two I had to do a complete reinstall, with this last one being a total pain). Prior to this update change, I never had issues with NC in the 5-6yrs I used it... I kept my system updated regularly, and everything "just worked". It's a shame a bunch of morons on Unraid caused this. Dev's swear this new system is working better than the old one, but I'm not convinced of that after watching discord, the forums, etc.


    As much as I hate it, I'm done with linuxserver/nextcloud. I'll be switching to AIO probably Wednesday, or I may have to put it off till Monday. What pains me is I'm going to have to nuke swag (which I absolutely love due to it's simplicity) and switch to npm.

  • What pains me is I'm going to have to nuke swag (which I absolutely love due to it's simplicity) and switch to npm.

    I can't think of why you would have to switch away from swag.


    Having said that, I only thought about using my existing swag setup from my original Nextcloud install (linuxserver), but decided to use npm and AIO, which I set up over the weekend. NPM is in its own separate container.


    I wanted a challenge, I guess. Which I did not get, other than some stupid self-created permissions issues I managed to discover and fix on my own, and pointing the proxy host to the incorrect port instead of the Apache port.


    I am not tied to swag, for sure, as I was only using it for Nextcloud.

    For my subdomain setup following the how-to in this forum, I had to edit a number of configs files for things to work, as well as to remove the Admin/Security warnings. Not a big deal, really, as a long time Linux desktop user.


    But with npm, and nextcloud-AIO I have not had to do any of that at all.


    An interesting difference from using the AIO as that if you want to stop Nextcloud entirely, you need to do so from the AIO interface, as stopping the Nextcloud-AIO from the Compose plugin does not appear to stop any of the multiple related containers involved.


    Will see how this runs, compared to the linuxserver images.

    Asrock H370M-ITX/ac | i5-8400T | 16Gb RAM | Node304 case | 4-3Tb HDDs | 256Gb nvme | 128 Gb SATA SSD

  • Will see how this runs, compared to the linuxserver images.

    Runs great mate been using it for a long time.

    I don't use swag just npm

    Plugins - compose, cputemp, omv-extras, sharerootfs.

    Drives - 1tb nvme Data, 2TB nvme Leeching, 24TB (8tbx 3 merg) Media,

    Docker - nginx-proxy-manager, plex, prowlarr, qbittorrentvpn, radarr, sonarr, watchtower.

    • Offizieller Beitrag

    swag does not support AIO like it does most containers. I'll probably try it, but when I tried it with the official container a few years ago just to try it, it didn't work


    I'm sure it can be done, just have to take a look at it.

    • Offizieller Beitrag

    An interesting difference from using the AIO as that if you want to stop Nextcloud entirely, you need to do so from the AIO interface, as stopping the Nextcloud-AIO from the Compose plugin does not appear to stop any of the multiple related containers involved.

    If you use the backup utility of the compose plugin be careful with the Nextcloud AIO container. Only one copy of the two compose files will be made, nothing else will be copied. You should use the built-in backup utility in the Nextcloud AIO interface to regularly backup those containers.

    It gives me the feeling that the plugin does not know anything about the existence of those containers inside Nextcloud.

    Nextcloud AIO is like a miniPortainer, it manages everything internally. It has its advantages and disadvantages, at the moment it works very well for me after three weeks of use, I have already had to update some plugins without any problem, everything is perfect.

  • If you use the backup utility of the compose plugin be careful with the Nextcloud AIO container.

    Yup, that is what I am assuming, and just now set up backups via the AIO interface.

    Asrock H370M-ITX/ac | i5-8400T | 16Gb RAM | Node304 case | 4-3Tb HDDs | 256Gb nvme | 128 Gb SATA SSD

  • Hello,


    thank you for the guide, I managed to install everything right away without complications. When it comes to nextcloud I get stuck. On the nextcloudpage, when adding the admin and setting the mariaDB credentials, I receive the following error:

    Code
    Error while trying to create admin user: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[HY000] [1045] Access denied for user 'root'@'nextcloud.nextcloud_default' (using password: YES) 

    I checked the password many times. Is the username root not correct anymore?


    Edit one hour later...:


    So the fix was that MariaDB allows not more than 16 chars for the password and it cuts the following chars. And I thought I lost the ability to type correct.

  • I followed this guide a few nextcloud versions ago and it worked great. However, recently when I tried updating nextcloud it seemed to brick the installation so I've been trying to reinstall nextcloud from scratch.


    The issue I'm running into is at the nextcloud setup screen - only text shows, no images or style. If I try to create a database I get this error:

    Error while trying to initialise the database: An exception occurred while executing a query: SQLSTATE[HY000]: General error: 10 disk I/O error


    and then "Page not found" for all Nextcloud WebUI requests afterward.


    The swag logs are fine, but in the nextcloud container logs I see this error:

    Code
    Exception: Not installed in /app/www/public/lib/base.php:283
    
    Stack trace:
    #0 /app/www/public/lib/base.php(709): OC::checkInstalled()
    #1 /app/www/public/lib/base.php(1196): OC::init()
    #2 /app/www/public/cron.php(43): require_once('...')
    
    }
    2023-10-03T13:40:00+00:00 3 Not installed | reqId=[removed] remoteAddr= user=-- app=cron method= url=/nextcloud/cron.php userAgent=-- version= exception={"Exception":"Exception","Message":"Not installed","Code":0,"Trace":[{"file":"/app/www/public/lib/base.php","line":709,"function":"checkInstalled","class":"OC","type":"::"},{"file":"/app/www/public/lib/base.php","line":1196,"function":"init","class":"OC","type":"::"},{"file":"/app/www/public/cron.php","line":43,"args":["/app/www/public/lib/base.php"],"function":"require_once"}],"File":"/app/www/public/lib/base.php","Line":283,"CustomMessage":"--"}


    Has anyone else had this issue? I'm assuming it's a permissions problem but I don't understand what's causing it.

  • I have been using the exact configuration as described here by Macom and it worked flawlessly up to here. Due to a provider change i now need to route nextcloud through cloudflare (no public ipv4). Therefore i need to make it accessible on my internal LAN and get rid of the reverse proxy.

    When i uncomment this line :


    Code
    #    ports: # uncomment this and the next line if you want to bypass the proxy
    #      - 450:443

    and try to access it with 192.168.1.35:450/nextcloud i end up here:



    not sure what i am doing wrong

  • not sure what i am doing wrong

    You will need to undo the change in config.php to NOT rewrite the URL.

  • I thought of that too.

    Funny thing is: i already had a look there and the rewrite was wrong for a long time but still it worked without issue.

    I now took it out. result is the same, no change (commented 'overwrite.cli.url' line)

  • I now took it out. result is the same, no change (commented 'overwrite.cli.url' line)

    Commented out how?

    Did you restart Nextcloud container after?


    Without posting something to see, it's difficult and tiredsome to have to throw darts.


    Post the complete config.php but hide sensible data.

  • Commented out how?

    Did you restart Nextcloud container after?

    like this ://

    Yes i did restart the docker


    Without posting something to see, it's difficult and tiredsome to have to throw darts.

    Agreed

Jetzt mitmachen!

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