Skip to content

Troubleshooting and Common Issues

Jump to bottom
Thomas Gorgolione edited this page Jan 21, 2021 · 9 revisions

Issues when setting up more than two instances of locast2plex

If you have trouble accessing either instance, check to see if the UUID that is reporting in the logs are different in both instances. If they are the same, you can:

  • For 0.4.x delete the service_uuid file in the locast2plex folder in one of the instances to regenerate a different UUID.
  • For 0.5.x delete the uuid=xxxxx line in config.ini (or you could also change it manually)

Unable to login

Some users reported issues when logging in with special characters in the password. This should be resolved in 0.5.x as the username and password is set in a config file now.

Errors on obtaining GeoIP (0.4.x and below)

  • Fixed by upgrading to Python 2.7.9 in Windows (thanks mikeh143!)
  • For users that also employ pihole, or anyone who employs ad-blocking at a router or passthrough server level, make sure you whitelist get.geojs.io (thanks borFSU!).

[Errno 32] Broken pipe

This error occurs when you finished watching or recording a channel. It's related to Pythons http serving module, and is only shown for logging purposes. Should be safe to ignore.

Kodi does not show proper channel numbers

There are two aspects to this problem. Kodi can show correct channel numbers (based on the channels.m3u), with a setting. However, at the moment either Kodi or the IPTV Simple adapter (not sure which) has trouble with subchannels. So, for channels with multiple subchannels, all subchannels will be marked as the main channel number. To enable this, go into the PVR & Live TV settings (with Advanced Settings enabled), then check the "Use channel numbers from backend" option.

locast2plex does not detect your location properly

Sometimes we are not able to properly place your server in the right location. You can override your location by adding the following settings to config.ini:

# Override by Zip Code
override_zipcode = 18034

# Override by Latitude and Longitude
override_latitude = 33.3698
override_longitude = -104.6709

With great power comes great responsibility. Do not use these settings to receive stations you are not physically located in.

Other potential issues

  • We've seen instances where locast2plex could conflict with physical tuner devices, and disconnecting them temporarily fixed the issue. Also, for 0.5.x users, you might be able to get them both working by adding the following lines to the end of config.ini, and changing it to match a device that doesn't exist on your network:
reporting_model=<new model name>
reporting_firmware_name=<new firmware name>
Clone this wiki locally