I'm not sure if this is the right place for this, but I've been trying to access an Ignition Perspective application using the Perspective mobile app from anywhere on a college campus. There is a campus-wide WiFi network, but it seems that the WiFi my phone connects to is different from the Ethernet network my main gateway computer is on. As a result, my phone cannot find the gateway in the Perspective app.
I'm waiting for an exact response from campus IT, but it seems like there might be a lot of red tape involved in getting my phone and the gateway computer on the same network. Has anyone else dealt with a similar issue? Would it be easier to set up a local WiFi network for the gateway instead? I'm looking for some advice or ideas.
Most likely the campus network is firewalled and the WiFi has guest access which does not have permissions to get to the subnet the Ignition gateway is on.
Consider setting up a reverse proxy on a public host in the cloud somewhere, with a VPN tunnel from the gateway for the proxy traffic. This also makes it easy to maintain a Let's Encrypt certificate for the host name and forcing encryption on the public side.
I've had a really good experience with Hetzner.
$5/mo for an instance with 2 vCPU, 2GB RAM, 40GB local disk, and 1TB of traffic.
They don't have many options for regions, so ymmv.
Tailscale is also an option if you're just looking for a simple tunnel for you or a select few people to access an Ignition gateway - the free tier has worked great for home service access.
Hello everyone! Thank you for all the responses. Over the past 3 weeks I have been going between IT and some people from Ignition to try and sort out this issue. All your suggestions were great, we were just trying to avoid any circumventing of campus IT if possible. Embarrassingly on my end, the fix was super simple. For some reason the original inbound rule setup for the :8088 port was no longer actually allowing inbound connections on the network. I'm not sure if there was some issue with administrator access or something but we made a new admin account on the PC and re-setup the inbound rule and so far I have had no issues! Thank you again for all the support.