WebUI error

[soccken]

When operating grafana or jaeger webUI, I get an upstream request timeout error.
The demo environment is built with docker compose command.
What causes the upstream request timeout?
Also, what is the solution?

[puckpuck]

can you share the output from docker compose logs frontend-proxy

[soccken]

We apologize.

It is difficult to share logs for information protection.
Please just tell us the possible cause of the problem.

Or if you know what the keywords of the error are, I will investigate the log myself.

[julianocosta89]

@soccken the demo shouldn't have any sensitive data in the logs, unless you have changed something.

We need the logs to try to understand the issue and help you troubleshoot it.

Where are you running the demo?

[soccken]

I am running it on ec2 on aws with docker compose command.
The WebUI is accessed from a browser on another EC2 (windows server) on the same subnet.

Since we are developing in a company development environment, we are not allowed to disclose the logs.

I checked the logs with the docker compose logs frontend-proxy command, but could not find any logs that might be relevant.

Are there any important keywords to find errors?

Translated with DeepL.com (free version)

[julianocosta89]

@soccken we would be interested in knowing if there was any error, to help you troubleshooting.
But as you have mentioned that there are no errors, I'm wondering if the frontend-proxy is properly exposed, and allowing incoming connection.
If you ran the demo with docker compose the frontend-proxy should expose port 8080. Have you configured your ec2 instance network to allow incoming requests on that port?

[puckpuck]

Closing this since we can't help without proper logs. Please re-open if the problem persists, and you can get the logs.