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

  • my question is ... I clearly changed the image, and it's still showing it is Debian based. I did the same thing on a virtual install, w/ a completely new mariadb install, and it also still showed it was a Debian install, instead of an alpine install.

    Well, that is a good question. One I really don't have an answer since I don't know....

    All it matters (at that time, I was running armhf and change the DB to webhippie) is it worked and I was able to update NC to v20 (or v21) and there was no more "yellow flag".

    After linuxserver released the "alpine" version, I swapped the DB from webhippie to linuxserver's and kept the TAG on the YML.


    After migrating to aarch64, I just kept using it, :)

    But your question made me check what does it show and I confirm, it shows the same kernel and version of the host:

    docker mariaDBLinux b172c62b184c 5.10.17-v8+ #1421 SMP PREEMPT Thu May 27 14:01:37 BST 2021 aarch64 GNU/Linux

    aarch64 Host Linux tacho 5.10.17-v8+ #1421 SMP PREEMPT Thu May 27 14:01:37 BST 2021 aarch64


    So, maybe the "alpine version" is somewhere "hidden" (?!?) on the dockerfile???

  • Hi,


    I have got a little problem with Nextcloud and Swag. Every work perfectly with my external access, but with internal access I have got now the following error on the browser:


    Code
    The page is not redirected correctly
    An error occurred while connecting to 192.168.1.200:450.
    The cause of this problem may be the disabling or refusal of cookies.
  • Hi,


    I have got a little problem with Nextcloud and Swag. Every work perfectly with my external access, but with internal access I have got now the following error on the browser:


    Code
    The page is not redirected correctly
    An error occurred while connecting to 192.168.1.200:450.
    The cause of this problem may be the disabling or refusal of cookies.

    Did you comment out port 450 in your docker-compose?


    Post your compose file or the instructions you followed.

    Air Conditioners are a lot like PC's... They work great until you open Windows.


  • Hi guys.

    Finally I solved complications with my router and I was able to open ports 80 and 443. I have Nextcloud installed following the guide and I can access it from the outside, everything works fine.

    My problem is that I cannot access Nextcloud from the LAN. Access to my domain from the LAN is blocked. I have seen users here with the same problem but have not seen the solution.

    What address do I have to put in the browser to see Nextcloud from the LAN?

    OMV 5, Intel core i3 3225, 8GB RAM, PendriveUSB system, ZFS RaidZ 5xWD Red 4TB, 1x120GB SSD Docker

    Tomorrow you will wish you had made a backup today !!

  • Is it possible that another domain needs to be added here? a local domain?:


    Code
    'trusted_proxies' =>
    array (
    0 => 'swag',
    ),
    'overwritewebroot' => '/nextcloud',
    'overwrite.cli.url' => 'https://your.url/nextcloud',
    'trusted_domains' =>
    array (
    0 => 'your.url:443',
    ),

    Something like this?


    I have tried several without success.

    Any ideas?

    OMV 5, Intel core i3 3225, 8GB RAM, PendriveUSB system, ZFS RaidZ 5xWD Red 4TB, 1x120GB SSD Docker

    Tomorrow you will wish you had made a backup today !!

  • I give up. I don't know what else to try. I need help with this.


    This is my current setup.


    Stack:


    .../www/nextcloud/config/config.php


    If anyone knows what I have to do to see Nextcloud from the LAN, I invite you to a beer.

    OMV 5, Intel core i3 3225, 8GB RAM, PendriveUSB system, ZFS RaidZ 5xWD Red 4TB, 1x120GB SSD Docker

    Tomorrow you will wish you had made a backup today !!

  • The LAN, it shouldn't be an issue... it's just https://your.ip:450. You shouldn't need to do any of that stuff you've done there.


    Is that not working.


    IIRC, you have some sort of set up where you can't open ports. Unfortunately this is required to access nextcloud outside the LAN.

    Air Conditioners are a lot like PC's... They work great until you open Windows.


  • this does not match. you should use either 450 or 444

    What does not match? It is copied from the guide.

    Port 444 is down.

    The answer to port 450 is: "Access through an untrusted domain"



    Is that not working.

    No...


    IIRC, you have some sort of set up where you can't open ports. Unfortunately this is required to access nextcloud outside the LAN.

    This problem I already solved. From the outside I can access Nextcloud without problem. My problem is access from the LAN.

    OMV 5, Intel core i3 3225, 8GB RAM, PendriveUSB system, ZFS RaidZ 5xWD Red 4TB, 1x120GB SSD Docker

    Tomorrow you will wish you had made a backup today !!

  • I finally got a configuration that is working for me. The problem is solved by adding the local domain in the Nextcloud configuration as follows:


    Code
    'trusted_domains' =>
    array (
    0 => '192.168.0.1:450',
    1 => 'your-url',


    DO NOT change 192.168.0.1:450 even if the actual network configuration is different, or it will not work.



    Procedure that has worked for me, with subdomain. I can access Nextcloud from the WAN with my subdomain.domain and from the LAN with the server IP.



    Deploy the same docker (the same ports) as in the macom guide and run:


    docker logs -f swag


    If there are no errors continue.


    Instead of copying the nextcloud.subfolder.conf.sample file we will copy this:


    Code
    cd / srv / dev-disk-by-label-disk1 / appdata / swag / nginx / proxy-confs
    cp nextcloud.subdomain.conf.sample nextcloud.subdomain.conf

    If we are going to use the subdomain nextcloud. we leave it as is. If we want to use a different subdomain we edit it:


    Code
    nano nextcloud.subdomain.conf


    and we change server_name nextcloud. *; to server_name your-subdomain. *; where "your-subdomain" is the subdomain you have chosen.


    Then we edit the nextcloud configuration:


    Code
    nano /srv/dev-disk-by-label-disk1/appdata/nextcloud/config/www/nextcloud/config/config.php


    And we add at the end the following (before ");":



    Important note: DO NOT CHANGE << 192.168.0.1:450 >> EVEN IF YOUR NETWORK IS DIFFERENT.

    Important note: DO NOT use the line that appears in other tutorials 'overwritehost' => 'your-subdomain.your-url',. If you do this the access to the external url is changed and the LAN cannot resolve the address. Possibly related to this https://github.com/nextcloud/user_saml/issues/413


    Restart swag and nextcloud


    docker restart swag

    docker restart nextcloud


    It should already be accessed from the WAN and from the LAN.

    OMV 5, Intel core i3 3225, 8GB RAM, PendriveUSB system, ZFS RaidZ 5xWD Red 4TB, 1x120GB SSD Docker

    Tomorrow you will wish you had made a backup today !!

    Edited 2 times, last by chente ().

  • I have not read all 42 pages of this thread. But what I have been able to read tells me that there is no clear configuration to have 1 and 2 simultaneously:

    1. Access from LAN by typing the IP, and that the address changes by itself to the domain.

    2. Access with SWAG from WAN by typing the domain.


    Correct me if I'm wrong, but I've read a huge bunch of posts and different settings to get this done ... and I still don't know if it just worked for someone. In addition, you must have Nextcloud updates. This Nextcloud installation method with NGINX is not the official one. So I don't know how the updates will affect this.


    With what I have written in the previous post you get 1 and 2, but it is not perfect. Accessing from the LAN with the IP, by not changing the address to the domain, Nextcloud does not know which domain is used in the WAN. I don't know if this will cause any problems.


    If there is any way to improve this I am all ears. The truth is that I am not very convinced by having Nextcloud installed like this, it seems to be taken with tweezers ... (it is a way of talking about my country, what I mean is that I do not know if it will be a very durable installation).

    OMV 5, Intel core i3 3225, 8GB RAM, PendriveUSB system, ZFS RaidZ 5xWD Red 4TB, 1x120GB SSD Docker

    Tomorrow you will wish you had made a backup today !!

  • Nextcloud has a level of complexity that makes it unique among service add-ons for Openmediavault. There are so many variables in its implementation based on the user’s internet provider and router setup.


    chente your yml, config, and reverse proxy files all look fine. If you are accessing Nextcloud the way you want then use it and enjoy it.

    Easy data backup: In a Scheduled Job: rsync -av --delete /srv/dev-disk-by-label-SOURCE/ /srv/dev-disk-by-label-DESTINATION/ (HT: Getting Started with OMV5)
    OMV 5 (current) - Thinkserver TS140, Nextcloud, Plex, Airsonic, Navidrome, Ubooquity, Digikam, Wetty, & Heimdall - NanoPi M4 (v.1): backups using Rsync and Rsnapshot - Odroid XU4 (Using DietPi): PiHole - hc2, xu4, Pi 3B+, Odroid H2, and VirtualBox: Testing and playing - Mac user converting to Linux, Debian 10 KDE.

  • Nextcloud has a level of complexity that makes it unique among service add-ons for Openmediavault. There are so many variables in its implementation based on the user’s internet provider and router setup.


    chente your yml, config, and reverse proxy files all look fine. If you are accessing Nextcloud the way you want then use it and enjoy it.

    You're right. Nextcloud is a complex service with many possibilities. I think you can get a lot out of it if you use it well.


    This implementation in OMV through docker is the best integrated into the system. What doesn't convince me is moving away from apache and the official installation system. It takes some weird juggling to make it work. This leads me to wonder what will happen when nextcloud evolves. It may be favorable to this installation ... or not ...


    Anyway, I agree with you again and I will start using it like that. I can access from WAN and from LAN (albeit in a bit of a strange way). But I don't see a better way without leaving OMV, and I don't want to get away from OMV ;)

    OMV 5, Intel core i3 3225, 8GB RAM, PendriveUSB system, ZFS RaidZ 5xWD Red 4TB, 1x120GB SSD Docker

    Tomorrow you will wish you had made a backup today !!

  • I didn't want to say it but I'm going to do it. At the risk of some crucifying me ^^. One possibility that has crossed my mind is a debian installation under OMV with a snap package. After all, it would be the closest thing to docker and the official installation. Also with automatic updates. Maybe it will be a way out in the future if the evolution of Nextcloud is not favorable to OMV.

    OMV 5, Intel core i3 3225, 8GB RAM, PendriveUSB system, ZFS RaidZ 5xWD Red 4TB, 1x120GB SSD Docker

    Tomorrow you will wish you had made a backup today !!

  • I didn't want to say it but I'm going to do it. At the risk of some crucifying me ^^. One possibility that has crossed my mind is a debian installation under OMV with a snap package. After all, it would be the closest thing to docker and the official installation. Also with automatic updates. Maybe it will be a way out in the future if the evolution of Nextcloud is not favorable to OMV.

    There's people who have done it. I'm not sure what their success level was or if anything else needed modified.. but it's been done.


    Personally, while nextcloud is tedious to set up that first time... Once you do it once or twice, and just take a few notes and keep them... It really sets up very simply. I can take a bare bones install with only docker installed, and have docker set up and reverse proxy'd through my domain... In about 10-15min.


    Really doesn't get much easier than that. That though, required some work on my part. Saving docker compose files, using symlinks instead of paths so I always know where my volumes need mapped and am not trying to remember or find uuid's, etc.


    Really very simple.

    Air Conditioners are a lot like PC's... They work great until you open Windows.


  • Last night I started running Nextcloud for a bit, and I realized that this setting is not optimal at all. When I configure the client for the smartphone I have to choose between local IP or WAN domain. This is a problem, if I choose one I don't have the other.


    I will have to keep looking around to see how to solve it. At the moment I can only think of a DNS server, but ... is it necessary that much?

    OMV 5, Intel core i3 3225, 8GB RAM, PendriveUSB system, ZFS RaidZ 5xWD Red 4TB, 1x120GB SSD Docker

    Tomorrow you will wish you had made a backup today !!

  • As on a armfh platform (see signature) I had to migrate from linuxserver/mariadb to webhippie/mariadb according to the guide by Morlan. Applying my weekly "docker-compose pull" I got for the first time a (brand-)new version of webhippie/mariadb. But after the "docker-compose up -d" and trying to connect to my nextcloud I get

    Code
    Internal Server Error
    The server encountered an internal error and was unable to complete your request.
    Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
    More details can be found in the server log.

    It looks as if the mariadb-container does not start.


    Any clue?

    OMV 5.6.16 Usul | omvextrasorg 5.6.2 | Kernel Linux 5.10.60-mvebu | Armbian Buster 21.08.3 | Hardware Helios 4

  • Any clue?

    Not without further information. What does the mariadb-container log say?

    You could also switch back to the linuxserver images. They seem again support armhf again.


    Last night I started running Nextcloud for a bit, and I realized that this setting is not optimal at all. When I configure the client for the smartphone I have to choose between local IP or WAN domain. This is a problem, if I choose one I don't have the other.


    I will have to keep looking around to see how to solve it. At the moment I can only think of a DNS server, but ... is it necessary that much?

    Accessing the WAN domain does not work from your home LAN? Maybe you need a new router.

  • Accessing the WAN domain does not work from your home LAN? Maybe you need a new router.

    From the results of the google searches I understood that this is a common problem. I've seen ways to solve it, some more complicated than others. But I did not know that this can be solved from the router.

    I would appreciate more information on this. What kind of router? What configuration should be applied?

    OMV 5, Intel core i3 3225, 8GB RAM, PendriveUSB system, ZFS RaidZ 5xWD Red 4TB, 1x120GB SSD Docker

    Tomorrow you will wish you had made a backup today !!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!