nexcloud witch manual ?

sterremos · 19. Februar 2021

This weekend i want to try to install netcloud, if i am looking at the forum and you tube are the different ways to instal it.

From very simple to very complicate it, there are many ways i see.

So i saw the this manual, where i think that i can manage it

Can i use it and will it be working, our do i have to use a other manual, i am not keen with the linux commandos

Trying to deploy NextCloud on a fresh install of OMV 5.x

Ron

macom · 19. Februar 2021

Which DynDNS provider are you using?

sterremos · 19. Februar 2021

hi Macon,

i have now DuckDNS installed and its working.

Its going well now with OMV , and learning a lot.:-)

new4u · 19. Februar 2021

https://www.linuxbabe.com/ubun…tu-20-04-nginx-lemp-stack

That worked for me.

Carsten Rieger also offers instructions and a script:

https://www.c-rieger.de/nextcloud-installationsanleitung/

https://www.c-rieger.de/nextcl…ion-mit-nur-einem-skript/

macom · 19. Februar 2021

Zitat von sterremos

i have now DuckDNS installed and its working.

RE: Nextcloud Bad Gateway

sterremos · 20. Februar 2021

i am there almost, the Stacker build went well, but have some issue, how do i connect it with lan connection?

it won't start for now, i have the next message in Swag.

What must i do >

Code

 -1 }">

 -1 }">   Domain: www.www.sterremos.duckdns.org
 -1 }">   Type:   connection
 -1 }">   Detail: Fetching
 -1 }">   http://www.www.sterremos.duckdns.org/.well-known/acme-challenge/3AReYt11QrfHYCECeNTt14rWgJUz_9XhbSmFnTVjwkQ:
 -1 }">   Timeout during connect (likely firewall problem)
 -1 }">

 -1 }">   To fix these errors, please make sure that your domain name was
 -1 }">   entered correctly and the DNS A/AAAA record(s) for that domain
 -1 }">   contain(s) the right IP address. Additionally, please check that
 -1 }">   your computer has a publicly routable IP address and that no
 -1 }">   firewalls are preventing the server from communicating with the
 -1 }">   client. If you're using the webroot plugin, you should also verify
 -1 }">   that you are serving files from the webroot path you provided.
 -1 }">
ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

and this is the stack,

version: "2"
services:
  nextcloud:
    image: ghcr.io/linuxserver/nextcloud
    container_name: nextcloud
    environment:
      - PUID=1000
      - PGID=100
      - TZ=Europe/Amsterdam
    volumes:
      -  /srv/dev-disk-by-label-Nas/Ron/Appdata/nextcloud/config:/config
      -  /srv/dev-disk-by-label-Nas/Ron/Appdata/nextcloud/data:/data
    depends_on:
      - mariadb
#    ports: # uncomment this and the next line if you want to bypass the proxy
#      - 450:443
    restart: unless-stopped
  mariadb:
    image: ghcr.io/linuxserver/mariadb
    container_name: nextclouddb
    environment:
      - PUID=1000
      - PGID=100 
      - MYSQL_ROOT_PASSWORD=XXXXX
      - TZ=Europe/Amsterdam
    volumes:
      -  /srv/dev-disk-by-label-Nas/Ron/Appdata/nextclouddb:/config
    restart: unless-stopped
  swag:
    image: linuxserver/swag
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=100
      - TZ=Europe/Amsterdam
      - URL=www.sterremos.duckdns.org
      - SUBDOMAINS=www,
      - VALIDATION=http
      - EMAIL=sterremos@gmail.com
    volumes:
     -  /srv/dev-disk-by-label-Nas/Ron/Appdata/Swag:/config
    ports:
      - 444:443
      - 81:80
    restart: unless-stopped

Alles anzeigen

macom · 20. Februar 2021

Zitat von sterremos

To fix these errors, please make sure that your domain name was
-1 }"> entered correctly and the DNS A/AAAA record(s) for that domain
-1 }"> contain(s) the right IP address. Additionally, please check that
-1 }"> your computer has a publicly routable IP address and that no
-1 }"> firewalls are preventing the server from communicating with the
-1 }"> client.

and check the port forwarding in your router.

and here

https://blog.linuxserver.io/20…t-mapping-and-forwarding/

sterremos · 20. Februar 2021

i am struggling the hole night, its must be simple i think, i still get the next issue, and it must be wright in the docker

and its stange, because Duckdns is working

