Hi Shamus Sim
Welcome to Microsoft Q&A Forum, thank you for posting your query here!
There are two possible scenarios -
- Web socket connection is not happening for computes. Check DNS resolution of computes Nslookup <ciname>.<region>.instances.azureml.ms to private IP, if they are not resolving to private IP, fix the DNS mismatch. Make sure that WebSocket communication is allowed to
*.instances.azureml.net
and*.instances.azureml.ms
in your VNet. WebSocket's are used by Jupyter on compute instances.
2. Computes are un-healthy and does not have any free space to operate. There should be 5 GB memory free to operate. If your compute terminal accessible, use df -h to see highly occupied section and clear cache and delete not used files to make the compute healthy again.
kindly refer below link: Compute-Instance
Hope this helps. Do let us know if you any further queries.
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful.
Thank You.