🐛 Bug Report: Clients that uses well known openid-configuration will allways redirected to http://localhost:1411 #120

Closed
opened 2025-07-08 08:40:23 -04:00 by AtHeartEngineer · 0 comments

Originally created by @P1tt187 on 5/30/2025

Reproduction steps

I configured gitea to use Pocket-id.
it uses https://pocket-id.home.lan/.well-known/openid-configuration
My Pocketid instance runs behind traefik.

 labels:
      - "traefik.enable=true"
      - "traefik.http.routers.pocket-id.entrypoints=websecure"
      - "traefik.http.routers.pocket-id.rule=Host(`pocket-id.home.lan`)"
      - "traefik.http.routers.pocket-id.tls=true"      
      - "traefik.http.services.pocket-id.loadbalancer.server.port=1411"  

Click on Sign in using PocketID

Expected behavior

i would expect that gitea will redirect to the url which was specified in APP_URL

Actual Behavior

The browser will be redirected to http://localhost:1411

Version and Environment

v1.1.0
APP_URL=https://pocket-id.home.lan

Log Output

No response

*Originally created by @P1tt187 on 5/30/2025* ### Reproduction steps I configured gitea to use Pocket-id. it uses https://pocket-id.home.lan/.well-known/openid-configuration My Pocketid instance runs behind traefik. ```yaml labels: - "traefik.enable=true" - "traefik.http.routers.pocket-id.entrypoints=websecure" - "traefik.http.routers.pocket-id.rule=Host(`pocket-id.home.lan`)" - "traefik.http.routers.pocket-id.tls=true" - "traefik.http.services.pocket-id.loadbalancer.server.port=1411" ``` Click on Sign in using PocketID ### Expected behavior i would expect that gitea will redirect to the url which was specified in `APP_URL` ### Actual Behavior The browser will be redirected to http://localhost:1411 ### Version and Environment v1.1.0 `APP_URL=https://pocket-id.home.lan` ### Log Output _No response_
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pocket-id#120