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

Error status code 200 while hitting landing-page of ShinyProxy #158

Closed
dylancis opened this issue Jun 17, 2019 · 14 comments
Closed

Error status code 200 while hitting landing-page of ShinyProxy #158

dylancis opened this issue Jun 17, 2019 · 14 comments
Labels

Comments

@dylancis
Copy link

dylancis commented Jun 17, 2019

initial comment moved to a separate ticket #159

@dylancis
Copy link
Author

dylancis commented Jun 18, 2019

I believe this is also the reason why if you try top freshly open the /app_direct/ while using auth0, afte rlogin, you will get straight the following page:

image

You git F5 (refresh) anfd the app will show up.

@michaelhogersosis
Copy link

We are using landing-page: /app_direct/<app-name>/ + Auth0 and users occassionally see the 200 error mentioned by @dylancis.

@dylancis
Copy link
Author

@michaelhogersosis we are using the default landing-page in our side.

@dylancis
Copy link
Author

This is happening even using the main index page and clicking on the app link without /app_direct/

@michaelhogersosis
Copy link

@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

@dylancis
Copy link
Author

@michaelhogersosis I used to indeed after a new deployement - now our process tries the app once after a new ShinyProxy deployment.

@dylancis
Copy link
Author

dylancis commented Jun 19, 2019

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:
http://shiny-dev.dbrsanalytics.local/error?code=qUAIPRpdMMUwJhO8&state=2BVOdnXqMXIwUH9k26SI6kBq7Tjqza6Bu9hhjwjyjoo%3D

@michaelhogersosis
Copy link

@dylancis, interesting, we noticed a similar issue after a new deployment. Are you using Kubernetes? I had a feeling our image-pull-policy: Always setting was the cause

@dylancis dylancis changed the title No loading message while using app_direct mode (in contrary to app mode) Error status code 200 while hitting landing-page of ShinyProxy Jun 19, 2019
@dylancis
Copy link
Author

@michaelhogersosis yes we do use k8s although we have the following set:
image-pull-policy: IfNotPresent

@ericwburden
Copy link

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.

@PauloJhonny
Copy link

PauloJhonny commented May 26, 2021

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.
I'm using LDAP for authentication and shinyproxy v2.3.0. (I'm not using the k8s and /app-direct/ URL).

@tverbeke
Copy link
Member

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).

@PauloJhonny
Copy link

PauloJhonny commented May 27, 2021

Hi @tverbeke. I'm having a problem when upgrading to 2.5.0 :(
That's why i haven't done it yet.
If i just change Dockerfile to get the 2.5.0 version, I can access the login page, but it is not responsive...

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.

@LEDfan
Copy link
Member

LEDfan commented Jul 30, 2021

Hi @PauloJhonny

Great to hear that 2.5.0 solved your issue!
As I believe that your question is answered, I'm closing this issue. Feel free to re-open it if you need more help.

@LEDfan LEDfan closed this as completed Jul 30, 2021
@LEDfan LEDfan added the bug label Jul 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants