Skip to content

Support path-based reverse proxy (site_prefix) for SQLPage OIDC flows #1177

Closed

Description

@rinshadka

OIDC does not respect SQLPAGE_SITE_PREFIX when behind path-based reverse proxy

I’m running SQLPage behind an Nginx path-based reverse proxy (for example /123) with OIDC enabled.

Non-auth pages work correctly when started with:

SQLPAGE_SITE_PREFIX=/123

Environment:

SQLPage version: v0.39.1
Auth: OIDC (tested with Zitadel)
Reverse proxy: Nginx
Deployment type: Path-based proxy (/123)
OS: Linux

However, during OIDC login, the callback URL is generated as:

/sqlpage/oidc_callback instead of: /123/sqlpage/oidc_callback

Because of this, authentication only works when SQLPage is served from the root path. Any workaround to this?

I need to run multiple oidc based sqlpages under path based nginx proxy

Thanks.

Activity

  1. lovasoa commented on Jan 8, 2026

    @lovasoa
    Collaborator

    This is a bug in the oidc code, it should take the path prefix into account. I'll work on it!

  2. rinshadka commented on Jan 8, 2026

    @rinshadka
    Author

    This is a bug in the oidc code, it should take the path prefix into account. I'll work on it!

    Thanks @lovasoa , expecting the fix and a release soon :)

  3. linked a pull request that will close this issueOidc site prefix handling #1179on Jan 8, 2026
  4. lovasoa commented on Jan 8, 2026

    @lovasoa
    Collaborator

    It's going to be in the next release. In the meantime, the easiest way for you to test and confirm the fix is to use the lovasoa/sqlpage:main docker image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions