oidc
HI cannot connect my nas oidc server . Got this message. Listening on port 7575 url: http://d6f0c56ea72f:7575
[next-auth][error][SIGNIN_OAUTH_ERROR]
https://next-auth.js.org/errors#signin_oauth_error outgoing request timed out after 10000ms {
error: {
message: 'outgoing request timed out after 10000ms',
stack: 'RPError: outgoing request timed out after 10000ms\n' +
' at /app/node_modules/openid-client/lib/helpers/request.js:137:13\n' +
' at async Issuer.discover (/app/node_modules/openid-client/lib/issuer.js:144:24)\n' +
' at async openidClient (/app/node_modules/next-auth/core/lib/oauth/client.js:16:14)\n' +
' at async getAuthorizationUrl (/app/node_modules/next-auth/core/lib/oauth/authorization-url.js:70:18)\n' +
' at async Object.signin (/app/node_modules/next-auth/core/routes/signin.js:38:24)\n' +
' at async AuthHandler (/app/node_modules/next-auth/core/index.js:260:26)\n' +
' at async NextAuthApiHandler (/app/node_modules/next-auth/next/index.js:22:19)\n' +
' at async auth (/app/.next/server/pages/api/auth/[...nextauth].js:143:12)',
name: 'RPError'
All URI and server are ok .. help please
Errors | NextAuth.js
This is a list of errors output from NextAuth.js.
12 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
❓ Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
Is your SSO provider just down? I assume it was working and it's not anymore?
Otherwise please provide more informations as requested by Cakey Bot
Hi almost working the last error but put the same redirect uri got request","error_description":"The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed. The 'redirect_uri' parameter does not match any of the OAuth 2.0 Client's pre-registered 'redirect_uris'."}
What is your SSO provider, please provide all relevant information such as configs for both
Using authelia. But the oidc provider is sso server (synology). Add app with authelia.domain.com/auth/callback same in authelia and same in homarr container
Need more info than that, What is the URI set in homarr, what is the callback URI in authelia, have you set the scopes correctly. Need all of it
Homar : homar.domain/auth/callback . Please can I give you access to the nas in private session i m fuc…. Stuck
I am not comfortable doing that sorry. I know this can be frustrating but it'll be fine don't worry.
In authelia's configuration, you should have a part specifically for OIDC, which has parts for the id, secret, redirect_uri(s) and scopes. If you don't undestand what I'm talking about, this may be the part that you're missing.
As for homarr, you just need the id and secret from authelia, and the AUTH_OIDC_ISSUER which should look a little something like "https://auth.domain.tld".
Also set NEXTAUTH_URL to "https://homarr.domain.tld"
The redirect URI in authelia's config should be "https://homarr.domain.tld/api/auth/callback/oidc"
https://homarr.dev/docs/advanced/sso
You can try to follow this as best as you can, the example provided in the OIDC provider tab should get you a long way
Thx ok should always add /api/auth/callback/oidc ?
That's for the callback uri in authelia, not in homarr. but yes
so authelia is provider could put any id or secret ....? or must put the same as my oidc nas server ?
You can generate any Key you want, usually just a random SHA256, and use the same in authelia and homarr