websocket closed every minute

[webysther]

Hi, I started using this project in my NAS with docker compose and nginx proxy manager (fancy nginx) and I'm getting websocket drops, I have nearly 60 containers in my homelab and no issues, my configuration:

The ws primus close:

version: '3.9'

services:
  cocalc:
    image: sagemathinc/cocalc-v2
    container_name: app-calc
    env_file: ../cocalc/.env
    networks:
      cocalc:
    expose:
      - 80
    volumes:
      - /etc/TZ:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
      - "$STORAGE/projects:/projects"
    restart: unless-stopped

networks:
  cocalc:
    name: cocalc

STORAGE=/volume1/docker/cocalc
NOSSL=true

My nginx is boring, websockets enabled and with cocalc resolving in the same bridge internally (look above the expose and not ports):

I'm using my public domain but the project is used as a personal tool, mainly to play around with jupyter.

I got a error about context in websocket and fixed using:

add_header 'Service-Worker-Allowed' '/';

But still getting the same error.

PS¹: No firewall rules from my pc to nas, cable connection, all wi-fi traffic is using another VLAN. PS²: I read all from Debugging connectivity issues

Any suggestions to look?

[webysther]

Seems to hub is always connected and working but the ws is reconnect, not a big issue but the annoyng "starting" splash, as a workaround, there a way to disable this splash?

Here is using the cocalc on chrome latest without any extension enabled:

[webysther]

screen-capture.webm

[williamstein]

Do you have a reasonably minimal sequence of steps that I can use to reproduce the problem?

[webysther]

Hi @williamstein, turns out I think I discovered the root problem.

I'm using the Synology DSM 7.2, very new but old kernel (4.4.302+), the docker engine have some problem with the cocalc and I got this error, why I have so much sure?

• I installed the cocalc in my notebook using multipass (ubuntu 22) with hyper-v on windows 10 via cloud-init
• Using the same docker-compose.yml
• Using the same nginx server and configuration

Worked just fine, I got less latency but I think the major problem is the kernel.

Note:

• Before trying this solution I installed the jupyter desktop with jupyterlab ds docker version on NAS and worked without any error
• I have a vs code server on my NAS with the jupyter extension and worked too (the vs code I use for almost 3 years)

I don't know if make sense to provide Synology constrains support by cocalc, so for now I will move to jupyterlab container but I really like to see this project grow, I will keep the server installed on my NAS with watchtower to automatic update, if you want my help to check the new versions, but let me know.

[webysther]

This is my connection from this setup: