Nextcloud Bad Gateway

TonyNGUYEN · Jul 24th 2022

I do not have nginx for the moment, I just follow KM0201 tuto.

Here is the stack :

version: "2.1"

services:

nextcloud:

image: ghcr.io/linuxserver/nextcloud:latest

container_name: nextcloud

##network_mode: swag_default

environment:

- PUID=998

- PGID=100

volumes:

- /srv/dev-disk-by-uuid-0d45c8f5-06ad-448b-b231-fddefcac8735/config/nextcloud/config:/config

- /srv/dev-disk-by-uuid-0d45c8f5-06ad-448b-b231-fddefcac8735/config/nextcloud/data:/data

- /etc/localtime:/etc/localtime:ro

depends_on:

- mariadb

ports:

- 450:443

restart: unless-stopped

mariadb:

image: ghcr.io/linuxserver/mariadb:latest

container_name: nextclouddb

##network_mode: swag_default

environment:

- PUID=998

- PGID=100

- MYSQL_ROOT_PASSWORD=XXXXX

volumes:

- /srv/dev-disk-by-uuid-0d45c8f5-06ad-448b-b231-fddefcac8735/config/nextclouddb:/config

- /etc/localtime:/etc/localtime:ro

restart: unless-stopped

Soma · Jul 24th 2022

Quote from KM0201

PUID=1000

Quote from TonyNGUYEN

PUID=998

This shows that you didn't follow his tutorial properly

HannesJo · Jul 24th 2022

That container uses nginx. So in

/srv/dev-disk-by-uuid-0d45c8f5-06ad-448b-b231-fddefcac8735/config/nextcloud/config

you should find some logs of nginx and php.

Why user 998?

Edit: corrected the path.

TonyNGUYEN · Jul 24th 2022

Hi Soma,

I think my PUID and PGID are correct :

Hi HannesJo,

You are corretc, I follow the path and I see logs. So I have a problem in config .php wich come from a french tuto that does not work for me.

So I decide to follow MK0201 tuto. Do you know how I can get a correct config.php ?

Agricola · Jul 24th 2022

As your screenshot shows 998 is the uid to your admin user which should only be used in connection with your web-gui login. You need to use a regular, unprivileged user, created by you in the Users section of the gui, the first being 1000. This is the GUID you should be using. You probably got 998 from a DBTech video.

TonyNGUYEN · Jul 24th 2022

Hi Agricola,

Thanks for the informations. I have updated the stack but still have the same error.

PS : french tuto is from GuiPoM

KM0201 · Jul 24th 2022

Quote from TonyNGUYEN

Hi Soma,
I think my PUID and PGID are correct :

You literally failed in the first paragraph...

Quote

Everything that starts with a # needs to be adjusted for your system and then the # erased. Nothing other than those lines need to be changed despite what you've seen in other tutorials. DO NOT ADJUST THE ##network_mode at this time. That will come later when we set up the proxy. Again, do not mix this with other tutorials, you'll just fail and be frustrated.

Delete your config and data folders

Stop followuing dbtech tutorials

Create a user in the webUI and get a proper PUID (probably going to be 1000 since it's likely your first user)

Follow that post.

It 100% works

TonyNGUYEN · Jul 24th 2022

Hi KM0201,

I deleted all folders and started from scratch.

It works well but at the last stage (23), I get the following error :

KM0201 · Jul 25th 2022

Did you get a certifIcate? I assume not. What error did swag give you when you tried to pull a cert.

TonyNGUYEN · Jul 25th 2022

Hi KM0201,

I see no error in swag log :

cont-init: info: /etc/cont-init.d/99-custom-files exited 0

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service legacy-services: starting

services-up: info: copying legacy longrun cron (no readiness notification)

services-up: info: copying legacy longrun fail2ban (no readiness notification)

services-up: info: copying legacy longrun nginx (no readiness notification)

services-up: info: copying legacy longrun php-fpm (no readiness notification)

s6-rc: info: service legacy-services successfully started

s6-rc: info: service 99-ci-service-check: starting

[ls.io-init] done.

s6-rc: info: service 99-ci-service-check successfully started

Server ready

s6-rc: info: service s6rc-oneshot-runner: starting

s6-rc: info: service s6rc-oneshot-runner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service 00-legacy: starting

s6-rc: info: service 00-legacy successfully started

s6-rc: info: service fix-attrs successfully started

s6-rc: info: service legacy-cont-init: starting

cont-init: info: running /etc/cont-init.d/01-envfile

cont-init: info: /etc/cont-init.d/01-envfile exited 0

cont-init: info: running /etc/cont-init.d/02-tamper-check

cont-init: info: /etc/cont-init.d/02-tamper-check exited 0

cont-init: info: running /etc/cont-init.d/10-adduser

usermod: no changes

-------------------------------------

_ ()

| | ___ _ __

| | / __| | | / \

| | \__ \ | | | () |

|_| |___/ |_| \__/

Brought to you by linuxserver.io

-------------------------------------

To support the app dev(s) visit:

Certbot: https://supporters.eff.org/donate/support-work-on-certbot

To support LSIO projects visit:

https://www.linuxserver.io/donate/

-------------------------------------

GID/UID

-------------------------------------

User uid: 1000

User gid: 100

-------------------------------------

cont-init: info: /etc/cont-init.d/10-adduser exited 0

cont-init: info: running /etc/cont-init.d/20-config

cont-init: info: /etc/cont-init.d/20-config exited 0

cont-init: info: running /etc/cont-init.d/30-keygen

cont-init: info: /etc/cont-init.d/30-keygen exited 0

cont-init: info: running /etc/cont-init.d/50-config

using keys found in /config/keys

Variables set:

0

PGID=100

TZ=

URL=xxxxxxxxxx.duckdns.org

SUBDOMAINS=wildcard

EXTRA_DOMAINS=

ONLY_SUBDOMAINS=false

VALIDATION=duckdns

CERTPROVIDER=

DNSPLUGIN=

EMAIL=xxxxxxxxxx@gmail.com

STAGING=

Using Let's Encrypt as the cert provider

SUBDOMAINS entered, processing

Wildcard cert for xxxxxxxxxx.duckdns.org will be requested

E-mail address entered: xxxxxxxxxx@gmail.com

duckdns validation is selected

the resulting certificate will only cover the subdomains due to a limitation of duckdns, so it is advised to set the root location to use http://www.subdomain.duckdns.org

Certificate exists; parameters unchanged; starting nginx

cont-init: info: /etc/cont-init.d/50-config exited 0

cont-init: info: running /etc/cont-init.d/60-renew

The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am).

