Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

504 (Gateway Timeout) #970

Closed
khteh opened this issue Nov 1, 2023 · 4 comments
Closed

504 (Gateway Timeout) #970

khteh opened this issue Nov 1, 2023 · 4 comments

Comments

@khteh
Copy link

khteh commented Nov 1, 2023

Which version of Duende IdentityServer are you using?
Community
Which version of .NET are you using?
7.0.113
Describe the bug
My React.JS / Next.JS application using next-auth library is getting 504 (Gateway Timeout) from time to time. Here is the config:

providers: [
  DuendeIDS6Provider({
    id: "myapp",
    name: "myapp",
    authorization: {
      params: { scope: "openid email address phone profile", protection: "pkce" },
    },
    issuer: process.env.DUENDE_IDS6_ISSUER || config.get('DUENDE_IDS6_ISSUER'),
    clientId: process.env.DUENDE_IDS6_CLIENT_ID || config.get('DUENDE_IDS6_CLIENT_ID'),
    clientSecret: process.env.DUENDE_IDS6_CLIENT_SECRET || config.get('DUENDE_IDS6_CLIENT_SECRET'),
    wellKnown: `${process.env.DUENDE_IDS6_ISSUER || config.get('DUENDE_IDS6_ISSUER')}/.well-known/openid-configuration`,
    idToken: true,
    httpOptions: {
      timeout: 10000,
    },
    profile (user, tokens) {
      console.log(`profile(): ${JSON.stringify(user, null, 2)}, tokens: ${JSON.stringify(tokens, null, 2)}`)
     }
  }),
],

image

Is it something due to the server?
To Reproduce

Steps to reproduce the behavior.

Expected behavior

A clear and concise description of what you expected to happen.

Log output/exception with stacktrace

data

Additional context

Add any other context about the problem here.

@AndersAbel
Copy link
Member

This looks like a network/hosting problem and not something that is related to IdentityServer itself.

@AndersAbel AndersAbel self-assigned this Nov 1, 2023
@khteh khteh closed this as completed Nov 2, 2023
@OmidID
Copy link

OmidID commented Aug 7, 2024

Hello @AndersAbel and @khteh

We faced a similar issue recently only to the well-known endpoint. the rest of the application responding well.

Microsoft mentioned this issue back to the app itself and they get 504 after 240 seconds.

I would like to know, how did you solve this problem.

Thanks in advance.

@AndersAbel
Copy link
Member

@OmidID Please open a new issue as this is already closed.

@AndersAbel
Copy link
Member

@OmidID Could you please have a look at #1361 to see if that is the reason for your issue. Also, if you have any additional information to share please do so in that thread.

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

No branches or pull requests

3 participants