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

Loadgen doesn't work through the frontendproxy #1706

Closed
martinjt opened this issue Aug 22, 2024 · 4 comments
Closed

Loadgen doesn't work through the frontendproxy #1706

martinjt opened this issue Aug 22, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@martinjt
Copy link
Member

Bug Report

Which version of the demo you are using?
1.11.1

Symptom

A clear and concise description of what the bug is.

What is the expected behavior?

The Loadgen UI for locust works when accessing from the /loadgen path from the frontendproxy.

What is the actual behavior?

Because the static resources don't contain the base path, it doesn't work and all the static resources 404.

Reproduce

Could you provide the minimum required steps to resolve the issue you're seeing?

Additional Context

Please feel free to add any other context about the problem here.

@martinjt martinjt added the bug Something isn't working label Aug 22, 2024
@dides82
Copy link

dides82 commented Aug 27, 2024

Same issue here. Ended up port-forwarding service loadgenerator to access UI and it is working fine.
Issue seems to be related to Locust but did not find a way to configure it correctly (see locustio/locust#149 for example)

@gjshao44
Copy link

gjshao44 commented Oct 1, 2024

have the same issue with version 1.11.1, thanks for the workaround.

@julianocosta89
Copy link
Member

Hello all, thanks for reporting it.
I'm not sure how to properly solve this, but there is a working solution, just add / at the end of the url.
Seems funny, but believe me:

localhost:8080/loadgen
Screenshot 2024-10-14 at 16 13 29

localhost:8080/loadgen/
Screenshot 2024-10-14 at 16 13 53

We tried making it explicit in the docs and in the make start command, but we are open to suggestions.

@martinjt any suggestions?
Or should we close this one?

@gjshao44
Copy link

@julianocosta89, your workaround works, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants