Running slicer-notebook Docker behind HTTPS reverse proxy?

4GB RAM is low and 4th generation Intel CPU is very old. You can open a new terminal using New button in the Jupyter GUI to inspect the system logs and see what fails. See for example this similar topic (failure to start Slicer on a 3rd generation Intel CPU).

You can also try to just simply install Slicer on that computer and see if it starts.

I’ve also updated and tested a notebook image and tested that it works well.

Maybe you could make Slicer work by building it on your system instead of installing the pre-built package.