Forum Replies Created
-
Posts
-
Many thanks for fixing the permission issue, Paul. I have able to access jupyterhub and tyring to start the server.
However, during the first time server starting, I am experiencing the following issue:
Hey Paul, I have retried all the steps including cleaning cookies/sessions and re-accepted with no luck 🙁 Any other solution can we try?
Hey, Paul. I believe I clicked the confirm link back to 09/14 for the production registration and got “invitation not found ” error message as we spoke once over Teams chat. (I did not experience the issue with beta registration though which was done on the same day).
I found out the email again but I believe the link is expired for sure. At this moment, anything we can do to fix it?
cookie issue resolved by manually searching for testbed and deleting everything related. Still seeing 403 for jupyterhub though 🙁
Thank you for your swift action, Paul.
I have tried again but with no luck. Also tried the following steps: deleting cookie and any cache/session data relates to fabric; tried with a different browser with fresh SSO login
All the above failed with 403: Access Forbidden 🙁
Many thanks for your reply, Paul. The script and docker is the approach we ended up going with.
Another follow question come up with is that the server has a GUI console, is it in general approach to have it running and accessible from public? (for now I am tunneling to verify the server installation)
