# Running slicer-notebook Docker behind HTTPS reverse proxy?

**URL:** <https://discourse.slicer.org/t/running-slicer-notebook-docker-behind-https-reverse-proxy/15066>\
**Category:** Support\
**Created:** [December 14, 2020, 11:59pm UTC](https://discourse.slicer.org/t/running-slicer-notebook-docker-behind-https-reverse-proxy/15066 "2020-12-14T23:59:56Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [December 23, 2020, 1:23am UTC](https://discourse.slicer.org/t/running-slicer-notebook-docker-behind-https-reverse-proxy/15066/8 "2020-12-23T01:23:35Z")

</div>

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](https://discourse.slicer.org/t/slicer-and-jupyter-kernel-dies-repeatedly-problem-with-connection/14965/18) (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](https://github.com/Slicer/SlicerDocker/tree/master/slicer-notebook) 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.

---

_[View the full topic](https://discourse.slicer.org/t/running-slicer-notebook-docker-behind-https-reverse-proxy/15066)._