Hi, I’ve been using Grist self-hosted for several months, and it’s been great for my use case. At some point in the past few weeks, however [assuming it has something to do with a recent release], Grist started forcing me to operate as “@Guest”. Clicking “Sign In” does nothing. Setting GRIST_DEFAULT_EMAIL does nothing. Has anyone else experienced this as new behavior? Below’s my docker compose. Is there something wrong with my setup? Thanks!
grist:
image: gristlabs/grist:latest
container_name: gristCore
env_file:
- .env
networks:
traefik_proxy:
ipv4_address: 192.168.5.36
default:
environment:
- DEBUG=1
- GRIST_DATA_DIR=/docs
- APP_DOC_INTERNAL_URL=https://localhost:8484
- APP_DOC_URL=https://grist.$DOMAINNAME_CLOUD_SERVER
- APP_HOME_URL=https://grist.$DOMAINNAME_CLOUD_SERVER
- GRIST_SINGLE_ORG=docs
- GRIST_ORG_IN_PATH=false
- GRIST_SUPPORT_ANON=false
- GRIST_DOMAIN=https://grist.$DOMAINNAME_CLOUD_SERVER
- GRIST_FORWARD_AUTH_HEADER=X-Forwarded-User
- GRIST_FORWARD_AUTH_LOGOUT_PATH=_oauth/logout
- GRIST_DEFAULT_EMAIL=$myEmail
- GRIST_SESSION_COOKIE=grist.$DOMAINNAME_CLOUD_SERVER
ports:
- "8484:8484"
volumes:
- /$DOCKERDIR/appdata/grist/data:/persist
- /$DOCKERDIR/appdata/grist/docs:/docs
labels:
- "traefik.enable=true"
## HTTP Routers
- "traefik.http.routers.grist-rtr.entrypoints=https"
- "traefik.http.routers.grist-rtr.rule=Host(`grist.$DOMAINNAME_CLOUD_SERVER`)"
## Middlewares
- "traefik.http.routers.grist-rtr.middlewares=chain-oauth@file"
## HTTP Services
- "traefik.http.routers.grist-rtr.service=grist-svc"
- "traefik.http.services.grist-svc.loadbalancer.server.port=8484"
## Homepage Labels
- "homepage.group=Applications"
- "homepage.name=Grist"
- "homepage.icon=grist.png"
- "homepage.href=https://grist.$DOMAINNAME_CLOUD_SERVER"
- "homepage.description=Spreadsheet Database"