Nextcloud, letsencrypt, welcome to our server message

[ljt]

Hi all,

 

Followed the tutorial from Spaceinvaderone to the letter to get Nextcloud working with Duckdns, my own domain and letsencrypt.

When I go to my domain I only see the message Welcome to our server. There is a certificate signed by Letsencrypt so that part is working.

 

Here are my configs:

 

config.php

 

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'ocl2txj38u82',
  'passwordsalt' => 'XXXXXXXXXXXXXXXXXXXXXXX',
  'secret' => 'XXXXXXXXXXXXXXXXXXXXXXXXXXX',
  'trusted_domains' =>
  array (
    0 => 'xxx.xxx.xxx.xxx:xxx',
    1 => 'cloud.domain.eu',
  ),
  'trusted_proxies' => ['letsencrypt'],
  'overwrite.cli.url' => 'https://cloud.domain.eu',
  'overwritehost' => 'cloud.domain.eu',
  'overwriteprotocol' => 'https',
  'dbtype' => 'mysql',
  'version' => '18.0.4.2',
  'dbname' => 'nextcloud',
  'dbhost' => 'xxx.xxx.xxx.xxx:xxxx',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'nextcloud',
  'dbpassword' => 'Topsecret',
  'installed' => true,
);

 

nextcloud.subdomain.conf

 

# assuming this container is called "letsencrypt", edit your nextcloud container's config
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
#  'trusted_proxies' => ['letsencrypt'],
#  'overwrite.cli.url' => 'https://nextcloud.your-domain.com/',
#  'overwritehost' => 'nextcloud.your-domain.com',
#  'overwriteprotocol' => 'https',
#
# Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this:
#  array (
#    0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
#    1 => 'nextcloud.your-domain.com',
#  ),

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_app nextcloud;
        set $upstream_port 443;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_max_temp_file_size 2048m;
    }
}

 

 

Checked it multiple times. I dont know where to look anymore.

 

Anyone can help me with this?

[Mathervius]

Maybe try using your IP instead of the hostname

 set $upstream_app nextcloud;

On my server I always have to use the IP. I'm sure this could be fixed somewhere but I use a static IP and it's no issue for me.

[ljt]

Tried it but didnt work.

 

Will try to redo everything. Maybe that will resolve it.

[ljt]

OK so for anyone  else having troubles I managed to fix it in a different way:

 

1) removed everything I did in the spaceinvader tutorial (configs, containers...) execpt the mariadb docker

2) Added the nextcloud docker and config it

3) Verified that nextcloud is working with local ip -> ok

4) add nginxproxymanager docker from jlesage

5) Add host in nginxproxymanager

 

Make sure the ports for 80 and 443 are forwarded ( see spaceinvaderone tutorial)

Nginxproxymanager needs that for the certificate.

 

Nginxproxymanager is just click and go. Add correct IP and ports, set SSL to on and off you go.

 

And make sure Nextcloud is not forwarding HTTP to HTTPS, it will give you an error. Nginxproxymanager is in charge of the https thing.

In the config.php in Nextcloud I changed this: 'overwrite.cli.url' => 'https://cloud.domain.eu',  INTO this: 'overwrite.cli.url' => 'http://cloud.domain.eu',

 

 

 

[Xylem59]

On 5/19/2020 at 4:42 AM, ljt said:

OK so for anyone  else having troubles I managed to fix it in a different way:

 

1) removed everything I did in the spaceinvader tutorial (configs, containers...) execpt the mariadb docker

2) Added the nextcloud docker and config it

3) Verified that nextcloud is working with local ip -> ok

4) add nginxproxymanager docker from jlesage

5) Add host in nginxproxymanager

 

Make sure the ports for 80 and 443 are forwarded ( see spaceinvaderone tutorial)

Nginxproxymanager needs that for the certificate.

 

Nginxproxymanager is just click and go. Add correct IP and ports, set SSL to on and off you go.

 

And make sure Nextcloud is not forwarding HTTP to HTTPS, it will give you an error. Nginxproxymanager is in charge of the https thing.

In the config.php in Nextcloud I changed this: 'overwrite.cli.url' => 'https://cloud.domain.eu',  INTO this: 'overwrite.cli.url' => 'http://cloud.domain.eu',

 

 

 

Can you provide more detail on how you did it please?

[Xylem59]

On 5/19/2020 at 4:42 AM, ljt said:

OK so for anyone  else having troubles I managed to fix it in a different way:

 

1) removed everything I did in the spaceinvader tutorial (configs, containers...) execpt the mariadb docker

2) Added the nextcloud docker and config it

3) Verified that nextcloud is working with local ip -> ok

4) add nginxproxymanager docker from jlesage

5) Add host in nginxproxymanager

 

Make sure the ports for 80 and 443 are forwarded ( see spaceinvaderone tutorial)

Nginxproxymanager needs that for the certificate.

 

Nginxproxymanager is just click and go. Add correct IP and ports, set SSL to on and off you go.

 

And make sure Nextcloud is not forwarding HTTP to HTTPS, it will give you an error. Nginxproxymanager is in charge of the https thing.

In the config.php in Nextcloud I changed this: 'overwrite.cli.url' => 'https://cloud.domain.eu',  INTO this: 'overwrite.cli.url' => 'http://cloud.domain.eu',

 

 

 

This is what I have but not working... so far.

I have port 80 forwarded to 180, and 443 to 1443.

Any help please!

[serverdoc]

I had the same issue with the "welcome to our server" message and found a potential solution for some:

 

When I edited the nextcloud subdomain ".conf" sample file with Notepad++, ".txt" was unknowingly added to the end of the file by Notepad++. It wasn't until I discovered this while viewing the file in another text editor and removed it where it no longer gave the "welcome to our server" and worked as expected.