-
Notifications
You must be signed in to change notification settings - Fork 150
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
Error status code 200 while hitting landing-page of ShinyProxy #158
Comments
We are using |
@michaelhogersosis we are using the default |
This is happening even using the main index page and clicking on the app link without |
@dylancis, do you occasionally have users running into a 404 error as well? It is similar to the 200 error you describe, in that the application will show up after refreshing the page |
@michaelhogersosis I used to indeed after a new deployement - now our process tries the app once after a new ShinyProxy deployment. |
Hi @fmichielssen I have renamed the github issue as this was two different issues one is feature request:
The url gets updated with the following - not sure what that means though: |
@dylancis, interesting, we noticed a similar issue after a new deployment. Are you using Kubernetes? I had a feeling our |
@michaelhogersosis yes we do use k8s although we have the following set: |
I have a user at another site who runs into this the first time they attempt to log in on a regular basis. I'm not using k8s, but I am using KeyCloak for authentication. Not using the /app-direct/ URL, either. |
I have the same issue when i try to login the first time. The second time works well and i can access the main apps page. |
Hi @PauloJhonny Can you check with ShinyProxy 2.5.0? 2.3.0 is almost two years old and there have been 6 releases since (with numerous fixes). |
Hi @tverbeke. I'm having a problem when upgrading to 2.5.0 :( Since i customized shinyproxy templates (app.html, index.html, login.html, navbar.html), i think there's something to do with it... Maybe I need to do the customization again, but using the default template files. Thank you. EDIT: I upgraded shinyproxy to 2.5.0 and it seems the problem is gone. |
Hi @PauloJhonny Great to hear that 2.5.0 solved your issue! |
initial comment moved to a separate ticket #159
The text was updated successfully, but these errors were encountered: