Problem installing nextcloud

  • Hi everybody, I followed this guide to install nextcloud in MY OMV5 on Raspberry PI4.

    I created a user named docker1, I created an account in duckdns.org, I created a subdomain, I taked the token etc. etc.

    I port forward the 80 and 443 port on the router in TCP&UDP
    I created, also, the docker-compose.yaml like this and launched it.


    I renamed the file nextcloud.subdomain.conf.sample in nextcloud.subdomain.conf, I restarted swag contenitor but don't work, here the log of swag

    Where I wrong?
    Thanks and cioa

  • geaves

    Approved the thread.
  • Pietrogramma

    Changed the title of the thread from “Problem to install nextcloud” to “Problem installing nextcloud”.
  • macom

    Approved the thread.
  • Getting the same error. I have tried the same video you used as well as the technodadlife portainer stack video. Same error both times. Tried it on a fresh install of OMV as well.

  • I didn't watch the video, but a couple things stand out to me as either not making sense or dated... I would probably start over w/ empty config and data folders when you do the below, but that's your decision. I've also never set up on a Pi, but it should be more or less the same as the linuxserver images configure the same way.


    1. A couple of your container images (line 4 and 16) are outdated in your docker compose. Unlikely it's the problem as they should be properly mirrored for now, but might as well get it right in case they ever aren't)


    nextcloud: ( linuxserver nextcloud )

    nextclouddb ( linuxserver mariadb )


    2. Your swag container doesn't look right to me... I didn't watch that video so maybe he has a reason for doing it like this, but I've never setup it up like this. Why didn't you just use the duckdns plugin? Why set the subdomain to wildcard? If you're using duckdns, that's all you can use.


    linuxserver swag


    Lines 9, 12, 13, 16, 18...


    Then redeploy.

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


  • Hello

    I went to the same problem. I went back to Letsencrypt and the certificat was issued properly.

    Some issue with the python script I guess.

    ciao

  • Hello

    I went to the same problem. I went back to Letsencrypt and the certificat was issued properly.

    Some issue with the python script I guess.

    ciao

    Worked fine for me


    Are you using a Pi4?

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


  • Quick update. I had posted a question on that same video on youtube and some had replied with this feedback (see below). That did fix my swag cert error. Now I am stuck on the "Welcome to your SWAG instance" page. Which is progress!


    KM0201 - thanks for the feedback. Will also look at your suggestions. I tried a few different videos and was getting stuck on the python error.


    Hardware: RPi 4 8GB + SSD boot.



    "This fixed it for me: https://docs.linuxserver.io/faq#libseccomp Simply install and restart container"
  • Didn't watched the video, since the guide to follow is here on the forum and it works. Nextcloud with SWAG....


    How did you forwarded the ports on the router????

    The way you have your docker-compose.yml, your ports ON THE ROUTER must be:

    80 (From Internet)---> 82 (To LAN IP of the NC/SWAG server)

    443 (From Internet)-->444 (To LAN IP of the NC/SWAG server)


    Also, if you're on subfolder (again, didn't watched the video), and you edited DUCKDNS AUTH as KM0201 said above ---^^^^^, you will reach Nextcloud by: "https:// yoursubdomain.duckdns.org/nextcloud/"


    If you did it as subdomain, it will probably error due to cert beeing created only for "SUBDOMAINS=yoursubdomain"

    Code
    - URL=yoursubdomain.duckdns.org #subdomain unique that you register on duckdns
    - SUBDOMAINS=wildcard # Or more exclusively: www,nextcloud,whatever #all this names will be certified by SWAG
    - VALIDATION=duckdns
    - DUCKDNSTOKEN=Your duckdns Token

    Then you'll reach Nextcloud as: "https://nextcloud.yoursubdomain.duckdns.org/"

  • actually it would just be yoursubdomain.duckdns.com


    no subfolder

    If the sample file used in SWAG/proxy-confs is "nextcloud.subfolder.conf" then SWAG will upstream the NEXTCLOUD to https://subdomain.duckdns.org/nextcloud/

    ;)

  • On duckdns? I didn't think duckdns allowed subfolders

    This is not duckdns. duckdns only gives the "whatever.duckdns.org" domain register.

    Then SWAG takes over and upstreams it to "whatever.duckdns.org/nextcloud" <<<--- if *.subfolder.conf is used.

    "nextcloud.whatever.duckdns.org" <<<--- if *.subdomain.conf is used.


    For clarification sake, I used that code above--^^^^ "SUBDOMAINS=wildcard" on my docker-compose and I can "https" to my RPi4 on "NEXTCLOUD,mydomain" "MOTIONEYE.mydomain", etc as long as I only have on the "SWAG/proxy-confs", the *subdomain.conf files active.(without the ".sample"

  • This is not duckdns. duckdns only gives the "whatever.duckdns.org" domain register.

    Then SWAG takes over and upstreams it to "whatever.duckdns.org/nextcloud" <<<--- if *.subfolder.conf is used.

    "nextcloud.whatever.duckdns.org" <<<--- if *.subdomain.conf is used.


    For clarification sake, I used that code above--^^^^ "SUBDOMAINS=wildcard" on my docker-compose and I can "https" to my RPi4 on "NEXTCLOUD,mydomain" "MOTIONEYE.mydomain", etc as long as I only have on the "SWAG/proxy-confs", the *subdomain.conf files active.(without the ".sample"

    I have no real need for external services other than nextcloud, so it's not something I ever really looked into it but I could have swore I read duckdns blocks subfolders somehow (admittedly, I always wondered how they did as well)

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


  • I have no real need for external services other than nextcloud, so it's not something I ever really looked into it but I could have swore I read duckdns blocks subfolders somehow (admittedly, I always wondered how they did as well)

    Well, duckdns doesn't know that your server is "serving" subfolders.

    SWAG only grabs your "duckdns.url" and "rewrites" it or better said "appends" the service your calling (creates an ALIAS, do I make any sense?!?)


    This is subfolder (only part of it):

    # 'overwritewebroot' => '/nextcloud',

    # 'overwrite.cli.url' => 'https://your-domain.com/nextcloud',



    And this is for subdomain (again, only part):

    server_name nextcloud.*; # <<<---- this is where the magic happens

    location / { 

    include /config/nginx/proxy.conf;

    set $upstream_app nextcloud;

    set $upstream_port 443;

    set $upstream_proto https;

    proxy_pass $upstream_proto://$upstream_app:$upstream_port; # <<<----  and here is the final url


    But if you don't use SWAG (or any other) reverse proxy, of course it's completely different.

    This is just some things I managed to learn, :)

  • No, it makes perfect sense and I understand what you're saying.. I just remember reading that somewhere and I always wondered how duckdns could pull that off (since they really are just redirecting).. but since it's not something I needed, it wasn't something I ever looked at.

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


  • Worked fine for me


    Are you using a Pi4?

    I have PI 3 b+ . but afterward, I run into some other issues I could not solved. trying another video of Techno Dad Now ^^ ; this is the way (of noobs like me)

Participate now!

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