Posts by DarrenHill

    It's only the major build version (Matrix v19.x vs Leia v18.x vs Krypton v17.x etc) that matter. The minor ones (the bit after the point) doesn't matter.


    The database version is only bumped when the major version is. The minor ones within a given major release version all use the same database number.


    Look in the debug logs of each instance and check that the advancedsettings.xml file is being read correctly, and whether there are any other access errors shown.

    It can be done within the LE settings addon (the built-in one) or alternatively you can do it within your router. Set the network connection up as normal then go to it, edit the connection and the setting is in there (at least it is on the Pi version).


    The latter is the normally recommended method unless there's a specific reason not to.

    From the Team Kodi side, it's detailed in our VPN policy - https://kodi.wiki/view/official:vpn_policy


    The LibreElec stance isn't quite as restrictive as ours is, but is parallel with regard to the piracy and geoblocking aspect.


    For the specific case of homebrew VPN back to your home network, it's assumed that if you're savvy enough to set the server up then you're savvy enough to set the client up as well, and issues tend to be with those (OpenVPN, Wireguard or whatever) and are often better directed at their support forums.

    zomboided - replacing #PATH with the explicit path didn't help (basically same error in openVPN.log as before), so it looks to me like the issue is in the naming and inhaling of the password file from the askpass tag.


    But the good news is that PiVPN can generate an ovpn file without the password encryption (PiVPN -a nopass is the command line to do so, for anyone else who needs it) and that works fine out of the box without any modifications just by pointing the add-on at it under User Defined.


    I'm not sure we lose anything by going that way given the password is stored on the machine in plain text anyway in this case, just a slightly non-standard tweak needed to create it.

    I think I tried that yesterday, but I'll give it another go tonight.


    But also I think PiVPN does have the ability to create ovpn files without a password anyway. So if setting the path specifically doesn't work then I'll try that and report back.

    zomboided I've just hit this same issue, and even by adjusting the ovpn file it doesn't work properly.


    If I add the askpass tag it does ask for the password, and saves it in a file user.txt in the addon's data folder. But the ovpn file gets modified to point to key.txt for some reason. But even if I duplicate the user.txt file to key.txt, it still fails to import it properly as it seems to be just pointed at the folder rather than the specific file in it (see the openvpn.log below)?


    Below are the relevant log files plus the sanitised ovpn file. If you need more information please let me know and I'll grab it.


    ovpn - hastebin
    openvpn.log - hastebin
    import log - hastebin

    I'd also wonder a little if the IP address of the Win10 PC has been changed/reassigned by the router when it rebooted.


    If so the links within KODI may now point to the wrong address and so failing? You can see the IP address in the web dashboard page of the router (usually) and the address that the LE source is using by editing it.


    milhouse - ok tried the image and it works fine for both lirc and usb.


    So it's specifically 8.0.1 that has the issue. I'm now rolled back to 8.0.0 again as the skin i use (Amber) isn't Leia compatible yet.


    Where should we go from here?


    Oops :blush: corrected.


    I will, but give me a few days as I'm traveling at the moment and would rather back the card up first so i can roll back afterwards properly. I'm now back on 8.0.0 and everything is working fine again (after re-enabling the lirc in the config addon).


    I had to hot plug the WiFi dongle to get it working, so it could be.