Not sure what my QNAP is set to, but I haven’t had a chance to try the link chewitt posted.
eightball70 you said the file in the link worked in an earlier post correct? So no issues?
Posts by quickstang
-
-
https://chewitt.libreelec.tv/testing/.Libre…-12.95.1.img.gz is a current LE13 nightly (ignore the odd version) with the recent libnfs bump reverted. Test and report back.
Says the webpage can't be found when clicking the link
-
Does anyone already have a solution to this problem? It doesn't seem to be a common problem, since only a few people are affected.
I’ve got nothing. Keep updating to each nightly and still the same issue. Either my media starts then stutters, or it spins like it wants to start then kind of times out. Again, nothing after the nightly build on the 8th works. Revert back and 0 issues.
-
My biggest issue is that once I downgrade to the 08 nightly, I lose my skin, and VPN addon gets hosed and doesn't work. But I can play all my media. lol.
I can then upgrade to the latest nightly, my skin comes back, OpenVPN works automatically, but no media plays.
Hopefully an upgraded nightly soon will fix the media issue whatever it may be, even if it isn't libnfs. I had no idea what caused it. But as stated, glad I am not the only one with the issue.
-
https://test.libreelec.tv/13.0/RPi/RPi5/LibreELEC-RPi5.aarch64-13.0-nightly-20260808-7e66d59.img.gz
This is the last nightly that works for me as well on my QNAP-212 just like Reddog. None of my media plays after that nightly build. It either stutters in the beginning, or tries to load then nothing. As soon as I revert back to 08/08, everything works again. -
After nonstop playing around with NAS settings and google, I FINALLY figured out why the Pi wouldn't play anything from the multimedia folder and I kept getting the picture above.
Under the QNAP NFS settings, the SQUASH options drop down box was set to ALL_SQUASH and when I changed it to NO_ROOT_SQUASH everything started working again. I realized that all of my IP settings were correct in the permission section, there were no settings in the Pi I could see, so I gave this a try. I decided to check other folders and noticed this one was not like the rest for the SQUASH setting. Not sure how it ended up changed, but when I changed it, everything in the multimedia folder now works again on the Pi.
Only took me a whole week to figure it out. lol
-
If you are granting access to NAS shares only to specific IP's and the RPi moves around the DHCP scope, you could:
- Configure a static address in the RPi and then allow that address on the NAS
- Create a DHCP reservation in the router for the RPi so it is always dynamically assigned the same address
- Create credentials to access the shares and avoid the need for IP blocking
IMHO using a DHCP reservation (makes SSH access to the RPi consistent) and also using credentials and basic access controls to manage access to shares is the winning combination. From a security perspective IP blocking is a fairly blunt instrument.
I tried the 3rd option which took in router settings, but still no luck. I then decide to go back to regular default settings and no luck there either. The IP address in the Pi is the same I added to the shared folder in the NAS. Usually as soon as I add the IP address the movies start working again.
However I am getting the picture attached. Rebooted the PI, then the NAS as well, double checked I applied the settings when I added the IP address to the shared folder. Only other change is the nightlies. I wouldn't think that would be an issue, but I can try and downgrade to a previous version to see.
I also know the files are still available because I checked the multimedia folder in the NAS and everything is still there. So I have no idea why the PI is suddenly not seeing the folder. Especially since I added the IP address to the shared folder.
-
Great thanks, I will have a look at this to see if I can figure it out.
-
So I have a QNAP NAS, and for some reason I have noticed recently that on occasion my Pi keep changing IP addresses. And when it does, I have to take that new IP address and add it into my NAS settings for it to see the multimedia. Is there something I should be changing on the PI to prevent this from happening, or is this something I need to fix in my EERO router? Granted I haven't changed any router or PI settings, but it appears to happen more frequently than before.
-
It works on Chrome on the laptop, so it has to be something related to iOS Beta 26. Nothing has changed except that on the iPhone as I was going to the nightly build page daily. Why the nightly build page crashes, I have no idea, because the forum works fine. Regardless if it's WiFi or 5G, the nightly build site does not work on any phone web browser. I have tried 4 of them. But again, why an OS update would cause this for all web browsers, no idea.
-
I’ll have to give the PC a shot. Doesn’t work on any mobile browser for some reason.
-
Odd, because I have tried it in 4 different web browsers on my phone, and they all turn up blank. Duckduckgo flashes repeatedly, safari gives me the image, Chrome is blank, and so is Aloha.
-
-
Can confirm. Latest nightly does work, and all network settings are there.
Thanks again to all who were involved in getting this fixed.
-
Since I know have a working nightly and the latest nightlies aren't that big of a deal, I can patiently wait until the PR is merged.
I may still play with it on another SD card just for the sake of more SSH learning.
Thanks again to you as well as chewitt for the help.
-
I borrowed RPi4 to check a few things. My instructions to replace the firmware were not complete - you also need to create a symlink pointing to the firmware, depending on whether you're using RPi4 or RPi5.
A workaround for the latest nightlies is:
This disables "External auth" feature. Note that WPA3-only network will not work but you should be able to connect to a WPA2/WPA3-mixed network.
Should I run this on a working nightly then install the newest? Or should I just install the latest nightly, then run the code?
Also, is that code the only code that needs ran, or do I need to run it along with the other commands you mentioned in your prior post?
Thanks!
-
Thanks again for trying, and I will use the code as I haven’t yet.
-
In LibreELEC Settings enable SSH, don't disable password. Default password is 'libreelec'. You should be then able to connect with PuTTy by entering Pi's IP address, login is 'root'.
Unfortunately the code did not fix it. I rebooted, installed the latest Nov 3 nightly, and still had no network settings.
I had to throw the old working 19th update from USB stick into the update folder, reboot, and all is fine again.