The log shows the exact binary data that you're sending when the problem happens. I took this data and injected into the plugin so that when I would go to watch the same channel, the plugin would send
your data at that point.
It still works for me, so the problem is not with the data, and as far as I can tell not with the plugin, though the fact that you are only having this problem with the plugin and in a browser still points at XBMC.
It looks like a networking problem, e.g. something to do with Overplay/Smart DNS, or how you're setup to connect through them. If you can watch channels on
www.aertv.ie in a browser but not in XBMC
on the same machine then the only thing I can think of is that the network configuration within XBMC does not match that used by your browser. That 's something to check, maybe take it up with overplay support.
Note: If you haven't got XBMC running on the PC that your browser is running on, then it would be helpful for you to do so, install the plugin and try it out and let me know if it works or not.
The following is the relevant output from your logs:
Code:
PostBinary : 'response.status, response.reason: 504, Gateway Time-out'
PostBinary : 'response.getheaders():
[
[
'close',
'connection'
],
[
'1822',
'content-length'
],
[
'content-type',
'text/html'
],
[
'Mon, 31 Mar 2014 18:11:39 GMT',
'date'
],
[
'1.0',
'mime-version'
],
[
'server',
'squid/3.0.STABLE25'
],
[
'ERR_CONNECT_FAIL 110',
'x-squid-error'
]
]'