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

Eclipse Che dashboard is giving not opening with 404 error after keycloak authentication #22443

Closed
debkantap opened this issue Aug 21, 2023 · 3 comments
Labels
area/install Issues related to installation, including offline/air gap and initial setup kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@debkantap
Copy link

Describe the bug

Tried to install Eclipse Che in GKE with Keycloak at OIDC provider.

Please help
DK

Che version

7.72@latest

Steps to reproduce

Steps:

  1. Deployed NGINX ingress controller
  2. Deployed Keycloak with that ingress controller in http mode
  3. Tried to deploy eclipse che with chectl utility
  4. Deployment of eclipse che was clean without error.
  5. While testing the eclipse che is presenting the keycloak for authentication, after successful authentication, the redirect to eclipse che is not working fine. It is giving 404 error and dashboard not opening.
  6. I am following the below command for the deployment:

chectl server:deploy --platform=k8s --che-operator-cr-patch-yaml che-operator-cr-patch.yaml --domain gosimplyee.life --k8spodreadytimeout=500000 --k8spoderrorrechecktimeout=500000 --installer=operator --debug -n che

che-operator-cr-patch.yaml is as below:

kind: CheCluster
apiVersion: org.eclipse.che/v2
spec:
networking:
domain: gosimplyee.life
annotations:
kubernetes.io/ingress.class: nginx
auth:
oAuthClientName: "che-client-id"
oAuthSecret: ""
identityProviderURL: ""

Expected behavior

Eclipse Che dashboard not opening.

whereas devfile , plug-in registries are openings fine

Runtime

other (please specify in additional context)

Screenshots

GKE

Installation method

chectl/latest

Environment

GCE

Eclipse Che Logs

n upstream response is buffered to a temporary file /tmp/nginx/proxy-temp/0000000012 while reading upstream, client: 10.76.0.1, server: gosimplyee.life, request: "GET /dashboard/monaco.44c72f8b45251763d459.js HTTP/1.1", upstream:

Additional context

No response

@debkantap debkantap added the kind/bug Outline of a bug - must adhere to the bug report template. label Aug 21, 2023
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Aug 21, 2023
@tolusha
Copy link
Contributor

tolusha commented Aug 21, 2023

I hope it can help you
#21049 (comment)

@debkantap
Copy link
Author

Hello, Thanks for the response. However I am able to integrate with Keycloak and Che and while redirecting to che dashboard after authentication by keycloak getting 404 error:

"10.76.0.1 - - [22/Aug/2023:09:07:44 +0000] "GET /dashboard HTTP/1.1" 404 19 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 16_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) GSA/277.0.555192628 Mobile/15E148 Safari/604.1" 4340 0.011 [che-che-gateway-8080] [] 10.76.0.59:8080 19 0.011 404 70bf41cc15ec343242e004cd2d7eb61f"

I googled and found two links are close to my issue:

  1. https://stackoverflow.com/questions/68111471/getting-404-error-on-eclipse-che-dashboard-hosted-on-gke
  2. 404 page not found when i open the dashboard after successfully deplying Che  #21288

In first link it says "The fix is fixing Ingress path from /dashboard/* to /dashboard/". but not able to figure out where I need to do this.

Can you pls help.

Thanks & Regards
DK

@dkwon17 dkwon17 added area/install Issues related to installation, including offline/air gap and initial setup and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Aug 22, 2023
@che-bot
Copy link
Contributor

che-bot commented Feb 18, 2024

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 18, 2024
@che-bot che-bot closed this as completed Feb 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/install Issues related to installation, including offline/air gap and initial setup kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants