Skip to content
This repository was archived by the owner on Sep 21, 2021. It is now read-only.

Error when accessing /dasboard in K8s #353

Closed
cgaulay opened this issue Dec 6, 2017 · 11 comments
Closed

Error when accessing /dasboard in K8s #353

cgaulay opened this issue Dec 6, 2017 · 11 comments

Comments

@cgaulay
Copy link

cgaulay commented Dec 6, 2017

Please make sure that you provide enough information for us to help you with this issue. Thank you!

Zalenium Image Version(s):
3.8.1b

Actual Behavior -

With Zalenium 3.8.1b in Kubernetes environment, when i trying to access on /dashboard, i got an 403 nginx error page with acces denied. In nginx configuration file, dashboard alias seems to be wrong for dashboard location :
alias /home/seluser/videos;
i've replace it by :
alias /home/seluser/;
and now it works !

It is possible to push a correction ?

thanks in advance !
Regards.

@cgaulay cgaulay changed the title Error getting 403 when accessing /dasboard in K8s Error when accessing /dasboard in K8s Dec 6, 2017
@diemol
Copy link
Contributor

diemol commented Dec 6, 2017

Hi @cgaulay,

Yes, this is kind of a little issue in Kubernetes. Without changing anything, can you access the dashboard if you put a slash at the end? E.g. http://host:port/dashboard/

@diemol
Copy link
Contributor

diemol commented Dec 10, 2017

So after checking this, the real bug is in the nginx configuration. When the mapped port is different from 4444 and the dashboard url does not end with a "/", then a redirection happens to port 4444 and an error is displayed.

Current workaround is to add a "/" at the end of the url. I tried to fix the nginx configuration but I was not successful, any help would be appreciated.

@doertedev
Copy link

Just out of curiosity, can it be that it should point to /home/seluser instead of /home/seluser/videos? Because there are no html files in the videos directory.

@diemol
Copy link
Contributor

diemol commented Feb 16, 2018

Hi @doertedev,

It should point to the videos folder, the files are creating during execution time. Actually that part is ok, it is just a matter of tuning the nginx configuration.

@parberge
Copy link
Contributor

parberge commented Mar 7, 2018

One fix could be to add a rewrite that adds a trailing slash, but I'm afraid it might break something else

@parberge
Copy link
Contributor

parberge commented Mar 8, 2018

Well not even that worked 😠

@Tim-Schwalbe
Copy link
Contributor

I am still facing this issue, also with trailing slash, I get 403 forbidden.
using: image: dosel/zalenium:latest

@parberge
Copy link
Contributor

@Tim-Schwalbe can you try 3.9.1a and see if it works any better?

@Tim-Schwalbe
Copy link
Contributor

I only changed the image tag to image: dosel/zalenium:3.9.1a
Now there is an issue with the docker container --> CrashLoopBackOff
The hubs seems to come up shortly and crashes after a while.
The 403 is still there.

@parberge
Copy link
Contributor

I think your problem is unrelated to this issue to be honest, and probably caused by your setup and/or config

@diemol
Copy link
Contributor

diemol commented Apr 27, 2018

Thanks to @pearj, this has been fixed in https://github.com/zalando/zalenium/releases/tag/3.11.0e

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Projects
None yet
Development

No branches or pull requests

5 participants