Can't add host.

[Zelaf]

• Luna Version: Luna 0.7.0-rc7
• nVidia GeForce Experience Version: 3.4.0.70
• Moonlight Embedded Version: 2.3.0
• OSMC Version: 2017.03-1

Expected Behaviour: Getting the pair code after entering the IP to be entered on the host computer.

Actual Behaviour: "An exception occured...." after entering the IP of the host and then nothing else happens. No pair code or anything the the IP menu closes after clicking error and the error comes up after a couple of seconds.

I create this issue for a friend of mine (He's not very good at github stuff) and he gets this weird error. I post on his behalf and will help him guide through any possible solutions.

The error should have been reported to EOS.

I hope there are a workaround for this, we tried to get Luna's inbuilt host pairer working but couldn't get python to work properly.

Thank you.

[wackerl91]

Phew, that's not going to be easy ...
For that period (03/22 through 03/26) I got multiple exceptions that might be relevant, but they weren't generated by the same user.

• multiple connection timeouts when trying to get the host information (usually either wrong IP or GFE not responding)
• high amount of "missing moonlight binary" exceptions
• an empty GFE response in the middle of the pairing process (those are all from 03/26, so after you created this issue, but used the IP input field for pairing)

I believe that the latter could be what you're seeing and might happen due to the new GFE version behaving slightly different than previous versions (again).
To be sure, would it be possible for you to mail me the user ID of your friend? You can find my mail address on my profile page and the user ID at ~/.kodi/userdata/addon_data/script.luna/.storage/.eos_uid (if it's a default OSMC installation).

Luna's built-in pairing needs m2crypto (can be installed using apt-get) and pycrypto (via pip). Especially m2crypto can be a pain to install via pip IIRC.

[Zelaf]

"24327924313024634f426158336b525a62336653446654314a4b534d4f506c6466645a6b4b3230544a59717678376d7a675347507536755735746f57"
Finally he had time to do it :D

[wackerl91]

That's weird ... I can find that UUID in the collection where I'm keeping obfuscated HW IDs and generated UUIDs (so it was obviously properly generated at some point), but there's no user with this ID. To be honest I got no clue why this happened, but it's very likely that Eos didn't even receive your exceptions :/

Any chance you could try pairing again and send me the logs generated by Luna?

[TheSNKNeoGeo]

I have the same error and this is my log "24327924313024763248787757706833345375426f44452f5348634c6570747039676934772e645075352e6a68744568556b564a385445562e457561"

i only downloaded the zip and installed the add on, i cant fitn how to install instructions of how to install install m2crypto (via apt-get) and pycrypto (via pip).

Thank's for the great idea creating Luna !

[wackerl91]

@TheSNKNeoGeo Same issue as with Zelaf's friend: the ID has been generated, but is not attached to a user on Eos (i.e. no logs on my end). There seems to be something going wrong really early, preventing both the "registration" process for Eos and your pairing to complete.
Can you try again and copy the log from your end into a pastebin and link it here?

i only downloaded the zip and installed the add on, i cant fitn how to install instructions of how to install install m2crypto (via apt-get) and pycrypto (via pip).

No offense, but googling any combination of the keywords involved (e.g. linux apt-get m2crypto) gives you the answer to this literally in the first search result.

[TheSNKNeoGeo]

this is the "full" log 👍
https://s2.postimg.org/7wletoww9/Untitled-1.png

only the number key, i tryed install on OSMC and in Recalbox (on Kodi) with the same type of log and error.

[wackerl91]

That's not the log, that's the UUID generated by Eos. Luna is logging directly into the kodi log, which should be here (at least on OSMC) ~/.kodi/temp/kodi.log, but YMMV.

[TheSNKNeoGeo]

here is the full log my brother 👍

https://pastebin.com/a0UbDteS

[wackerl91]

Thanks for the log! I've looked through it and there seem to be two issues.

One is related to Eos (or - to be more precise - initial information gathering), which crashes one of the pre-launch threads. Easiest way to get resolve this is to disable Eos in the settings for now; a proper fix will be included in the next release.

The second one is a bit more difficult. From what it looks like - given the context - the moonlight binary couldn't be found. Can you tell me where yours is located?