Access to PG3 via ipad?

[GQuack]

I've been running Polisy for about a month now with very few issues. We've had 2 power outages at our house over that period of time and both times when the Polisy rebooted, I found I also needed to restart the node servers. Not a big deal provided I am at home and can get to the website via my laptop. I tried getting into the PG3 site via my iPad and ended up with a perpetual "logging in" message. I've noted similar questions from others and thinking this may be a security issue with the iPad perhaps. Is there a way to get to the PG3 site without accessing through the admin console? Concerned if there is a power outage while I am not home and having some issues that I'm not able to resolve.

[bpwwer]

You seem to be asking a couple of different things here so I'll try to answer as best I can.

On your local network, there shouldn't be any problem accessing PG3 from an iPad.  I just connected to mine using my iPhone and other than the small screen, it worked fine.

That being said, you may have to use an unsecured connection (http vs. https) as the iPad probably won't allow you to use the self-signed certificate since it it can't verify it.   Using the ISY Finder to connect may always try to use a secure connection.  If so, you simply have to type the Polisy's IP address manually into the browser address field (http://<ip address:3000/).

Then you mention trying to do it remotely.  Right now, PG3 does not provide any method to access it remotely.  That's not to say you can't, but you have to know how to configure your network to allow this.  You can open port 3000 through your router, however, for security reasons it is never a good idea to open ports.  Or you can access your home network via a VPN.  Using a VPN is much more secure and once the VPN is configured and connected, you'd access PG3 remotely the same way as if you were on your home network.

[Geddy]

3 hours ago, GQuack said:

Is there a way to get to the PG3 site without accessing through the admin console?

Absolutely! I never access PG3 through admin console (or the ISY Finder window). Use the IP of the Polisy and add :3000 and get directly to the interface using any web browser. 

On the ipad (or computer):  http://<ip of polisy>:3000   
                        (be sure to use your IP numbers in the crossed out area of the example)

Boom! You're there.

It's a 70/30 shot of getting there using http://polisy:3000 as some routers don't handle local addressing for Polisy correctly, but my current router does, so it's been nice to not have to remember the IP address. Although I did make a bookmark to the Polisy web interface on my browser of choice.

Like @bpwwer, I just tried to log in from my iPhone (using Chrome) and it worked like a snap. It did warn me that it wasn't a secure connection, but that's normal. Just remember it will want you to log into ISY Portal account first then come back and log into PG3. I think you can skip the portal login, but it's always best to just go through the Portal login process so all the node servers can update correctly. 

 

3 hours ago, GQuack said:

I tried getting into the PG3 site via my iPad and ended up with a perpetual "logging in" message.

Where are you getting stuck in this loop for login? Make sure that if you're using "admin" for the user that you use the lower case A. Often times on iOS it will capitalize the first letter of a form. The user name is case sensitive (yep...just found that out when I tested and used "Admin" it said wrong credentials changed to "admin" and zipped right in)

 

[GQuack]

bppwer and Geddy, this is great information. I was indeed able to get into PG3 on my iPad without issue from within my network using your suggestions. My bigger concern is if I am not on my home network. I need to ponder about the options of setting a router forwarding rule for port 3000 vs. a VPN connection. Thank you very much.

[Dub]

1 hour ago, GQuack said:

port 3000 vs. a VPN connection

I would very much consider a VPN vs port forwarding rule.  It's a little more effort but eliminates the risk.  I thought port 3000 might be an obscure port and "fly under the radar" but my search shows its a Bit-Torrent port on the open internet, so that might make your router a little more attractive for random hackers.  I would actually recommend to not open any port on your firewall inbound.