Endpoints don't work in Quarkus workspaces

[svor]

Describe the bug

Predefined endpoints don't work in Quarkus workspaces

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

1. Go to che.openshift.io and create Quarkus REST API workspace
2. Execute Package and Start Development mode (Hot reload + debug) commands
3. Try to click on hello-greeting-endpoint endpoint

Expected behavior

New tab should be opened with the application

Runtime

• kubernetes (include output of kubectl version)
• Openshift (include output of oc version)
• minikube (include output of minikube version and kubectl version)
• minishift (include output of minishift version and oc version)
• docker-desktop + K8S (include output of docker version and kubectl version)
• other: (please specify)

Screenshots

Installation method

• chectl
  • provide a full command that was used to deploy Eclipse Che (including the output)
  • provide an output of chectl version command
• OperatorHub
• I don't know

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • che.openshift.io
• other: please specify

Eclipse Che Logs

Additional context

[l0rd]

It looks like the port plugin is asking if we want to expose the port even if it's already exposed cc @benoitf

[benoitf]

@l0rd
port plugin is asking because the process is listening only on ::ffff:7f00:1 which is the loopback URL so it's not 'exposed' at all, it should listen on all interfaces '0.0.0.0' to be reached from the outside (without jwt proxy)

If I accept the redirect it's working

So it's how quarkus is configured that is wrong there.
quarkusio/quarkus@ac8b99c

22 days ago it has been changed to not listen on all interfaces anymore

And Max didn't wanted that we use a specific commit of quarkus repository it's what is happening with breaking changes.

Adding -Dquarkus.http.host=0.0.0.0 fixes the issue.