Not able to connect to my jupyter lab instance

Technical Help
#1

Hi,

I have been using quantrocket without any major issues and starting last week I have been unable to get into my jupyter lab. I went ahead and deployed the newest version to see if that would fix the issue and I am still unable to get into it and have a need to update a lot of strategies I run tomorrow morning. I ran the logs console command and the only thing I can see is:

houston-1 | 2025/03/31 22:11:00 [error] 11#11: *3 connect() failed (113: No route to host) while connecting to upstream, client: 40.130.89.98, server: , request: "GET /jupyter HTTP/1.1", upstream: "http://172.18.0.18:80/jupyter/lab", host: "quantrocket.ifpquant.com"
houston-1 | 40.130.89.98 - aarongilman1 [31/Mar/2025:22:11:00 +0000] "GET /jupyter HTTP/1.1" 502 824 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36"
houston-1 | 2025/03/31 22:11:05 [error] 11#11: *9 connect() failed (111: Connection refused) while connecting to upstream, client: 40.130.89.98, server: , request: "GET /jupyter/static/favicons/favicon.ico HTTP/1.1", upstream: "http://172.18.0.18:80/jupyter/static/favicons/favicon.ico", host: "quantrocket.ifpquant.com", referrer: "https://quantrocket.ifpquant.com/jupyter/lab"
houston-1 | 40.130.89.98 - aarongilman1 [31/Mar/2025:22:11:05 +0000] "GET /jupyter/static/favicons/favicon.ico HTTP/1.1" 502 824 "https://quantrocket.ifpquant.com/jupyter/lab" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36"
houston-1 | 40.130.89.98 - aarongilman1 [31/Mar/2025:22:11:05 +0000] "GET /favicon.ico HTTP/1.1" 404 0 "https://quantrocket.ifpquant.com/jupyter" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36"

Could you please advise I this is a time sensitive issue for me.

Thanks

#2

disregard - it looks like it eventually worked - just not sure why exactly.

#3

Glad it's working now.

If you run into the issue again, you can check if the Jupyter container is using too much memory by running docker --context cloud stats from your local computer’s terminal. Another helpful step is to open your browser to https://quantrocket.ifpquant.com/ping — if you see "hello from houston," that confirms you can successfully connect to your deployment, meaning the issue is likely specific to the Jupyter container (which, based on your logs, seems to be the case here).

If the Jupyter container does turn out to be the issue, you can recreate it by running:

docker --context cloud compose up -d --force-recreate jupyter

This essentially does what updating to a new version did in your case; it's likely that re-creating the container—rather than the version update itself—resolved the problem. Re-creating the Jupyter container is a safer approach because updating carries a small risk of library changes affecting your strategies. For that reason, it’s best to schedule updates for the weekend when you have time to validate everything.