[SOLVED] Reverse proxy settings

[tidal patio]

A few weeks ago I moved my self-hosted Appwrite instance behind a reverse proxy (using Nginx Proxy Manager) - I just noticed that if I go into Auth > User > Sessions, the IP address being reported is the private IP address and so location is always unknown. It looks like Appwrite isn't getting the correct IP address. Is this an Appwrite configuration that I just missed or is this something that I need to do on the NPM side?

[wooden flare]

See https://medium.com/@stnguyen90/how-to-run-appwrite-behind-nginx-19348ed34243#1d36

[tidal patio]

I already have this added to the docker-compose.override.yml file. Should this be added to the main docker-compose.yml file instead?

[tidal patio]

Here's my docker-compose.override.yml:

version: '3'
services:
  traefik:
    command:
      - --accessLog=true
      - --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.trustedIPs=IP_MASKED_IN_THE_SCREENSHOT
      - --entrypoints.appwrite_websecure.forwardedHeaders.trustedIPs=IP_MASKED_IN_THE_SCREENSHOT
networks:
  gateway:
    name: npm_gateway
    external: true

NPM is accessible through proxy.domain.com - but somehow if I put the IP address on the browser's address bar, it doesn't show NPM.

When accessed as http://IP_MASKED_IN_THE_SCREENSHOT, I get: 404 Not Found openresty. If accessed as https://IP_MASKED_IN_THE_SCREENSHOT, I get: ERR_SSL_UNRECOGNIZED_NAME_ALERT.

[wooden flare]

uhhh the ip address that's shown in appwrite...isn't tha the ip address of NPM?

[tidal patio]

When I look at any user's sessions, it shows 172.22.0.2 which is a private internal IP. It's probably the IP of NPM, should I use this IP instead of the static public IP?

Okay when I used the private IP instead of the public IP, it worked. Thanks!