cont-init: info: /etc/cont-init.d/60-renew exited 0

cont-init: info: running /etc/cont-init.d/70-templates

cont-init: info: /etc/cont-init.d/70-templates exited 0

cont-init: info: running /etc/cont-init.d/90-custom-folders

cont-init: info: /etc/cont-init.d/90-custom-folders exited 0

cont-init: info: running /etc/cont-init.d/99-custom-files

[custom-init] no custom files found exiting...

cont-init: info: /etc/cont-init.d/99-custom-files exited 0

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service legacy-services: starting

services-up: info: copying legacy longrun cron (no readiness notification)

services-up: info: copying legacy longrun fail2ban (no readiness notification)

services-up: info: copying legacy longrun nginx (no readiness notification)

services-up: info: copying legacy longrun php-fpm (no readiness notification)

s6-rc: info: service legacy-services successfully started

s6-rc: info: service 99-ci-service-check: starting

[ls.io-init] done.

s6-rc: info: service 99-ci-service-check successfully started

Server ready

KM0201 · Jul 25th 2022

Quote from TonyNGUYEN

Hi KM0201,
I see no error in swag log :
cont-init: info: /etc/cont-init.d/99-custom-files exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun cron (no readiness notification)
services-up: info: copying legacy longrun fail2ban (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun php-fpm (no readiness notification)
s6-rc: info: service legacy-services successfully started
s6-rc: info: service 99-ci-service-check: starting
[ls.io-init] done.
s6-rc: info: service 99-ci-service-check successfully started
Server ready
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service 00-legacy: starting
s6-rc: info: service 00-legacy successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/01-envfile
cont-init: info: /etc/cont-init.d/01-envfile exited 0
cont-init: info: running /etc/cont-init.d/02-tamper-check
cont-init: info: /etc/cont-init.d/02-tamper-check exited 0
cont-init: info: running /etc/cont-init.d/10-adduser
usermod: no changes

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/

Brought to you by linuxserver.io
-------------------------------------

To support the app dev(s) visit:
Certbot: https://supporters.eff.org/donate/support-work-on-certbot

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid: 1000
User gid: 100
-------------------------------------

cont-init: info: /etc/cont-init.d/10-adduser exited 0
cont-init: info: running /etc/cont-init.d/20-config
cont-init: info: /etc/cont-init.d/20-config exited 0
cont-init: info: running /etc/cont-init.d/30-keygen
cont-init: info: /etc/cont-init.d/30-keygen exited 0
cont-init: info: running /etc/cont-init.d/50-config
using keys found in /config/keys
Variables set:
0
PGID=100
TZ=
URL=xxxxxxxxxx.duckdns.org
SUBDOMAINS=wildcard
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=false
VALIDATION=duckdns
CERTPROVIDER=
DNSPLUGIN=
EMAIL=xxxxxxxxxx@gmail.com
STAGING=

Using Let's Encrypt as the cert provider
SUBDOMAINS entered, processing
Wildcard cert for xxxxxxxxxx.duckdns.org will be requested
E-mail address entered: xxxxxxxxxx@gmail.com
duckdns validation is selected
the resulting certificate will only cover the subdomains due to a limitation of duckdns, so it is advised to set the root location to use http://www.subdomain.duckdns.org
Certificate exists; parameters unchanged; starting nginx
cont-init: info: /etc/cont-init.d/50-config exited 0
cont-init: info: running /etc/cont-init.d/60-renew
The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am).
cont-init: info: /etc/cont-init.d/60-renew exited 0
cont-init: info: running /etc/cont-init.d/70-templates
cont-init: info: /etc/cont-init.d/70-templates exited 0
cont-init: info: running /etc/cont-init.d/90-custom-folders
cont-init: info: /etc/cont-init.d/90-custom-folders exited 0
cont-init: info: running /etc/cont-init.d/99-custom-files
[custom-init] no custom files found exiting...
cont-init: info: /etc/cont-init.d/99-custom-files exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun cron (no readiness notification)
services-up: info: copying legacy longrun fail2ban (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun php-fpm (no readiness notification)
s6-rc: info: service legacy-services successfully started
s6-rc: info: service 99-ci-service-check: starting
[ls.io-init] done.
s6-rc: info: service 99-ci-service-check successfully started
Server ready

Display More

Sorry I'm exhausted I need to get some sleep. I'll try to take a look at this in a few hours if you're on later tonight I'll probably be in the discord channel if you want some help

TonyNGUYEN · Jul 25th 2022

Thank you KM0201.

Keep safe

Agricola · Jul 25th 2022

Your cert looks good. Your problem probably lies somewhere in your proxy configuration. look at this [How-To] under the Configuration of Proxy section to find your .conf and config.php files. Post those in a code box - but hide your passwords, etc.

Agricola · Jul 25th 2022

You probably should hide your username, dbpassword, and domain. Delete the post above and copy/paste the file in a code box using the </> button in the menu bar above, but hide that sensitive information.

Code

Code box like this.

TonyNGUYEN · Jul 25th 2022

Hi Agricola,

Do you think I must change dbuser and dbpassword ?

PHP

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'oczc9zwun5q1',
  'passwordsalt' => 'lPbzJeWpOLD9AiNGlTaalbMaW9WVuw',
  'secret' => 'dnUkbUEr3CPIAY+YCQAg12siS9C6YRRIDqxO9sfJeHdj+/3a',
  'trusted_domains' =>
  array (
    0 => '192.168.1.23:450',
    1 => 'nextcloud.xxxxxx.duckdns.org',
  ),
  'dbtype' => 'mysql',
  'version' => '24.0.3.2',
  'overwrite.cli.url' => 'https://192.168.1.23:450',
  'dbname' => 'nextcloud',
  'dbhost' => 'nextclouddb',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'oc_admin',
  'dbpassword' => '6QDuG48jyJ68mhLxXWZJw1wKNDCZuZ',
  'installed' => true,
  'overwrite.cli.url' => 'https://nextcloud.xxxxxx.duckdns.org',
  'overwriteprotocol' => 'https',
  'default_phone_region' => 'FR',
);

