Posts by vmosin

version: "2"
services:
  nextcloud:
    image: ghcr.io/linuxserver/nextcloud
    container_name: nextcloud
    environment:
      - PUID=1002 #change PUID if needed
      - PGID=100  #change PGID if needed
      - TZ=Europe/Berlin #change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-uuid-5c204a65-6a30-4a36-8c58-9d0c77f8de2b/appdata/nextcloud/config:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted
      - /srv/dev-disk-by-uuid-5c204a65-6a30-4a36-8c58-9d0c77f8de2b/appdata/nextcloud/data:/data     #/srv/dev-disk-by-label-disk1 needs to be adjusted
    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=1002 #change PUID if needed
      - PGID=100  #change PGID if needed
      - MYSQL_ROOT_PASSWORD=mariadbpassword  #change password
      - TZ=Europe/Berlin #Change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-uuid-5c204a65-6a30-4a36-8c58-9d0c77f8de2b/appdata/nextclouddb:/config    #/srv/dev-disk-by-label-disk1 needs to be adjusted
    restart: unless-stopped
  swag:
    image: linuxserver/swag         #swag is the replacement for letsencrypt (see link below)
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1002 #change PUID if needed
      - PGID=100  #change PGID if needed
      - TZ=Europe/Berlin # change Time Zone if needed
      - URL=vexample.ddns.net #insert your domain name - yourdomain.url
      - SUBDOMAINS=www,
      - VALIDATION=http
      - EMAIL=vsexample@gmail.com # define email; required to renew certificate
    volumes:
      - /srv/dev-disk-by-uuid-5c204a65-6a30-4a36-8c58-9d0c77f8de2b/appdata/swag:/config  #/srv/dev-disk-by-label-disk1 needs to be adjusted
    ports:
      - 444:443
      - 81:80
    restart: unless-stopped

<?php
$CONFIG = array (
    'datadirectory' => '/data',
    'trusted_proxies' =>
  array (
    0 => 'swag',
  ),
  'overwritewebroot' => '/nextcloud',
  'overwrite.cli.url' => 'https://vexample.ddns.net/nextcloud',
  'trusted_domains' =>
  array (
    0 => 'vexample.ddns.net:443',
  ),
);

GID/UID
───────────────────────────────────────

User UID:    1002
User GID:    100
───────────────────────────────────────
Linuxserver.io version: 3.0.1-ls344
Build-date: 2024-12-14T03:34:30+00:00
───────────────────────────────────────

using keys found in /config/keys
Variables set:
PUID=1002
PGID=100
TZ=Europe/Berlin
URL=vexample.ddns.net
SUBDOMAINS=www,
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=false
VALIDATION=http
CERTPROVIDER=
DNSPLUGIN=
EMAIL=vsexample@gmail.com
STAGING=

Using Let's Encrypt as the cert provider
SUBDOMAINS entered, processing
Sub-domains processed are: www.vexample.ddns.net
E-mail address entered: vsexample@gmail.com
http validation is selected
Generating new certificate
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for vexample.ddns.net and www.vexample.ddns.net

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
  Domain: vexample.ddns.net
  Type:   connection
  Detail: example: Fetching http://vexample.ddns.net/.well-known/acme-challenge/WfLKra9H5fPggnTbhv1WuhUF4wcgSKK0DQs7c8qYVgY: Connection refused

  Domain: www.vexample.ddns.net
  Type:   dns
  Detail: DNS problem: NXDOMAIN looking up A for www.vexample.ddns.net - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for www.vexample.ddns.net - check that a DNS record exists for this domain

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
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