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.

Sign up for GitHub

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

Jump to bottom

Run Litmus behind reverse-proxy #3323

Open
dorroddorrod opened this issue Nov 1, 2021 · 5 comments
Open

Run Litmus behind reverse-proxy #3323

dorroddorrod opened this issue Nov 1, 2021 · 5 comments
Labels
project/community Issues raised by community members

Comments

@dorroddorrod
Copy link

dorroddorrod commented Nov 1, 2021 •
edited
Loading

Question

Hi,
I would like to deploy Litmus in one of my EKS clusters,
All of my infra applications run's on the same domain but different path ( www.example.com/<<app>>) by using nginx-ingress controller

When trying to load Litmus, the frontend app is trying to get static content from www.example.com/ and i would like to know if there is a way to set BaseURL to Litmus to load the client with /litmus . (something like this https://argoproj.github.io/argo-workflows/argo-server/#base-href)

Screen Shot 2021-11-01 at 10 20 57
@imrajdas
Copy link
Member

imrajdas commented Nov 1, 2021 •
edited
Loading

Hi @dorroddorrod, currently, it is possible to run the frontend in a "/litmuschaos" path. You just need to replace frontend's docker image with litmuschaos/litmusportal-frontend-path-litmuschaos:<version>

Please note, only "/litmuschaos" path is possible with this image.

@dorroddorrod
Copy link
Author

Cool ! thanks for the quick response :)

@dorroddorrod
Copy link
Author

dorroddorrod commented Nov 4, 2021 •
edited
Loading

@rajdas98 After changing the default image to litmuschaos/litmusportal-frontend-path-litmuschaos:<version>
I'm getting the following error from the subscriber pod

***@IL-C02FF8LHMD6P ~ % kubectl logs -f subscriber-6cb89f4d97-r2vcl -n litmus
time="2021-11-04T12:08:37Z" level=info msg="Go Version: go1.16.9"
time="2021-11-04T12:08:37Z" level=info msg="Go OS/Arch: linux/amd64"
time="2021-11-04T12:08:37Z" level=info msg="all deployments up"
time="2021-11-04T12:08:37Z" level=info msg="all components live...starting up subscriber"
time="2021-11-04T12:08:37Z" level=fatal msg="failed to parse cluster confirm data" data="<html>\r\n<head><title>405 Not Allowed</title></head>\r\n<body>\r\n<center><h1>405 Not Allowed</h1></center>\r\n<hr><center>nginx/1.18.0</center>\r\n</body>\r\n</html>\r\n" error="invalid character '<' looking for beginning of value"

Any idea's ?

@uditgaurav uditgaurav added the project/community Issues raised by community members label Nov 9, 2021
@dorroddorrod
Copy link
Author

Hi,
Still getting this error with the latest version (2.4.0 )

kubectl logs -f subscriber-6ff65bc955-w8g69 -n litmus 
                                      
time="2022-01-09T10:39:25Z" level=info msg="Go Version: go1.16.12"
time="2022-01-09T10:39:25Z" level=info msg="Go OS/Arch: linux/amd64"
time="2022-01-09T10:39:25Z" level=info msg="all deployments up"
time="2022-01-09T10:39:25Z" level=info msg="all components live...starting up subscriber"
time="2022-01-09T10:39:26Z" level=fatal msg="failed to parse cluster confirm data" data= error="unexpected end of JSON input"

@SteamSpoon
Copy link

This is still an issue - is the base URL configurable?

I see that litmuschaos/litmusportal-frontend-path-litmuschaos is still being pushed but as of v3.11.0 it is identical to the normal version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
project/community Issues raised by community members
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@imrajdas @dorroddorrod @uditgaurav @SteamSpoon