jademonkee

Was it a Chrome thing?! You've now got it working in another browser? Also, I think Custom Links is native now (though don't quote me on that), which might explain the conflict.

Final thought: check your NextCloud plugin page for any updates or plugins related to sharing (e.g. I used to use a "custom sharing links" plugin that once caused a conflict). If nothing there, I'm all out of ideas.

Hrmm. I have no idea. Is there anything in the logs? Go to: https://YOURNEXTCLOUD.URL/settings/admin/logging And look for anything with a matching timestamp to when you last tried sharing. Also, are there any errors showing at: https://YOURNEXTCLOUD.URL/settings/admin/overview ?

I just tried sharing a folder on my NextCloud instance (using the WebUI) and the URL was created succesfully, and could be opened from an Incognito browser session without a problem. I use Firefox on MacOS. I also did the same process on Safari. It also worked fine. I do not use Chrome, so can't test it on that. What exactly do you mean by "I can't share files anymore"? Is an error ever supplied? If so, at what point (sharing, or accessing?). In what way does sharing not work?

Only problem I've had recently was a bug in the updated Windows client that made it SLOOOOOW. Basically unusable. That was the new x.0.0 release (I think 34.0.0) of the Desktop client (NOT the server). Worth checking if you have a 'point' release to the desktop client available. Otherwise, have you checked the admin panel in the web UI? Are there any manual (i.e. OCC commands) upgrade steps that you still need to perform? Also: you really need to give more context in your posts. Anyone reading this has no idea if you're talking about the Windows client, MacOS client, web interface, or which version you updated to. Just a tip for the future. This is a forum of volunteers (I'm typing this at my breakfast table), not an IT help desk, so you're more likely to get a response if you provide some context in which a subscriber to this post can see a solution without having to dedicate excessive time to it. Not said with any malice here: just trying to help you understand what will get you the response you want.

Just wanna say that I've appreciated your help in the past. Thanks for all your help to me and others. Sorry to hear that your efforts have so often been overlooked - there's so often a feeling of entitlement online, and the time it takes to help is often dismissed/unrecognised. I'm subscribed to this thread, so will continue to pop on when I see a problem I think I have a solution to. Keep well ✌️

@dlandon Version 9.1.1 is out. Can you please do a refresh of the Docker image? Many thanks! If anyone is interested, the changelog is here: GitHubCommits · LMS-Community/slimserverServer for Squeezebox and compatible players. This server is also called Lyrion Music Server. - Commits · LMS-Community/slimserverEDIT: Better, more readable, changelog here: https://lyrion.org/getting-started/changelog-lms9/

Wow, doing a quick Google search and that model ranges from £175 to like £1000+ over here in the UK...

Updated from 7.3.0 seemingly without issue.

This ☝️x100 @SirCadian I definitely recommend moving PiHole from your Unraid server to a Raspberry Pi. Even an original Raspberry Pi can comfortably run PiHole (including with Unbound) - I did so for years. You can pick up a second-hand Pi 3B+ for like £20-£30. It's so much easier/reliable than having your internet tied to your server's uptime. PiHole is super easy to set up on a Pi, too: https://github.com/pi-hole/pi-hole/#one-step-automated-install And if you want better anonymity, you can run Unbound as your own DNS, too (just don't expose it to the internet and accidentally make it a public DNS): https://docs.pi-hole.net/guides/dns/unbound/

That's wild. Sorry to hear it: this has been the best update for me since the jump to v7. My CPU now runs cooler, and draws around 25w less on average with no performance degradation, thanks to the improvements to the EPP AMD Pstate drivers. The Tips & Tweaks plugin (now known as Tips & Tweaks Next) has also been updated to easily change between them, too, and better support the different approaches to Intel & AMD power profiles. All my Dockers worked without issue from the get-go. I don't know why some people are having problems with Docker. I know the jump with the eailer 7.2.5 (or .6?) updated the Docker engine, which caused some troubles, but mine were quickly reolved. So I say again: well done, Unraid. I'm very pleased with this update.

Just FYI, since upgrading to Unraid 7.3.0, I've noticed a ~20w drop in power consumption. I believe it's due to improvements to the amd-pstate driver in the newer Kernel. (see my post at: https://forums.unraid.net/topic/198745-unraid-730-stable-now-available/page/3/#findComment-1623014 ) Tips & Tweaks currently has my server set using "Normal" governor as "Balanced Performance" in the drop-down, while the info column to the right reports it as "CPU Frequency Scaling - Driver: AMD Pstate EPP - Governor: Power Save". In the Unraid "Power Mode" setttings, I have it set to "Best Power Efficiency" I'm probably going to change the "Normal CPU Scalig Governor" setting in Tips & Tweaks to "Balanced Power" to see if it does anything meaningful. But may I ask: What's the relationship between the options in Tips & Tweaks and the Unraid Power Save setting? Does one cancel out the other (specifically for my AMD EPYC CPU - see sig)? Many thanks.

A day later, and yes: it seems that my UPS is reporting that my machine (of course, this includes the other peripherals attached to the UPS) is sitting around 90-100w when 'idle' (IE, no VM running, but all my usual Dockers running), whereas it used to idle around 120w-140w. Looks like the newer kernel is properly using amd-pstate rather than acpi-cpufreq. The min freq of the CPU has also changed from 545.0000 MHz to 429.5810 MHz. Great stuff!

Upgraded to 7.3.0 without issue. It seems to me that my power consumption has dropped? I think my CPU is falling into low-power states more easily/often now. Thanks for all the hard work ✌️

Can confirm: I had LMS as Bridge, and setting it to Host fixed the problem. So all good now. It seems that Docker 28+ broke UDP broadcast forwarding into bridge containers, which kills Slimproto discovery and connectivity for Squeezebox Radio / PiCorePlayer. So switching to Host is now considered best practice for LMS (indeed, I note that this container defaults to Host, but I have been using various LMS containers for so long that I continued to use Bridge).