You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Checked the hub pod and didn't find anything logged about the user reporting the issue
Didn't had enough context to try and reproduce this myself so I've decided to start a server under the user reporting the problem
Immediately after starting the server, after some load time, I was faced with a 503 error this time
Checking the user pod logs, this 503 looked like a 403 from the server app. Full logs can be found in this gitst. Notice that after some time of leaving the server running and not touching anything, there's a redirect, then 200 OKs
I restarted the server a few more time and every time the same thing happened
I found berkeley-dsep-infra/datahub#2284 that looks kind of similar, though that one has clear evidence about expired tokens, so not sure how similar they actually are 😕
Preliminary conclusion
I'm not sure if the 403 that the user is experiencing on rstudio translates into the same logs on the user pod side as I wasn't able to reproduce that (I copied the rmd file and tried to run it from my own server, but rstudio beat me and couldn't make it to render or raise a 403).
But even without that, the 503 is weird as well and intrusive enough. By the way, you can acknowledge the 503, the error disapears and nothing bad seems to happen afterwards.
The text was updated successfully, but these errors were encountered:
The Freshdesk ticket link
https://2i2c.freshdesk.com/a/tickets/2196
Ticket request type
Something is not working
Ticket impact
🟨 Medium
Short ticket description
Some users are experiencing 403 errors in RStudio
(Optional) Investigation results
I found berkeley-dsep-infra/datahub#2284 that looks kind of similar, though that one has clear evidence about expired tokens, so not sure how similar they actually are 😕
Preliminary conclusion
I'm not sure if the 403 that the user is experiencing on rstudio translates into the same logs on the user pod side as I wasn't able to reproduce that (I copied the rmd file and tried to run it from my own server, but rstudio beat me and couldn't make it to render or raise a 403).
But even without that, the 503 is weird as well and intrusive enough. By the way, you can acknowledge the 503, the error disapears and nothing bad seems to happen afterwards.
The text was updated successfully, but these errors were encountered: