# Remote Web Access via Ignition Perspective App - Ignition Maker 8.0.14 **URL:** \ **Category:** Maker\ **Created:** [July 26, 2020, 5:38am UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096 "2020-07-26T05:38:46Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![davidt](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@davidt](https://forum.inductiveautomation.com/u/davidt)\ **Post date:** [July 26, 2020, 5:38am UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/1 "2020-07-26T05:38:46Z")
Hi All, I can get access to ignition via the App over my home wifi but not from my public ip address (ISP static IP). I have added port forwarding for 8088 to my router but the app is not connecting. Is there an additional step? Does it only work from a public IP address if I use SSL? Note - All security settings are currently still default. ---
**Author:** ![tordvd](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tordvd/32/11525_2.png) [@tordvd](https://forum.inductiveautomation.com/u/tordvd)\ **Post date:** [July 26, 2020, 7:45am UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/2 "2020-07-26T07:45:55Z")
You should be good. In your app, the gateway url should be [http://public-ip:8088](http://public-ip:8088). Maybe you have a firewall on the server? ---
**Author:** ![davidt](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@davidt](https://forum.inductiveautomation.com/u/davidt)\ **Post date:** [July 26, 2020, 11:02am UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/3 "2020-07-26T11:02:19Z")
I thought if it works on my wifi it should work via my ISP static IP with the port forwarding for 8088 on my router. I already tried with the firewall disabled. Maybe I should check with my ISP that port 8088 is not blocked by them? ---
**Author:** ![tordvd](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tordvd/32/11525_2.png) [@tordvd](https://forum.inductiveautomation.com/u/tordvd)\ **Post date:** [July 26, 2020, 12:10pm UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/4 "2020-07-26T12:10:34Z")
On the gateway webserver. Check config - network - webserver. Make sure the settings are correct and not only local host or local ip ---
**Author:** ![dion.botha](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dion.botha](https://forum.inductiveautomation.com/u/dion.botha)\ **Post date:** [August 12, 2020, 3:01am UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/5 "2020-08-12T03:01:36Z")
I would love to be able to open my perspective apps from outside my local network. I checked my webserver settings, I have Auto Detect HTTP Address checked. I googled for my public IP address and I tried [http://{public-ip}:8088](http://public-ip:8088/) but no luck. Is there anything else that is needed besides checking firewall settings? ---
**Author:** ![tordvd](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tordvd/32/11525_2.png) [@tordvd](https://forum.inductiveautomation.com/u/tordvd)\ **Post date:** [August 12, 2020, 10:41am UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/6 "2020-08-12T10:41:41Z")
Port forwarding in your router/modem. You need to map 8088 against your local ip ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [August 12, 2020, 12:06pm UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/7 "2020-08-12T12:06:54Z")
Don’t do this with port 8088. Only the secure port is safe for exposure to the internet. ---
**Author:** ![tordvd](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tordvd/32/11525_2.png) [@tordvd](https://forum.inductiveautomation.com/u/tordvd)\ **Post date:** [August 12, 2020, 7:56pm UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/8 "2020-08-12T19:56:08Z")
I agree, but the treshhold is abit higher when using ssl. Maybe get 8088 to work first, just as a test. Then setup correctly later ( for example with let’s-encrypt or openssl) ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [August 12, 2020, 8:14pm UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/9 "2020-08-12T20:14:22Z")
> [@tordvd](#): > > Maybe get 8088 to work first, just as a test. Not on a real system, no. Not even for a few minutes. ---
**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\ **Post date:** [August 12, 2020, 9:15pm UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/10 "2020-08-12T21:15:25Z")
I 100% agree with @pturmel. It took me the better part of a day to get SSL working but it is worth it because security should never be an afterthought when it comes to opening a port into your local network! Here is my post documenting what I had to do to get Lets Encrypt working. I hope it helps you. > [@Let's Encrypt SSL Certificate Failing](http://forum.inductiveautomation.com/t/lets-encrypt-ssl-certificate-failing/36317): > > I have been following the previous forum posts and have managed to get through all the steps needed to upload my SSL certificate into the gateway. The problem is when I press the continue button the following error comes up: The following is from the gateway wrapper: INFO | jvm 1 | 2020/07/02 16:24:44 | E [g.SslConfigRoutes] [20:24:44]: Unable to transition to ca-signed certificate state route-group=config, route-path=/ssl/transition/ca-signed-certificate INFO | … ---
**Author:** ![dion.botha](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dion.botha](https://forum.inductiveautomation.com/u/dion.botha)\ **Post date:** [August 12, 2020, 10:17pm UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/11 "2020-08-12T22:17:24Z")
I will definitely try to get it working with SSL from the start and not port 8088, thanks for the info and advise, I will get back to you after I find time to try again. ---
**Author:** ![Steve\_Laubach](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_laubach/32/60900_2.png) [@Steve\_Laubach](https://forum.inductiveautomation.com/u/Steve_Laubach)\ **Post date:** [August 18, 2020, 8:35pm UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/12 "2020-08-18T20:35:23Z")
I agree with @pturmel . Any real system that is controlling real things in your house should be secured. You should also use a secure password on your Ignition Gateway. Consider what someone could do if they are able to open a designer into your gateway with connections to devices and databases. That’s just one example but hopefully you get the point. ---
**Author:** ![davidt](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@davidt](https://forum.inductiveautomation.com/u/davidt)\ **Post date:** [September 11, 2020, 12:19pm UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/13 "2020-09-11T12:19:34Z")
I think it’s time that Ignition support stepped in to resolve this issue as it looks from this forum post that it’s wasting lots of peoples time. I was hoping to convert my current home automation system over to using Ignition Maker but if I can’t access it via my public static IP address then I am wasting my time. I read: An SSL certificate is typically issued to a Fully Qualified Domain Name (FQDN) such as “[https://www.example.com](https://www.example.com)”. However, some organizations need an SSL certificate for a public IP address. \*Note: Only public IP addresses can be used on OrganizationSSL certificates. You must be the owner of the public IP address as per the records held with the [RIPE Network Coordination Centre (NCC) Source: [https://support.globalsign.com/ssl/general-ssl/securing-public-ip-address-ssl-certificates](https://support.globalsign.com/ssl/general-ssl/securing-public-ip-address-ssl-certificates) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [September 11, 2020, 12:25pm UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/14 "2020-09-11T12:25:26Z")
Did you try configuring the public address? [https://docs.inductiveautomation.com/display/DOC80/Web+Server+Settings#WebServerSettings-PublicHTTPAddresssettings](https://docs.inductiveautomation.com/display/DOC80/Web+Server+Settings#WebServerSettings-PublicHTTPAddresssettings) ---
**Author:** ![mcarritt1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mcarritt1/32/4262_2.png) [@mcarritt1](https://forum.inductiveautomation.com/u/mcarritt1)\ **Post date:** [September 11, 2020, 12:32pm UTC](https://forum.inductiveautomation.com/t/remote-web-access-via-ignition-perspective-app-ignition-maker-8-0-14/37096/15 "2020-09-11T12:32:26Z")
> [@davidt](#): > > I think it’s time that Ignition support stepped in to resolve this issue as it looks from this forum post that it’s wasting lots of peoples time. I was hoping to convert my current home automation system over to using Ignition Maker but if I can’t access it via my public static IP address then I am wasting my time. eh, If you can hit your gateway from another device locally on the network by going to 'local ip address':8088 But can't hit it outside of your network by going to 'public ip address':8088 there's something wrong with how you you've done port forwarding or your firewall. I've done it with no issue. If you're trying to set up SSL, they have a let's encrypt guide: [Let's Encrypt Guide for Ignition | Inductive Automation](https://www.inductiveautomation.com/resources/article/lets-encrypt-guide-for-ignition) This isn't really a problem Ignition needs to solve, you would have to figure this out on any server you want to expose to the internet.