I have experienced similar issue loading the JupyterLab, the solution that worked for me was to use only the part of the url shown at the shell command upto the word “lab” (i.e. http://******.compute-1.amazonaws.com/lab), paste this part only in a new tab to load Jupyterlab, then when it loads there will be a textbox to enter a token to get access to the Jupyter notebook, now copy the token part (the part after the word “token=”) from the shell command window into this textbox, press enter, done.
1 Like
I had tried this, did not work…
Reinaldo Lepsch Neto
I had the exact same issue as Reinaldo using a Mac + Safari. That is, in step 7, the Jupyter Lab URL didn’t work. It got stuck loading the page without success. I tried using another browser (Chrome) and clearing my cache, but it didn’t work.
I got past the problem using a different computer and going through the same steps in Vocareum. I’m using Windows + Firefox now.
Hope it helps!
1 Like
I tried another computer, but it didn’t solve it.
I cancelled the course, who knows will try it another time.
1 Like
Same here - tried Google Chrome, Firefox, different network settings. This lab cannot be completed - hope this problem can be resolved soon so it doesn’t impact the course certification.
I recommend you run a Forum search for the phrase “cloud9”, and see if there are other reports.
Hi @Rannie , sorry that you’re experiencing this issue. Unfortunately our team is not able to reproduce this issue with our devices and network setup. Would you be able to try a difference computer and see if it resolves the issue? If not, could you perhaps share a screenshot of the Jupyter log file you get after running step 7?
Hey, @jessica-dlai
Got the same issue here, below is the error messsage.
Hi @minlin ,
Thanks for reaching out. I checked with our engineers and it seems that perhaps you tried to run the setup.sh script twice? That would cause this error. I suggest you delete the cloud9 environment and restart the steps. Or if your lab already timed out, you may need to wait a little while for the AWS resources to clean up, then you’ll be able to try the lab again. Please let me know if that resolves the issue.
Jess
Hi Guys,
I had similar issue and resolved it by adding inbound rule to the network security group of the ec2 instance. The inbound should allow Custom TCP for port 8888 to “my ip” address. To do this fo to ec2 instance > click on security > security group > edit inbound rule > add custom TCP rule , port 888, select “My Ip” from ip list.
I hope the admins can pick this up to help the learners. Please look for troubleshooting ec2 instance connection.
Also check out this video to edit your security group: https://www.youtube.com/watch?v=f3S2QN1Yml0&t=229s
1 Like