Kernel stuck when accessing through DNS

Notebook
,
1

I have deployed Jupyter notebook using docker images “jupyter/scipy-notebook” and “jupyter/r-notebook”. I’ve configured the container to run on port 10000:8888. And there is a nginx serving in front of the service. When user tries to use jupyter with DNS the cell is stuck at running(forever). When accessing through the IP-addr:port (without using the DNS) the cell result is done.
Here is my nginx.confg:

server {
    listen                          	80;
    server_name                     	playground.company.local;
    server_tokens 			off;
    client_max_body_size 		10M;
    return 301				https://playground.company.local$request_uri;
}
server {
    listen                          	        443 ssl;
    server_name                     	playground.golomtbank.local;
    server_tokens			off;
    client_max_body_size 	   	10M;
    access_log 			   	/var/log/nginx/playground/playground.access.log;
    error_log 			   	/var/log/nginx/playground/playground.error.log;

#    client_max_body_size 		10M;
    client_header_buffer_size 		32k;
    ssl_certificate      		/etc/nginx/ssl/playground.crt;
    ssl_certificate_key  		/etc/nginx/ssl/playground.key;

    location / {
	proxy_pass			http://0.0.0.0:10000/;
        proxy_set_header            	Host $host;
        proxy_set_header            	X-Real-IP  $http_x_forwarded_for;
        proxy_http_version          	1.1;
        proxy_set_header            	X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header            	X-Forwarded-Proto https;
        proxy_redirect              	off;
	proxy_read_timeout	    	3600;	#added by togidoto on 9-16-2023
	error_log 			/var/log/nginx/playground/proxy_debug.log debug;   
    }
}

docker run command:
docker container run -it -d -p 10000:8888 -v /home/moguy/jupyter/data/:/home/jovyan/work jupyter/scipy-notebook
docker status:
8ed7a8b857b7 jupyter/r-notebook "tini -g -- start-no…" 7 days ago Up 19 minutes (healthy) 0.0.0.0:10000->8888/tcp, :::10000->8888/tcp strange_moser

2

It looks like you’re missing the Nginx configuration for websockets, have a look at
http://nginx.org/en/docs/http/websocket.html

3

As I understand I have to add below lines into my config, right?
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “upgrade”;
Also I already increased the “proxy_read_timeout 3600;”