Code

 -1 }">   Domain: www.sterremos.duckdns.org
 -1 }">   Type:   unauthorized
 -1 }">   Detail: Incorrect TXT record "" found at
 -1 }">   _acme-challenge.www.sterremos.duckdns.org
 -1 }">

 -1 }">   To fix these errors, please make sure that your domain name was
 -1 }">   entered correctly and the DNS A/AAAA record(s) for that domain
 -1 }">   contain(s) the right IP address.
 -1 }">
ERROR: Cert does not exist! Please see the validation error above. Make sure your DUCKDNSTOKEN is correct.

Alles anzeigen

image: linuxserver/swag

container_name: swag

cap_add:

- NET_ADMIN

environment:

- PUID=1000

- PGID=100

- TZ=Europe/Amsterdam

- URL=www.sterremos.duckdns.org

- SUBDOMAINS=

- VALIDATION=Duckdns

- TOKEN=xxxxx

- EMAIL=sterremos@gmail.com

volumes:

- /srv/dev-disk-by-label-Nas/Ron/Appdata/Swag:/config

ports:

- 444:443

- 81:80

restart: unless-stopped

macom · 21. Februar 2021

I removed the token in your post. You should get a new one. You should not make the token public.

When I put sterremos.duckdns.org in my browser I end up on your OMV login page. That means you did the port forwarding on your router from port 80 to 80. For the compose file to work you need to forward port 80 (wan) to port 81 (lan).

In the guide I linked for duckdns the environment variables are like this:

Code

      - DNSPLUGIN=duckdns
      - URL=duckdns.org
      - DUCKDNSTOKEN=**YOUR_TOKEN
      - SUBDOMAINS=**YOUR_SUB_DOMAIN
      - ONLY_SUBDOMAINS=true
      - VALIDATION=http
      - EMAIL=**YOUR_EMAIL

sterremos · 21. Februar 2021

Thanks, its was late yesterday, and indeed not well from me.

i wil send a PM

KM0201 · 21. Februar 2021

Code

image: linuxserver/swag

container_name: swag

cap_add:

- NET_ADMIN

environment:

- PUID=1000

- PGID=100

- TZ=Europe/Amsterdam

- URL=www.sterremos.duckdns.org

- SUBDOMAINS=

- VALIDATION=Duckdns

- TOKEN=xxxxx

- EMAIL=sterremos@gmail.com

volumes:

- /srv/dev-disk-by-label-Nas/Ron/Appdata/Swag:/config

ports:

- 444:443

- 81:80

restart: unless-stopped

Alles anzeigen

sterremos where did you get that docker-compose ? That isn't even close to right for duckdns.

sterremos · 21. Februar 2021

KM0201. i do not know anymore, i started at the tube nextcloud in 6 minutes.

so i have update it now,

container_name: swag

cap_add:

- NET_ADMIN

environment:

- PUID=1000

- PGID=100

- TZ=Europe/Amsterdam

- DNSPLUGIN=duckdns

- URL=duckdns.org

- DUCKDNSTOKEN=XXXXXXXXX

- SUBDOMAINS=sterremos

- ONLY_SUBDOMAINS=true

- VALIDATION=http

- EMAIL=sterremos@XXXXX

Have at monent nextcloud working on LAN access 192.168.50.160:450. not through mobile and duckDNS yet.

so its going well.

Nextcloud is also very slow at the moment

Ron

KM0201 · 21. Februar 2021

Zitat von sterremos

KM0201. i do not know anymore, i started at the tube nextcloud in 6 minutes.
so i have update it now,

container_name: swag
cap_add:
- NET_ADMIN
environment:
- PUID=1000
- PGID=100
- TZ=Europe/Amsterdam
- DNSPLUGIN=duckdns
- URL=duckdns.org
- DUCKDNSTOKEN=XXXXXXXXX
- SUBDOMAINS=sterremos
- ONLY_SUBDOMAINS=true
- VALIDATION=http
- EMAIL=sterremos@XXXXX

Have at monent nextcloud working on LAN access 192.168.50.160:450. not through mobile and duckDNS yet.
so its going well.

Nextcloud is also very slow at the moment

Ron

Alles anzeigen

It's extremely slow at first... if you've got it working local... then it's probably a routing issue.. have you forwarded the proper ports in your router? You'll also need to make the edits to configuration files I mentioned in the bad gateway thread.

nexcloud witch manual ?

Jetzt mitmachen!

Tags