Trying to set the docker container up behind a apache reverse proxy

[Atlasfreak]

Hi,
I am trying to set the docker container up behind a reverse proxy but I always get an error when trying to register.
The error:
[b6534e93-23bb-4f1b-8bda-efd32f45bf0c] ActionController::InvalidAuthenticityToken (HTTP Origin header (https://maybe.<url>.de) didn't match request.base_url (http://maybe.<url>.de)):
The server runs on the maybe..de domain.
I deployed the container with docker compose via Portainer and modified the compose file slightly as I hoped that would fix the problem.

My compose file:

services:

  app:
    image: ghcr.io/maybe-finance/maybe:latest
    volumes:
      - ./storage:/rails/storage
    ports:
      - 127.0.0.1:9991:3000
    restart: unless-stopped
    env_file:
      - stack.env

    depends_on:
      postgres:
        condition: service_healthy

  postgres:
    image: postgres:16
    restart: unless-stopped
    volumes:
      - postgres-data:/var/lib/postgresql/data
    environment:
      POSTGRES_USER: ${POSTGRES_USER:-postgres}
      POSTGRES_DB: ${POSTGRES_DB:-maybe_production}
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:?}
    healthcheck:
      test: [ "CMD-SHELL", "pg_isready -U $$POSTGRES_USER" ]
      interval: 5s
      timeout: 5s
      retries: 5

volumes:
  postgres-data:

and the stack.env file:

PORT=3000
SYNTH_API_KEY=
SMTP_ADDRESS=mail.pergoet.de
SMTP_PORT=465
SMTP_USERNAME=
SMTP_PASSWORD=
SMTP_TLS_ENABLED=true
EMAIL_SENDER=
DB_HOST=postgres
DB_PORT=5432
POSTGRES_PASSWORD=postgres
POSTGRES_USER=postgres
APP_DOMAIN=https://maybe.pergoet.de
SENTRY_DSN=
REQUIRE_INVITE_CODE=false
SELF_HOSTING_ENABLED=true
HOSTING_PLATFORM=localhost
SECRET_KEY_BASE=jWGL3nfviCambSmNvLMhEZlC9DtXraV5n0o4SKCl4tcYplyVAVJQwZk6MelZ55PQ
UPGRADES_ENABLED=false
UPGRADES_MODE=manual
UPGRADES_TARGET=release
GITHUB_REPO_OWNER=maybe-finance
GITHUB_REPO_NAME=maybe
GITHUB_REPO_BRANCH=main
RAILS_FORCE_SSL=false
RAILS_ASSUME_SSL=false
GOOD_JOB_EXECUTION_MODE=async

My apache config:

ServerName maybe.<url>.de

ErrorLog ${APACHE_LOG_DIR}/webseiten/maybe.<url>.de.error.log
CustomLog ${APACHE_LOG_DIR}/webseiten/maybe.<url>.de.access.log combined

Include /etc/letsencrypt/options-ssl-apache.conf

Include /etc/letsencrypt/ssl-certificate.conf

SSLProxyEngine On

ProxyPreserveHost On
ProxyPass / http://localhost:9991/
ProxyPassReverse / http://localhost:9991/

I think it may have something todo with #308 but as far as I know that seems to be fixed and should have been handeled by RAILS_FORCE_SSL and RAILS_ASSUME_SSL.

[master-roby3]

You should add this to the apache config:

RequestHeader set X-Forwarded-Proto expr=%{REQUEST_SCHEME}
RequestHeader set X-Forwarded-SSL expr=%{HTTPS}