Display More

Agricola · Jul 25th 2022

If you do you will have to reconfigure your compose file and delete your config folder and rerun your swag cert. make sure you have a strong password on your nextcloud login.

TonyNGUYEN · Jul 25th 2022

dbuser and dbpassword were set by default.

I have change accordint to my stack but have still the same problem.

Hereafter my nextcloud.subdomain.conf :

Code

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;
        include /config/nginx/resolver.conf;
        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;
    }
}

Display More

TonyNGUYEN · Jul 25th 2022

and my config.php :

PHP

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'oczc9zwun5q1',
  'passwordsalt' => 'lPbzJeWpOLD9AiNGlTaalbMaW9WVuw',
  'secret' => 'dnUkbUEr3CPIAY+YCQAg12siS9C6YRRIDqxO9sfJeHdj+/3a',
  'trusted_domains' =>
  array (
    0 => '192.168.1.23:450',
    1 => 'nextcloud.xxxxxx.duckdns.org',
  ),
  'dbtype' => 'mysql',
  'version' => '24.0.3.2',
  'overwrite.cli.url' => 'https://192.168.1.23:450',
  'dbname' => 'nextcloud',
  'dbhost' => 'nextclouddb',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'oc_admin',
  'dbpassword' => '6QDuG48jyJ68mhLxXWZJw1wKNDCZuZ',
  'installed' => true,
  'overwrite.cli.url' => 'https://nextcloud.xxxxxx.duckdns.org',
  'overwriteprotocol' => 'https',
  'default_phone_region' => 'FR',
);

Display More

Agricola · Jul 25th 2022

Are you not able to reach your Nextcloud login page at nextcloud.your-subdomain.duckdns.org ?

TonyNGUYEN · Jul 25th 2022

I can't reach my page :

Nextcloud Bad Gateway

Participate now!

Similar Threads

Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

Let's encrypt doesn't work with MyFritz and Nextcloud

OMV5 Installation issue

Nextcloud and Airsonic with Letsencrypt: Airsonic redirect to Nextcloud always!

Problem with Letsencrypt and Nextcloud Configuration on Docker.

Tags