Posts by Billzilla

    A bit of a bump for this problem.

    I don't use YT much on the Libreelec box but just occasionally I'd like to. It's always worked just fine but after the last update (on 9.2.6 now) it asks to sign-in. I followed the instructions on the link provided and it takes me to this page -

    https://github.com/anxdpanic/plug…rsonal-API-Keys

    I'm signed-in on that page but it refuses to let me create a project or whatever it is I'm supposed to do. See the attachment.
    After reading this thread I thought I'd try to update to V10 but I can't long-in with SSH as it doesn't recognise any password I've tried. (kodi, libreelec, password, guest, admin) I would not have changed the password so I don't know how to go any further with that either.

    Any suggestions please? If it's going to be a s**tfight I'll just delete the YT app from the box and be done with it.

    "Let me guess: this occurs since Microsoft did update your Windows 10 this week?"

    Quite possibly.


    "

    Does the new router have same IP range?

    Some routers uses 192.168.0.xx and others uses 192.168.1.xx.

    It that changes and Your devices uses IP adress to connect that might cause errors. "

    I can't remember, but the SMB share thingy hasn't been changed. See the attachment, that's from earlier in the year and it's still exactly the same now.

    Aaaaaannnnnnd it's back again.

    None of the networking settings have been changed. Checked all the sharing and permission setting, all okay. Checked the passwords, all okay.

    As soon as I try to go access one of the folders (that have worked perfectly for some time now) it comes up with the old "invalid argument" error again.
    Any idea where to start with this please?

    Edit - I forgot to mention that the router I was using back then crapped itself (Netgear D7700 I think) so I replaced it with a D-Link something-or-other, that was garbage so it is now a TP-Link Archer V900.

    Wired or wireless network ?

    Have you rebooted the router ?

    You said everything was working until you rebooted the Windows 10 machine, correct ?

    Did you check the "Advanced sharing settings" - both Private (current profile) and All Networks ?

    You could also try this:

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    .... and with that (relatively) simple action, the W10 box was updated to the 1803 build and .....

    IT WORKSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!

    The smb shares work perfectly, eg, smb:\\CAPTAIN\Movies The user account in W10 was 'libreelec' with the same word for the user & password. I had already added that account to the various folders I wanted to share so they were actually already set up. I'll post the various screens here so other people can see exactly what was done. There was no need to try to get smb1 working.

    blueribb - send me a message. I've got a 3D printer here and I'll make anything you like and post it to you.
    THANKS!!!!!!!!

    I made another video for anyone here to see if I'm doing anything incorrectly.

    External Content youtu.be
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    On the LE box side of things I tried an smb connection using captain, CAPTAIN, and 192.168.0.7. For the share folder I tried Movie and movie. I tried all of those with and without using log-ins & passwords. I tried to see any shared folders on the other PC on this network, a W7 box. It shows this pc on the network but any attempt to connect is refused. The network troubleshooter can't fix it (zero surprise there) when it asks if I want to fix it. I tried all of that on the W7 box with and without the firewall on this W10 pc on.

    Edit - When I use this pc's name (captain) LE spits out the error 'Invalid argument'. When I use the IP address, it spits out "connection timed out" or something like that.

    Yeah I figure it's not the LE box, it's something on the W10 pc that I'm not doing correctly. I just don't know what it is.
    I have to do a little work on the other W7 pc, I'll see if I can get access through that - Letcha know soon.

    Edit - I just found this video, it's got more info than a lot of other ones I've seen and I'm trying it now.

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    A small but useless update.

    I really didn't want to do a full network reset but I took a deep breath and did it. So everything was factory-fresh again. I carefully added a new user, 'libreelec' as an admin. I added libreelec to the shares on a few directories and it did look like that was happening as the green line thing happening as all the files were added. So I tried to access this W10 pc with the LE box .... exactly the same errors popped up as before. I tried a lot of different combinations of passwords (log-in & password were also libreelec) and server (captain in lower & upper case, IP address) and directories (Movie, movie) but none of them would work. When the error messages popped up, I added the share path anyway, as suggested earlier, but the LE box would still not access the shared folder.
    So not a thing better sorry.

    Thanks fellas - I had a look at the NFS stuff and it's waay over my head. I'll have another go at the SMB thing some time in the next few weeks. One of the only things I haven't tried is doing a full network reset on this pc. I may well have changed some setting in the past in this pc that is stopping it from working with LE. I'm totally fed up with the whole thing right now and I'll take some time to get the enthusiasm to try again later.