# Opening Perspective access to the internet

**URL:** <https://forum.inductiveautomation.com/t/opening-perspective-access-to-the-internet/79190>\
**Category:** Ignition\
**Created:** [September 14, 2023, 4:35pm UTC](https://forum.inductiveautomation.com/t/opening-perspective-access-to-the-internet/79190 "2023-09-14T16:35:52Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [September 14, 2023, 9:09pm UTC](https://forum.inductiveautomation.com/t/opening-perspective-access-to-the-internet/79190/6 "2023-09-14T21:09:54Z")

</div>

> [@Transistor](#):
>
> This is probably not a good beginner's project.

Echoing this. You must know what you're doing to do this safely, and not knowing what you're doing can lead to serious problems.

> [@Web server access through internet using cpanel](https://forum.inductiveautomation.com/t/web-server-access-through-internet-using-cpanel/69325/6):
>
> This is not an Ignition problem to solve. The vast majority of the work involved in making an Ignition gateway accessible over the public internet is general IT knowledge that's not specific to Ignition. I'll also add that if you do not know what you're doing, it is incredibly dangerous to expose internal servers to the public internet. For any period of time. I would consider it an absolute requirement to have a public domain name, a valid SSL certificate, and HTTPS enabled before even conside…

---

_[View the full topic](https://forum.inductiveautomation.com/t/opening-perspective-access-to-the-internet/79190)._