Yes, thank you! Although, I believe it is resolved. Thank you!
Sorry, @micelijt ! Yes, I think it was all fixed for you by a system update we did back in October. My question was to @eugene.brenner , whose account looks like it must be having problems due to a different issue.
Hi, gpjt,
Of course you can take a look at files. Thank you!
@eugene.brenner thanks! I think I see the problem. At the end of your .bashrc, there is some stuff to set up something to do with virtualenvs, which overrides the conda setup that is immediately above. The result is that if you try to run something in a conda environment, it will try to use the system Python instead. The reason that means that your server doesn’t start is that it activates its own conda environment, then tries to start and finds that none of the packages it needs to run are available.
I’ve commented it out, so you should be able to access the server now. If you want to re-introduce it, then I think that it will work if you put it above the “conda” block in the file – you can double-check that without breaking the server by re-introducing it there, then starting. a new terminal – if, in there, you can run these commands without an error, it should be OK:
conda activate jupyterlab
python -c "from jupyterhub.singleuser import main"
Hi, @gpjt ,
The server starts fine now. Thank you very much! Yes, I see now what caused the problem. Will double-check every change I make in the future 
Excellent, very glad to hear we could help 
Hi @gpjt ,
I’m having an issue with my Anaconda Cloud notebook server. I keep getting the error:
Spawn failed: Server at http://127.0.0.1:36707/jupyterhub/user/efa7895e-2474-4df4-b084-3dbcaf6318aa/ didn’t respond in 300 seconds
Is it possible to get it fixed? Thank you!
Hi there! I’ve replied in this other forum thread.
Try now, it should be fixed
Thank you, it works now!
What was the problem? And can I solve it myself if it occurs again?
Hello! I have the same spawning error 
Can you please help me with this?
I suspect it might be a caching issue, so I tried it in incognito mode, but it didn’t solve the problem.
Hey @ajeong2k, sorry about that! Could you send the URL that you are accessing so that we can get that resolved today for you?
Thanks,
Jack
Hello Jack,
Thank you for your response. I am currently accessing the JupyterHub on a server managed by my university through an OpenVPN connection. In this case, would sending the URL help resolve the issue?
Thank you in advance for your assistance.
Hey, in that case no I don’t think it would. Sorry I thought you were accessing Anaconda Notebooks at nb.anaconda.cloud
In this case I think you would need to speak to the administrator of your university JupyterHub if that’s possible?
Thanks,
Jack
Thank you for the clarification and your help!
Hi!
I think I have the same issue. I’m trying to access my notebooks through: https://anaconda.cloud/api/navigator/v1/applications/open/an
Can you please help me? Thank you!!
P.S. right now I can’t even start anaconda 
Jubiter lab is working instead.
I’d like to download the files I saved in the cloud and reset everything. What a mess I made!
It looks like you made changes to .bashrc that broke the path, so everything was broken. I have replaced your .bashrc with the default, working one so you should be able to start your server again
1 Like