# Accessing prodigy from outside

**URL:** <https://support.prodi.gy/t/accessing-prodigy-from-outside/1608>\
**Category:** Uncategorized\
**Tags:** usage, solved\
**Created:** [June 3, 2019, 1:53am UTC](https://support.prodi.gy/t/accessing-prodigy-from-outside/1608 "2019-06-03T01:53:57Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [July 14, 2020, 4:58pm UTC](https://support.prodi.gy/t/accessing-prodigy-from-outside/1608/4 "2020-07-14T16:58:11Z")

</div>

> [@DirkP-cntl](#):
>
> You suggest [ngrok.com](http://ngrok.com) as a solution. Is this a trusted solution that you can recommend? It is a closed-source, free tool that provides encrypted tunnels which can be a yellow flag.

Ah, I'm not really suggesting ngrok as a "solution" – it's just a handy tool that makes it easy to try things locally and quickly mirror your localhost. It's the quickest way to get started and it's a popular tool with a premium plan that includes encryption – I haven't heard anything negative about it.

> [@DirkP-cntl](#):
>
> Is it possible for prodigy to listen on a HTTPS port instead of HTTP so that we could set up a auth mechanism and encrypt the communication instead?

Yes, you should be able to set that up with a reverse proxy – also see here:

> [@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.

---

_[View the full topic](https://support.prodi.gy/t/accessing-prodigy-from-outside/1608)._
