[SOLVED] Bad Gateway (502) - Nginx Proxy Manager with SSL certificate does not work

I am trying to use Nginx Proxy Manager as Reverse Proxy. In Nginx Proxy Manager I have configured a Subdomain (https://baas.example.com) to the traefik container and its port (8000) as http://localhost:8000. I have created a SSL certificate in NPM for the subdomain pointing to appwrite/traefik.

I have tried to follow the visible instructions from Steven on Medium.com. Unfortunately it is for members only.

• NPM is now added to the same network as appwrite-traefik container
• I have added a docker-compose.override.yml with

version: '3'

services:
  traefik:
    image: traefik:2.7
    container_name: appwrite-traefik
    command:
      - --providers.file.directory=/storage/config
      - --providers.file.watch=true
      - --providers.docker=true
      - --providers.docker.exposedByDefault=false
      - --providers.docker.constraints=Label(`traefik.constraint-label-stack`,`appwrite`)
      - --entrypoints.appwrite_web.address=:80
      - --entrypoints.appwrite_websecure.address=:443
      - --entrypoints.appwrite_web.forwardedHeaders.insecure
      - --entrypoints.appwrite_websecure.forwardedHeaders.insecure

I have restarted docker compose of appwrite and the setting for command are visible when using docker inspect.

When visiting https://baas.example.com the SSL certificate is visible but I get Bad Request 502 (openresty) as Error.

Appwrite Doctor has the following error:

I have set the environment variables _APP_DOMAIN and _APP_DOMAIN_TARGET to baas.example.com.

You can't use localhost because localhost refers to the current container (NPM and not Appwrite)

Do I need to use the IP address inside the (docker network shared with NPM) of the appwrite-traefik container?

If they're in the same docker network, you can use the service name

That was the missing key. Thanks a lot, @Steven :appwriteheart2:

[SOLVED] Bad Gateway (502) - Nginx Proxy Manager with SSL certificate does not work