how to check error when launch app on landing page

[wss29]

Hi
I deployed two Kubernetes clusters with Theia-Cloud on tow host: one is online, and the other is offline. The online cluster works fine, but the offline one fails to launch the application.

To investigate the issue, I ran the following command to check the pod logs:

kubectl logs -f <pod-name> -n my-namespace

Here are the logs for the online cluster:

And here are the logs for the offline cluster:

Is there any method to check what is happening on the landing page? This would help me understand why the application cannot be loaded.

[jfaltermeier]

In general, this works as follows:

We expect users to implement their own landing page, for example, using the @eclipse-theiacloud/common package:
https://www.npmjs.com/package/@eclipse-theiacloud/common?activeTab=readme

With this library, you can make REST calls to the Theia Cloud Service. I am not sure what offline refers to in your message, but the landing page needs to be able to communicate with the Theia Cloud Service. If this is failing, it could be related to the timeout you are seeing.

The Theia Cloud Service will then create or find the session object in the cluster and return either an error or the session URL.

To debug this, please check whether the landing page can reach the service and review the logs of the service and the operator for any errors.

If you are not yet using a custom landing page and need an example, you can find the source code of our sample landing page here:
https://github.com/eclipse-theia/theia-cloud/tree/main/node/landing-page

[wss29]

I am using MetalLB, a load balancer implementation specifically designed for bare-metal Kubernetes clusters. On the online host, I have a network proxy. When the proxy is enabled, everything works fine. However, when the proxy is disabled, the landing page times out when I try to launch my Theia app. This behavior is similar to what happens on the offline host.

An offline host is a computer that is not connected to the Internet but is part of a local area network.

I suspect that the issue with launching the app might be related to the interaction between the Theia cloud service and the MetalLB network configuration. However, I am not familiar with the details of how the Theia cloud service manages network operations.