Troubleshooting

Troubleshooting

Log

The proxy writes its debug messages to the Enigma2 debug log with the prefix SPC:. To get them:

1. Set the log level to DEBUG, in StreamProxyCockpit - Setup (config.plugins.streamproxycockpit.debug_log_level) or in the setup of the plugin that uses the proxy.
2. Reproduce the problem and attach the Enigma2 debug log.
3. Set the level back afterwards: the debug log is large.

Lines of the plugin that provides the channel have their own prefix (PTV: for PlutoTVCockpit, for example).

Analysing a log

AnalyzeProxyLog.py (in the plugin directory) summarises a log by hand. It reports output windows that were muxed with silence and never got their audio later, and lines that look like errors:

python3 AnalyzeProxyLog.py /path/to/Enigma2_debug_<date>.log

Common problems

Problem	What to check
The channel does not start, SPC: ... can't resolve in the log	The plugin could not look up the stream address. Check its own log lines; the channel may be off air or blocked in your region
The channel played before an update and not now	Update the bouquet of the plugin so it gets the lazy addresses. A bouquet written by an older version holds addresses of the old kind
Distorted video for a few seconds when an ad starts	The channel is played without the proxy. Check that Stream proxy is on in the plugin's setup and that the bouquet was updated afterwards
A recording is cut at an ad break	The recording was made from the address of the stream, not through the proxy. Same checks as above
Nothing at all plays through the proxy	ffmpeg is missing on the receiver, or port 7654 on 127.0.0.1 is used by another program
A channel keeps being downloaded after you zapped away	A recording or timeshift of that channel is still running; it is closed when the last one is done