You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running locast2plex v0.6.5 on a Synology running DSM 6.2.4-25556. I'm running the Plex Media Server 1.22.2.4282-6000. This version was installed on 4/13/2021 (5 days ago). It was updated manually as requested by the server. I tried to watch live TV and received an error. When looking at the Docker logs (below), it seems that Locast2Plex is communicating with Locast.org and determining that my IP address is located somewhere in Virginia. When I check that same IP address using iplocation.net or https://nordvpn.com/what-is-my-ip/, it identifies my location correctly. Not sure if the new update on Plex is causing an issue with locast2plex to incorrectly send/receive my location thus not allowing me to use the service. Any thoughts?
00:45:19 Initiating Locast2Plex v0.6.5 stdout
00:45:19 Opening and Verifying Configuration File. stdout
00:45:19 /app/config/config.ini stdout
00:45:19 /app/config.ini stdout
00:45:19 Loading Configuration File: /app/config.ini stdout
00:45:19 Tuner count set to 3 stdout
00:45:19 Server is set to run on xxx.xxx.xxx.xxx:xxxxx stdout
00:45:19 UUID set to: XXXXXXX... stdout
00:45:19 Getting user location... stdout
00:45:19 Getting location via IP Address stdout
00:45:19 Got external IP ##.###.###.### stdout
00:45:20. Got location as Hampton - DMA 544 - Lat\Lon 37.0374-76.3316 stdout
00:45:20 Locast reports that this DMA\Market area is not currently active! stdout
00:46:13 Initiating Locast2Plex v0.6.5 stdout
The text was updated successfully, but these errors were encountered:
Interesting. Having the same issue with the Locast.org app on my FireStick. I submitted a ticket to Locast.org and they responded that GPS issues on devices are not uncommon. They suggested logging out of Locast app on the FireStick and going back in. I did it and it starting working. A little while later, I went to my Synology / Docker app to figure out a way to logout and back on to the Locast account on the Locast2Plex Docker app and noticed that it is now working. Could have been a coincidence or the logging in and out of the app on the fire stick somehow reset my account and set the same IP account to the correct location.
Running locast2plex v0.6.5 on a Synology running DSM 6.2.4-25556. I'm running the Plex Media Server 1.22.2.4282-6000. This version was installed on 4/13/2021 (5 days ago). It was updated manually as requested by the server. I tried to watch live TV and received an error. When looking at the Docker logs (below), it seems that Locast2Plex is communicating with Locast.org and determining that my IP address is located somewhere in Virginia. When I check that same IP address using iplocation.net or https://nordvpn.com/what-is-my-ip/, it identifies my location correctly. Not sure if the new update on Plex is causing an issue with locast2plex to incorrectly send/receive my location thus not allowing me to use the service. Any thoughts?
00:45:19 Initiating Locast2Plex v0.6.5 stdout
00:45:19 Opening and Verifying Configuration File. stdout
00:45:19 /app/config/config.ini stdout
00:45:19 /app/config.ini stdout
00:45:19 Loading Configuration File: /app/config.ini stdout
00:45:19 Tuner count set to 3 stdout
00:45:19 Server is set to run on xxx.xxx.xxx.xxx:xxxxx stdout
00:45:19 UUID set to: XXXXXXX... stdout
00:45:19 Getting user location... stdout
00:45:19 Getting location via IP Address stdout
00:45:19 Got external IP ##.###.###.### stdout
00:45:20. Got location as Hampton - DMA 544 - Lat\Lon 37.0374-76.3316 stdout
00:45:20 Locast reports that this DMA\Market area is not currently active! stdout
00:46:13 Initiating Locast2Plex v0.6.5 stdout
The text was updated successfully, but these errors were encountered: