Since the end of the 3rd course, I’ve constantly faced issues with the jupyterlabs setup, ie, it ending up not loading.
I’ve tried deleting the Cloud9 environment multiple times, re-creating it by alternating between public subnets a and b, and yet there is no change - it doesn’t load.
I looked at the security rules on the EC2 instance that powers it, and there is a rule to allow access to :8888 from any IP - so I don’t see what the blocker is. I’ve wasted a lot of time doing these deletions - sometimes more than the actual lab itself. What can I do about this?
Hello @laegoiste
Sorry for the inconvenience. If you keep facing the same issue in the lab and you are sure you are choosing all the right settings for your cloud9 environment, please fill out the lab refresh form for the problematic lab, and try again afterwards.
I’ve just done that. Is there a time-credit issued for these kinds of issues? It’s incredibly annoying and this is perhaps the 6th or 7th time I’ve had this issue.
@laegoiste You are right, and I am sorry. Please, wait up to 3 business days and try again after. If your subscription ends, we can ask the staff about your options.
Hello @Mubsi
Can you please help @laegoiste here? He lost a few days because of an issue in one of the labs, and he is asking if we can compensate for that.
Thank you in advance.
I can do that, sure. But, I think it’s a bad UX to have the user who experienced problems reach out to coursera support and explain the problem all over again.
This is because you are asking for compensation, which is in the hand of Coursera (all of the UI, subscription payments etc fall under the umbrella of Coursera), and I (DeepLearning.AI) have no say or control in this matter.
DeepLearning.AI is only responsible for the learning content it puts on Coursera.