https for all my subdomains wont work

fraxor · 1. Dezember 2019

Hi Forum,

i had this setup 2 weeks ago up and running. Since i had a HW failure, i needed a new MainBoard, CPU and RAM.
Now to my problem... i cant reach to my Nextcloud, Bitwarden and GiTea over the internet via https.
All the Containers come up without problem. Logs shows no error...
I deleted all the Containers and the volumes to see if i can solve the error but nothing.

i'm desperate searching the error since 1 week allredy...

DuckDNS

Code: docker-compose.yml

version: "2"
services:
  duckdns:
    image: linuxserver/duckdns
    container_name: duckdns
    env_file:
      - ./duckdns.env
    volumes:
      - /var/docker/appdata/duckdns/:/config
    restart: unless-stopped

Code: duckdns.env

PUID=1001
PGID=100
TZ=Europe/Zurich
SUBDOMAINS=mysubdomain
TOKEN=TOKEN_FROM_DNS_SERVICE_PROVIDER

Letsencrypt

Code: docker-compose.yml

version: "2"
services:
  letsencrypt:
    image: linuxserver/letsencrypt
    container_name: letsencrypt
    cap_add:
      - NET_ADMIN
    env_file:
      - ./letsencrypt.env
    volumes:
      - /var/docker/appdata/letsencrypt/:/config
    depends_on:
      - duckdns
    networks: 
      - proxy
    ports:
      - 444:443
    restart: unless-stopped


networks:
  proxy:

Alles anzeigen

Code: letsencrypt.env

PUID=1001
PGID=100
TZ=Europe/Zurich
URL=mysubdomain.duckdns.org
SUBDOMAINS=wildcard
VALIDATION=duckdns
DUCKDNSTOKEN=TOKEN_FROM_DNS_SERVICE_PROVIDER
EMAIL=EMAIL@EMAIL.COM

NextCloud

Code: docker-compose.yml

version: "2"
services:
  nextcloud:
    image: linuxserver/nextcloud
    container_name: nextcloud
    environment:
      - PUID=1001
      - PGID=100
      - TZ=Europe/Zurich
    volumes:
      - /var/docker/appdata/nextcloud/config:/config
      - /sharedfolders/nextcloud/:/data
    ports:
      - 445:443
      - 82:80
    restart: unless-stopped


networks:
    default:
        external:
            name: letsencrypt_proxy

Alles anzeigen

I did also the Modification on the Letsencrypt-ReverseProxy-Conf and on the Nextcloud Conig.php
looks like this:

PHP

<?php
$CONFIG = array (
  'trusted_domains' =>
  array (
    0 => '192.168.1.130:445',
    1 => 'nextcloud.mysubdomain.duckdns.org',
  ),
  'trusted_proxies' => ['letsencrypt'],
  'overwrite.cli.url' => 'https://nextcloud.mysubdomain.duckdns.org/',
  'overwritehost' => 'nextcloud.mysubdomain.duckdns.org',
  'overwriteprotocol' => 'https',
  ...
);

Alles anzeigen

Code: nextcloud.subdomain.conf

server {
    listen 443 ssl;
    listen [::]:443 ssl;


    server_name nextcloud.*;


    include /config/nginx/ssl.conf;


    client_max_body_size 0;


    location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_nextcloud nextcloud;
        proxy_max_temp_file_size 2048m;
        proxy_pass https://$upstream_nextcloud:443;
    }
}

Alles anzeigen

many Thanks for the help!

Regards
etfraxor

Morlan · 1. Dezember 2019

I'm not familiar with the network config in your letsencrypt setup:

Code

networks:
  proxy:

Maybe try also using the external network arg as in your nextcloud config. You need to manually create the network before (what you probably already know).

Code

networks:
    default:
        external:
            name: letsencrypt_proxy

fraxor · 1. Dezember 2019

Hi Morlan,

thx for your hint.
normally on my way when I execute the docker-compose up -d then this will create the network lets encrypt_proxy

When I inspect the docker network, then letsencrypt and nextcloud container are on the same network.

I think that the problem is on the letsencrypt container. Because by don't activate the reverse proxy-conf on the nginx, and don't make the modification on the config.php of nextcloud, Nextcloud is working with the URL: https://192.168.1.x:445

Morlan · 1. Dezember 2019

What error message to you get? The nginx "welcome to our server" or something else?

The network part is important that letsencrypt and nextcloud can commicate over the docker dns-service. But when inspect shows them in the same network this seems fine.

In the past this argument in the nextcloud.subdomain.conf caused a problem on my machine. Maybe try to comment it out.

Zitat von fraxor

proxy_max_temp_file_size 2048m;

Also as a sidenote its recommended practice to use the definitive paths like /srv/dev-disk-by-label-... as a path to your bind mount instead of the /sharedfolder/path

Zitat von fraxor

volumes:
- /var/docker/appdata/nextcloud/config:/config
- /sharedfolders/nextcloud/:/data

fraxor · 1. Dezember 2019

Morlan,
you know what?! i could solve it...
I created a new Subdomain on DuckDNS and this made the trick...

everything was the same...
maybe with the change of my machine and stuff... the certificate or something else broke.

well... now I'm happy again!

Thanks for your time!

Jetzt mitmachen!