I have some very strange remote access behaviour recently. Here’s a rundown:
For a few days now I couldn’t get remote access to show that it’s working. As far as I can tell it always worked okay-ish (a bit slow on first connection maybe), but in the remote access settings it kept telling me that the server isn’t reachable from the internet. Hitting “retry” would briefly switch it to green, but then after a few second go back to a negative reading.
So I thought I’d give it a try fixing it.
I set it to a manually specified port and set up the port forwarding in the router (used upnp before). Immediately the remote access read as working! Testing it though revealed that it would only allow indirect streaming from outside my network now.
Well, I’d rather have it working while it’s telling me that it isn’t than the other way round.
So I switched it all back. Removed the port forward in the router and unticked the “Manually specify public port” option in PMS.
And would you know it, it now STILL only allows indirect streaming from outside my network.
So I’m at a bit of a loss here. What is happening?
Rebooted everything including router.
Positive: Yay, I can stream directly again from outside my network
Negative: PMS tells me that remote access ISN’T working again.
Current port mode: Upnp
So I’m back at square one. The remote access status in the PMS settings just seems to be lying to me. I guess I can live with that, but maybe it’s of interest to the developers.
I see that all the time, where remote access shows red (no access) but it still works.
Find that the Web-client is a little slow in making it show green… I think its just the way the process is done and how busy things are. I just ignore it and if I hear it’s not working then I look into it… Haven’t in a long time… Takes time to get used to ignoring it…
I turn WIFI off on my phone to test if its working remotely…
I too have noticed that the remote access indicator would occasionally take a bit of time to show it’s working. This time though the status would often not change at all and hitting “retry” would only succeed for a few seconds before switching back to red.
I think these issues would be cleared up if there was a third “undetermined” status there to be shown when the system hasn’t successfully confirmed remote access yet but hasn’t encountered an error yet either. Showing it not working by default leads to a lot of unnecessary troubleshooting.
