VU+ PVR fails with secure https

[nisse99]

New to ATV but was really happy when I found MrMC for it as I have no other means to stream from my VU-box otherwise...

Setting up the TV-section for my Vu+ box at home I've ran into a problem though. When using the secure https enabled the PVR can't set up a connection to my box. If I disable https and use my other port it works immediately.

And yes the port is forwarded correctly. I have an app for my ipad/iphone (Blackbox) which is able to use the https connection. I don't want the standard http-port forwarded and open from outside network that's why I'd really like getting the https to function.

I don't know if it's a problem with MrMc but searching the Kodi forums people don't seem to have any problem with the VU´+ PVR addon and https and I can't find anything on here. Anyone else tried?

Otherwise a fantastic app! Cheers!

[davilla]

mrmc.log would help.

[nisse99]

Out travelling but will post log as soon as I'm back home!

[nisse99]

Sorry for the late reply but I haven't been able to fix the logs until now.

For some reason the connection error just lasted a couple of minutes this time and then it seemed to find my box and started retrieving the EPG for my channels. I though wiihooo finally everythin working.... BUT... it still doesn't...

Now I get the TV submenu and can go in there and see my channels and the EPG/guide for them... however nothing happens when I try to watch any of the channels. (This still works without the SSL enabled, although some channels don't function with that either). I can however go into recordings and start something I have recorded on the box previously...

So I made logs and it was a complete mess however I seem to myself have found what the problem seems to be.

When retrieving the channel information / EPG the program calls for this line:

22:01:53 T:6156464128 INFO: AddOnLog: VU+ / Enigma2 Client: GetHttpXML Open webAPI with URL: 'https://XXX:[email protected]:8888/web/epgno ... %20bouquet'

Where XXX is my correct username and YYY my correct password and the ip-adress is also correct.
However when I try to put a channel on the program uses USERNAME:PASSWORD instead of my actual username and password like above. Which I guess explains why the channels are found and their guides but starting the actual play fails. So the code where it doesn't work is below:

22:02:21 T:6157037568 NOTICE: Creating InputStream
22:02:21 T:6157037568 DEBUG: PVRManager - OpenLiveStream - opening live stream on channel 'SVT1 HD'
22:02:21 T:6157037568 DEBUG: opening live stream on url 'pvr://stream/tv/1.ts'
22:02:21 T:6157037568 DEBUG: PVRFile - Open - playback has started on filename pvr://channels/tv/All channels/pvr.vuplus_1.pvr
22:02:21 T:6157037568 DEBUG: AddOnLog: VU+ / Enigma2 Client: SwitchChannel Switching channels
22:02:21 T:6157037568 ERROR: CCurlFile::Stat - Failed: SSL connect error(35) for https://USERNAME:[email protected]:8001 ... :0:0:0:0:0
22:02:21 T:6157037568 DEBUG: CCurlFile::GetMimeType - https://USERNAME:[email protected]:8001 ... :0:0:0:0:0 -> failed
22:02:21 T:6157037568 DEBUG: CFileCache::Open - opening <1:134:1:0:0:0:0:0:0:0> using cache
22:02:21 T:6157037568 DEBUG: CurlFile::Open(0x133847c00) https://MYIP.COM:8001/1:134:1:0:0:0:0:0:0:0
22:02:21 T:6157037568 ERROR: CCurlFile::FillBuffer - Failed: SSL connect error(35)
22:02:21 T:6157037568 ERROR: CCurlFile::Open failed with code 0 for https://USERNAME:[email protected]:8001 ... :0:0:0:0:0
22:02:21 T:6157037568 ERROR: Open - failed to open source <https://USERNAME:[email protected]:8001 ... :0:0:0:0:0>
22:02:21 T:6157037568 ERROR: CDVDInputStreamPVRManager::Open - error opening [https://USERNAME:[email protected]:8001 ... :0:0:0:0:0]
22:02:21 T:6157037568 ERROR: CDVDPlayer::OpenInputStream - error opening [pvr://channels/tv/All channels/pvr.vuplus_1.pvr]
22:02:21 T:6157037568 NOTICE: CDVDPlayer::OnExit()
22:02:21 T:6157037568 DEBUG: CDVDInputStreamPVRManager::Close - stream closed


So I guess it's a problem of the actual username and password not being used for all commands. Hope this helps and that you're able to make a quick fix for it...

[amet]

unfortunately "SSL connect error(35)" means that MrMC cant communicate with VU+ on https due to some handshake issues with curl and ssl.

since its not always failing it is difficult to fix , if we cant reproduce we cant fix

[davilla]

If you see 'USERNAME:PASSWORD', that from log redaction of the user/pass. It's not prefect which is why you see it showing up in some log lines but not all. On the list to hunt them down and force redaction.

This smells like an SSL issue. Will check on how we build curl.

[amet]

@nisse99, please send your apple ID email to [email protected] and we will add you into testflight with a possible fix.

[nisse99]

I didn't really understand davilla's post to be honest. Or wait, did he mean that all the lines with my actual username and password should be redacted? I guess that's what threw me off, because if that's the case it only seems to redact on the streaming of live-tv which also coincidentally is the only part that doesn't work. And for all other things that work (retrieval of EPG / channel lists / recordings) my actual username and password is seen in the log file and not redacted, that's why I thought it wasn't using the actual username and password...

I will email you my apple-ID now, and hope for a fix Thanks for the help guys!

[nisse99]

Searching the KODI forums I think I found the problem and a possible solution.

So the problem:

Trying to configure the VU+ PVR addon with my chosen outside port that is forwarded to my vu+ duo2 and enabling HTTPS in addon settings, authentication and access to the box for epg data etc. seems to work.
What I can't do is the actual streaming. The log shows me, that the plugin is trying to stream using a https:// URL as well. I think though, that the openwebif plugin on the vu+ duo2 side does not support actual streaming through https.
Does it make sense at all that the plugin tries to stream through HTTPS? Are there other enigma based boxes that do streaming through https? If yes, it would be good to have a corresponding option in addon settings to choose if streaming itself is done via HTTPS or authentication etc. only

And the next poster gave the following solution:

Did a bit of research and this can be fixed on either client (Kodi) side, with a fixed libcurl which accepts the cipher served by the Enigma2 receiver (TLS1.2 in my case), or on the server (receiver) side, by adding the following default option to the m3u file generated by OpenWebIf: #EXTVLCOPT--http-reconnect=true --ciphers=<cipher name here>


Are you able to incorporate the fixed libcurl for mrmx on the client side? To be honest I don't know how to go about with the solution for the receiver side as I'm not the most technical person...

[amet]

if you use current kodi, does it have the same issue? can you stream from VU+?