nextcloud bad gateway 502, i screwed up.

KM0201 · 18. Januar 2022

https://docs.linuxserver.io/general/swag

KM0201 · 18. Januar 2022

Zitat von HackitZ

here it is,

Code

version '2'
services;
   nextcloud:
    image: linuxserver/nextcloud
    container_name: Nextcloud
    environment:
      - PUID=1004
      - PGID=100 
      - TZ=America/New_York
      - default_phone_region=CA
    volumes:
      - /srv/dev-disk-by-label-Media/AppData/Nextcloud/config:/config
      - /srv/dev-disk-by-label-Media/AppData/Nextcloud/data:/data
    depends_on:
      - mariadb
    ports:
      - 450:443 
    restart: unless-stopped
  mariadb:
    image: linuxserver/mariadb
    container_name: Nextclouddb
    environment:
      - PUID=1004 
      - PGID=100
      - MYSQL_ROOT_PASSWORD=pass 
      - TZ=America/New_York
    volumes:
      - /srv/dev-disk-by-label-Media/AppData/Nextclouddb:/config 
    restart: unless-stopped
  letsencrypt:
    image: linuxserver/letsencrypt
    container_name: Letsencrypt
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1004
      - PGID=100
      - TZ=America/New_York
      - URL=cloud.kicks-ass.net
      - DNSPLUGIN=blaize
      - SUBDOMAINS=www,nextcloud
      - VALIDATION=http
      - EMAIL=my@email.com # define email; required to renew certificate
    volumes:
      - /srv/dev-disk-by-label-Media/AppData/Letsencrypt:/config
    ports:
      - 446:443
      - 81:80
    restart: unless-stopped

Alles anzeigen

I just saw this post... Stop using letsencrypt, and use swag as I linked you a minute ago. linuxserver/letsencrypt is deprecated, and has been for over a year.

https://hub.docker.com/r/linuxserver/letsencrypt

Soma · 18. Januar 2022

Zitat von KM0201

I just saw this post... Stop using letsencrypt, and use swag as I linked you a minute ago. linuxserver/letsencrypt is deprecated, and has been for over a year.

https://hub.docker.com/r/linuxserver/letsencrypt

That's the whole idea of this, make the changes from letsencrypt to SWAG.

Due to lack of time of the OP, it was postponed.

But, IIRC, if there's already a certificate created with letsencrypt, it will be reused by changing to SWAG.

HackitZ

If you decided to go through, do it 1 step at time.

If something goes wrong, it will be easy to revert.

Acoording to your YML, your configs live in /srv/dev-disk-by-label-Media/AppData/.

Now, all it's needed is the full path where you have your docker-compose.yml

After you post it, it will be easy to make the changes.

HackitZ · 18. Januar 2022

so i just edited my yml file. when i run it i get an error;

Code

ERROR: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:43918->[::1]:53: read: connection refused

over on git, they suggest to wait and run it again in a few minutes. i've tried this several times. still the same error. it seems this is an old issue, guess this is part in parcel when your late to the game.

has anyone had this issue and resolved?

tired restarting docker, still the same.

service docker restart

Agricola · 18. Januar 2022

I have have this kind of problem a few times, where I cannot get Docker and/or Portainer to re-install. Go into the OMV-Extras tab and select apt clean from the Updates pull-down. When the process finishes try to install your Docker from OMV-Extras.

HackitZ · 18. Januar 2022

Ill close this thread.

I have decided to just install nextcloud on my new server running omv6.

but my port 80 is blocked by my isp, so i need to wait until they add dyndns to the list of valid plugin names (i've put in a request) or change my dns provider.

i'm pretty much out of time for today.

adding info for someone else using dyndns. this is from github linuxserer/swag

There's no certbot plugin for dyndns so we can't add support for it. You're limited to http validation.

Jetzt mitmachen!