# JupyterLab, prodigy and extension: mixed content issue

**URL:** <https://support.prodi.gy/t/jupyterlab-prodigy-and-extension-mixed-content-issue/3619>\
**Category:** Uncategorized\
**Tags:** usage, solved, jupyter, server\
**Created:** [November 10, 2020, 12:58pm UTC](https://support.prodi.gy/t/jupyterlab-prodigy-and-extension-mixed-content-issue/3619 "2020-11-10T12:58:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [November 11, 2020, 1:26am UTC](https://support.prodi.gy/t/jupyterlab-prodigy-and-extension-mixed-content-issue/3619/2 "2020-11-11T01:26:31Z")

</div>

Hi! One option would be to serve Prodigy via HTTPS – for example, by putting a reverse proxy in front of it:

> [@Prodigy with https](https://support.prodi.gy/t/prodigy-with-https/2045/2):
>
> I would recommend adding a reverse proxy in front that is restricted to only https connections. For instance, you would advertise the service on localhost, and have something like Nginx, Traefik or Apache communicating externally, via https.

You could also edit the `app.py` included with Prodigy and add your certificate:

> [@jupyter-notebook: how to ssl the prodigy output?](https://support.prodi.gy/t/jupyter-notebook-how-to-ssl-the-prodigy-output/2461/6):
>
> yes Ines thats right. Adding some lines in the in the prodigy/app.py at uvicorn.run let it work. ssl\_keyfile="/address/.Certs/key.pem", ssl\_certfile="/address/.Certs/cert.pem", ssl\_ca\_certs=None, ssl\_ciphers="TLSv1", ssl\_version=2, ssl\_cert\_reqs=0, But it doesn't solve the prob with the tab in the jupyter lab.

---

_[View the full topic](https://support.prodi.gy/t/jupyterlab-prodigy-and-extension-mixed-content-issue/3619)._