Homelab setup on Docker with access via Cloudflare

[jphoke]

Hi all...

I have gotten this somewhat working but struggling with a few bits that are failing.

I have set up an application and hostname in cloudflare called "adventures.foo.com" (replaced domain with foo.com for this post. It points back to a docker container on the internal network "http://192.168.x.y:8015"

I am able to successfully create an account and login as a user via https://adventures.foo.com/ and the user UI appears to be working and even got immich integration working and finding images searched for.

When I try to go to the "/admin" endpoint "https://adventures.foo.com/admin" through cloudflare, or if I try http://192.168.x.y:8015/admin i get 404'd ... if I try internally http://192.168.x.y:8016/admin I am presented a login page but I have tried using admin and the password set in the compose file and the first user I created... at least its not a 404 error, but I cannot successfully log in:
Screenshot trying to log into /admin

Screenshot showing success logging in as user and configured Immich integration:

Trying to figure out what I am doing wrong, and as there are no 'guides' for cloudflare, I'd be happy to put one together if I can get over the hump....

Any suggestions, or glaring errors in what I am doing here?

Here is a redacted copy of the compose file I am using...

services:
  web:
    #build: ./frontend/
    image: ghcr.io/seanmorley15/adventurelog-frontend:latest
    container_name: adventurelog-frontend
    restart: unless-stopped
    environment:
      - PUBLIC_SERVER_URL=http://server:8000 # Should be the service name of the backend with port 8000, even if you change the port in the backend service
      - ORIGIN=http://adventures.foo.com
      - BODY_SIZE_LIMIT=Infinity
    ports:
      - "8015:3000"
    depends_on:
      - server

  db:
    image: postgis/postgis:15-3.3
    container_name: adventurelog-db
    restart: unless-stopped
    environment:
      POSTGRES_DB: database
      POSTGRES_USER: adventure
      POSTGRES_PASSWORD: [PASSWORD REDACTED]
    volumes:
      - postgres_data:/var/lib/postgresql/data/

  server:
    #build: ./backend/
    image: ghcr.io/seanmorley15/adventurelog-backend:latest
    container_name: adventurelog-backend
    restart: unless-stopped
    environment:
      - PGHOST=db
      - PGDATABASE=database
      - PGUSER=adventure
      - PGPASSWORD=[PASSWORD REDACTED]
      - SECRET_KEY=[PASSWORD REDACTED]
      - DJANGO_ADMIN_USERNAME=admin
      - DJANGO_ADMIN_PASSWORD=[PASSWORD REDACTED]
      - DJANGO_ADMIN_EMAIL=[EMAIL REDACTED]
      - PUBLIC_URL=http://localhost:8016 # Match the outward port, used for the creation of image urls
      - CSRF_TRUSTED_ORIGINS=http://localhost:8016,http://localhost:8015,http://192.168.x.y:8015,http://192.168.x.y:8016,https://adventures.foo.com # Comma separated list of trusted origins for CSRF
      - DEBUG=False
      - FRONTEND_URL=http://localhost:8015 # Used for email generation. This should be the url of the frontend
    ports:
      - "8016:80"
    depends_on:
      - db
    volumes:
      - adventurelog_media:/code/media/

volumes:
  postgres_data:
  adventurelog_media:

[seanmorley15]

Hi there! The login page you are showing is the login into the backend admin panel. This is accessed via the server URL, for example https://adventure-server.domain.com. If you are using cloudflare tunnels, I would check to make sure that the localhost and IPs are updated in the compose to use the domain for the frontend and backend exposed URLs. If these are configured correctly, login should transfer from frontend to backend so if you login to the web app, you can then launch the admin panel and you should be already logged in. Let me know if this makes sense, keep me updated!

[jphoke]

Gonna give it a go this weekend -- been slammed with other projects and need to set aside a few hours for this one

Thanks for the info, i think it will make sense when I am in front of it :)