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

[OSS] Airbyte logout 404 error #53673

Open
ivan-sukhomlyn opened this issue Feb 13, 2025 · 4 comments
Open

[OSS] Airbyte logout 404 error #53673

ivan-sukhomlyn opened this issue Feb 13, 2025 · 4 comments

Comments

@ivan-sukhomlyn
Copy link

Topic

No response

Relevant information

Airbyte version - 1.4.1
Helm chart version - 1.4.1
Deployment mode - oss
Edition - community

There is an error while requesting to Sign Out from UI with authentication enabled.

Response details:

Error 404: Not Found
The server can not find the requested page

Host: <hidden>
Original URI: /api/logout
Forwarded For: 10.50.34.36
Namespace: airbyte-test
Ingress Name: airbyte-webapp
Service Name: airbyte-airbyte-webapp-svc
Service Port: 80
Request ID: 6d899bf21093939b6acf5e027a3e4d23
Timestamp: 1739464332
Image
@marcosmarxm
Copy link
Member

@airbytehq/frontend can someone check if this is in front or in the API?

@marcosmarxm marcosmarxm added area/frontend Related to the Airbyte webapp team/compose and removed needs-triage labels Feb 17, 2025
@chandlerprall
Copy link
Contributor

99.9% sure this is API; the frontend path POSTs to /logout, any non-2xx or 3xx response will error. Along with this message, the user should also get an error logged in their console, which would confirm if this is the API (along with potentially more information) vs. frontend (error message would give us those details, too)

@teallarson
Copy link
Contributor

I was able to reproduce this locally in OSS. Echoing what Chandler said, this is a backend error, but I will take a look and have Compose folks look, too.

@pmossman
Copy link
Contributor

pmossman commented Feb 21, 2025

Tracked down the issue to a validation change on Micronaut's end that was introduced back in November. So this has likely been broken since then. I just merged in a fix that will go out in an upcoming release!

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

6 participants