Crash after setting up SSO

[CrazyWolf13]

Hi @arunavo4

I set up SSO via authentik today.

After doing so and saving it all seemed fine, but after clicking logout, it showed an message at the bottom right that there is a JSON error but not the actual error, then it was like the gitea-mirror UI, but not with any data, and I didn't get redirected to loginpage.

After that the application responded with Code 500 Internal Server Error and this log:

Oct 22 08:06:14 gitea-mirror bun[13473]: [Scheduler] Processing 1 valid configurations (out of 1 with scheduling enabled)
Oct 22 08:06:14 gitea-mirror bun[13473]: [Scheduler] Skipping user cgINKObx5R3XUQpzDS7JpVIZvnnGPvKy - next run at 2025-10-23T05:55:14.645Z

EDIT: I could not find any other relevant error in the log, accoring to the log everything should work fine.

I couldn't even get to a login page and a state where I could sign in with authentik, so this problem is purely on gitea-mirror side.

Also I saw you are using IDs for user, is it possible to map an existing user to an OIDC user?

can I just change the user ID via the DB, or do you plan on adding this feature?

[arunavo4]

@CrazyWolf13 did you try this PR #96

[CrazyWolf13]

my bad, still had reverse_proxy auth enabled on my reverse proxy.

500 Error is gone, but I'm getting this:

[arunavo4]

@CrazyWolf13 is this on the main branch or the PR #96

[CrazyWolf13]

@arunavo4 main branch.

If I shall test the PR, I'd be happy to do so, but then a tagged release would be awesome, so I can test it :)

[arunavo4]

@CrazyWolf13 let me make one for you

[arunavo4]

@CrazyWolf13 this should work https://github.com/RayLabsHQ/gitea-mirror/releases/tag/v3-sso since you need source files right?

[arunavo4]

@CrazyWolf13 also was there anything from docker logs>? on main branch anything useful?

[CrazyWolf13]

@arunavo4 I'm not using docker, I'm the proxmox guy :D
Yes, with the new branch deployed I can see this:

Oct 22 08:41:27 gitea-mirror bun[13994]: # SERVER_ERROR:  467 |   let { baseURL, params, query } = option || {
Oct 22 08:41:27 gitea-mirror bun[13994]: 468 |     query: {},
Oct 22 08:41:27 gitea-mirror bun[13994]: 469 |     params: {},
Oct 22 08:41:27 gitea-mirror bun[13994]: 470 |     baseURL: ""
Oct 22 08:41:27 gitea-mirror bun[13994]: 471 |   };
Oct 22 08:41:27 gitea-mirror bun[13994]: 472 |   let basePath = url.startsWith("http") ? url.split("/").slice(0, 3).join("/") : baseURL || "";
Oct 22 08:41:27 gitea-mirror bun[13994]:                        ^
Oct 22 08:41:27 gitea-mirror bun[13994]: TypeError: undefined is not an object (evaluating 'url.startsWith')
Oct 22 08:41:27 gitea-mirror bun[13994]:       at getURL2 (/opt/gitea-mirror/node_modules/@better-fetch/fetch/dist/index.js:472:18)
Oct 22 08:41:27 gitea-mirror bun[13994]:       at <anonymous> (/opt/gitea-mirror/node_modules/@better-fetch/fetch/dist/index.js:521:16)

did you setup your env vars properly?

[CrazyWolf13]

@arunavo4
Yes I think so, otherwise let me know.

NODE_ENV=production
HOST=0.0.0.0
PORT=4321
DATABASE_URL=sqlite://data/gitea-mirror.db
PUBLIC_BETTER_AUTH_URL=https://gitea-mirror.redacted.dev
BETTER_AUTH_URL=https://gitea-mirror.redacted.dev
BETTER_AUTH_TRUSTED_ORIGINS=https://gitea-mirror.redacted.dev,http://10.10.20.45:4321
BETTER_AUTH_SECRET=REDACTED
CLEANUP_DELETE_IF_NOT_IN_GITHUB=false
npm_package_version=3.7.1 

[arunavo4]

@CrazyWolf13 can you try the v3.8.7 version look like better-auth have fixed some of the issues with sso that was blocking in their new beta release.

[arunavo4]

@CrazyWolf13 can you share a screenshot of your OIDC config, you can redact domain. also is your authentik in http or https ?

[CrazyWolf13]

@arunavo4 authentik is https via nginxreverseproxymanager.

sure: