jfoxwoosh

Thank you @sixkittens . I just upgraded from 7.2.5 to 7.3.1 and ran into this problem. The VM (Linux Mint 22.3) boot up fine at first, but after a few minutes, it will suffer kernel panic with exit code = 0x0000008b. Enabling "Migratable" option in the VM template fix the issue for now.

For the past two weeks, I have been refraining myself from using mobile phone browser and Windows 11 Edge browser to access server's webui, and no trace of php-fpm warning in syslog. During this period, I have only used my Linux Mint laptop and VM's firefox browser to access the webui. My next experiment will be using Linux Mint's flatpak Mircosoft Edge browser and see the warning can be reproduced.

@bmartino1 , thanks for the reply. My appdata backup is configured to run manually, so I can rule that out for now. I have noticed, the timestamp of this php-fpm warning appearing lining up with me simply login into the webui with a browser. Although not always, but it has a high chance of the warning appearing when I use my iPhone's Firefox browser and Windows 11 Edge browser to access the server's webui. I am now testing using the Firefox browser on Linux Mint laptop and to see if this will happen or not.

Noticed this warning appearing in my log since 7.2 update. I am wondering if this is related.

Anyone interested, please visit this bug report and upvote.

Thanks. I was about to post question about this error as well. I am glad this is nothing to be of concern.

Thanks to @Salty2011 's script, I am happy to report ReBAR is successfully enabled in Win11 VM. @Salty2011 , for linux VM, does it need the xml edits? Or those edits are only for Windows VM? Platform: Unraid: 7.2 CPU: AMD Ryzen 9 5900x Motherboard: MSI B550 Gaming Plus GPU: AMD RX 6800 XT

Wow! Didn’t realize it was built-in. I copied the conf file, removed the plugin, put the conf file back, and it is back in business. Thanks!

updated to unraind 7.2, and the rclone setting page show absurdly large installed version. The version number will keep on increasing over time. Removed and reinstall doesn't correct it.

Anyone use music assistant and tried to subscribe to the uncast podcast? I tried both through 1) spotify and 2) RSS music providers, but uncast doen't load properly compared to other subscribed podcasts. Here is a snippet of the log: 2025-09-19 09:46:14.732 INFO (MainThread) [music_assistant] Loaded music provider Podcast RSS Feed 2025-09-19 09:47:37.187 WARNING (MainThread) [ffmpeg.9574] [https @ 0x150dbb904900] HTTP error 403 Forbidden [https @ 0x150dbb904900] Will reconnect at 0 in 0 second(s). [https @ 0x150dbb904900] HTTP error 403 Forbidden [https @ 0x150dbb904900] Will reconnect at 0 in 1 second(s). [https @ 0x150dbb904900] HTTP error 403 Forbidden [https @ 0x150dbb904900] Will reconnect at 0 in 3 second(s). [https @ 0x150dbb904900] HTTP error 403 Forbidden [https @ 0x150dbb904900] Will reconnect at 0 in 7 second(s). [https @ 0x150dbb904900] HTTP error 403 Forbidden [https @ 0x150dbb904900] Will reconnect at 0 in 15 second(s). [https @ 0x150dbb904900] HTTP error 403 Forbidden [in#0 @ 0x150dbb902c00] Error opening input: Server returned 403 Forbidden (access denied) Error opening input file https://www.buzzsprout.com/1746902/episodes/8458203-why-you-should-own-your-own-server.mp3. Error opening input files: Server returned 403 Forbidden (access denied) 2025-09-19 09:47:37.187 ERROR (MainThread) [music_assistant.audio.cache] Error while creating cache for podcastfeed--eBAzSKgm://podcast_episode/Buzzsprout-8458203: FFMpeg error 8 2025-09-19 09:47:37.188 WARNING (MainThread) [music_assistant.player_queues] Skipping unplayable item Why You Should Own Your Own Server (podcastfeed--eBAzSKgm://podcast_episode/Buzzsprout-8458203) 2025-09-19 09:48:03.904 WARNING (MainThread) [ffmpeg.9575] [https @ 0x14e02da8b900] HTTP error 403 Forbidden [https @ 0x14e02da8b900] Will reconnect at 0 in 0 second(s). [https @ 0x14e02da8b900] HTTP error 403 Forbidden [https @ 0x14e02da8b900] Will reconnect at 0 in 1 second(s). [https @ 0x14e02da8b900] HTTP error 403 Forbidden [https @ 0x14e02da8b900] Will reconnect at 0 in 3 second(s). [https @ 0x14e02da8b900] HTTP error 403 Forbidden [https @ 0x14e02da8b900] Will reconnect at 0 in 7 second(s). [https @ 0x14e02da8b900] HTTP error 403 Forbidden [https @ 0x14e02da8b900] Will reconnect at 0 in 15 second(s). [https @ 0x14e02da8b900] HTTP error 403 Forbidden [in#0 @ 0x14e02da89c00] Error opening input: Server returned 403 Forbidden (access denied) Error opening input file https://www.buzzsprout.com/1746902/episodes/8565052-all-about-vms-and-gpu-passthrough.mp3. Error opening input files: Server returned 403 Forbidden (access denied) 2025-09-19 09:48:03.904 ERROR (MainThread) [music_assistant.audio.cache] Error while creating cache for podcastfeed--eBAzSKgm://podcast_episode/Buzzsprout-8565052: FFMpeg error 8 2025-09-19 09:48:03.905 WARNING (MainThread) [music_assistant.player_queues] Skipping unplayable item All about VMs and GPU Passthrough (podcastfeed--eBAzSKgm://podcast_episode/Buzzsprout-8565052) 2025-09-19 09:48:30.623 WARNING (MainThread) [ffmpeg.9576] [https @ 0x14bd2c03e900] HTTP error 403 Forbidden [https @ 0x14bd2c03e900] Will reconnect at 0 in 0 second(s). [https @ 0x14bd2c03e900] HTTP error 403 Forbidden [https @ 0x14bd2c03e900] Will reconnect at 0 in 1 second(s). [https @ 0x14bd2c03e900] HTTP error 403 Forbidden [https @ 0x14bd2c03e900] Will reconnect at 0 in 3 second(s). [https @ 0x14bd2c03e900] HTTP error 403 Forbidden [https @ 0x14bd2c03e900] Will reconnect at 0 in 7 second(s). [https @ 0x14bd2c03e900] HTTP error 403 Forbidden [https @ 0x14bd2c03e900] Will reconnect at 0 in 15 second(s). [https @ 0x14bd2c03e900] HTTP error 403 Forbidden [in#0 @ 0x14bd2c03cc00] Error opening input: Server returned 403 Forbidden (access denied) Error opening input file https://www.buzzsprout.com/1746902/episodes/8646346-home-automation.mp3. Error opening input files: Server returned 403 Forbidden (access denied) 2025-09-19 09:48:30.623 ERROR (MainThread) [music_assistant.audio.cache] Error while creating cache for podcastfeed--eBAzSKgm://podcast_episode/Buzzsprout-8646346: FFMpeg error 8 2025-09-19 09:48:30.624 WARNING (MainThread) [music_assistant.player_queues] Skipping unplayable item Home Automation (podcastfeed--eBAzSKgm://podcast_episode/Buzzsprout-8646346)

Spent all day today getting the weewx container to work. I am putting down some of the pitfalls I encountered here hoping it will be useful to anyone in the future. Remove MQTT usb device mapping: if not passing through any device remove the mapping Fix the appdata folder permission: after hitting install in the community app, it will try to create the "weewx" folder in appdata. However, the folder need manual permission fix. I just gave it 777. Running the container for the first time: after fixing the folder permission, start the container. This time it will generate weewx.conf file and many other stuff, and the container will exit out. Leave the weewx.conf file unmodified for now. it will default to simulator driver. Start the container again, and it should run normal now. Install paho-mqtt module: MQTT extension requires a specific paho-mqtt module (see here). Open the container console, cd to /data folder, and run the pip command pip install paho-mqtt==1.6.1 Install extension: the container description said it comes bundle with Interceptor and mqtt, however, I found it not being the case. Extensions need manual install by using weectl command. Since the weewx.conf is not in the default location. --config=/path/to/weewx.conf option is needed. Open the container console and run the weectl command like the example below. weectl extension install <extension url> --config=/data/weewx.conf MQTT: https://github.com/matthewwall/weewx-mqtt/archive/master.zip Interceptor: https://github.com/matthewwall/weewx-interceptor/archive/master.zip Pay attention to the owner/permission of weewx.conf: the container should still be running without any error up to this point. Now we can stop the container and start modifying the weewx.conf. Before editing the file, note down the owner and permission of the file. I noticed this changing depending on how you edit the file. Don't forget to do Step 3 for MQTT extension.

I am seeing this as well. Tips & Tweaks plugin cannot change the EPP to anything other than "performance" when using amd-pstate-epp. The two power modes in 7.1.x corresponds to: Best power efficiency -> amd_pstate_epp powersave performance Best performance -> amd_pstate_epp performance performance No matter which setting I choose in Tips & Tweak, the EPP always got set to "performance" even though "balance_performance" or "balance_power" is selected. I have to use terminal to manually edit the EPP. e.g. echo "balance_performance" | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/energy_performance_preference @IronBeardKnight , if you want the old power modes back, you can try this.

Thank you all for the replies. p-state is keyword I needed for further googling and learning. I found these from reddit and phoronix very helpful. After some experimenting and changing the setting, 7.1.x power modes will corresponds to the following: (note1: by default for AMD Ryzen 5900x platform without modification to syslinux.cfg) (note2: I kept the same nomenclature as the phoronix article) Best power efficiency -> amd_pstate_epp powersave performance Best performance -> amd_pstate_epp performance performance Not sure if it is bug or by-design, the Tips & Tweaks plugin cannot change the Energy Performance Preference to anything other than "performance". To change that, I have to use the command found in the reddit post. echo "balance_performance" | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/energy_performance_preference I have since changed the preference to "balance performance" (making it amd_pstate_epp powersave balance_performance) and am quite happy with the result.

My system has Ryzen 5900x. Updated from 7.0.1 to 7.1.3, and the Balanced operation became unavailable, which was available before. Looking into "tips and tweaks" plug-in, there seems to be two new power modes option: Balanced Performance & Balanced Power However, none of the setting seems to be limiting the power usage. Before the update, best power efficiency mode will limit the cpu turbo, but not anymore with 7.1.3

I think this is fair. I love UnRaid, and I want limetech to stay around. You buy a license to a version of the software and got to keep using it with no subscription fee. If you want newer version/feature, then you pay a bit extra for the upgrade. As long as this "extra" is not outrageously expensive.

Tried this on my system: Ryzen 5900x MSI B550 Motherboard RX 6800XT UnRaid 6.12.3 I followed the instructions posted here, and tried it on one of my existing Win11 VM, which ended it with Code43. I then tried creating a Win11 VM from scratch, and it caused my host to reboot during the VM OS installation. After some more tries, it always end up causing the host to reboot. To avoid host reboot during Win11 VM creation, I had to disable ReBAR in bios.

Thank you for the insight. Does the messages in the log indicate any error? Or it is safe to ignore?

I have noticed my dashboard log size reporting to be 8% used. From my past experience, I have never seen this go over 2%, so I checked the files size by "du -sh /var/log/*" and found out the stdout.log is 9MB and have been slowly growing to near 9.5MB in the span of 2 hr. A quick look into the content of this log, I found it is the same messages repeating over and over again by the seconds. My array is currently spinned down and there is no file activities going on. 85803 [2023-07-26T09:56:35.934] [6943] [DEBUG] [app] Array was updated, publishing event 85804 [2023-07-26T09:56:40.934] [6943] [DEBUG] [emhttp] Loading state file for disks 85805 [2023-07-26T09:56:50.936] [6943] [DEBUG] [emhttp] Loading state file for disks 85806 [2023-07-26T09:56:50.940] [6943] [DEBUG] [emhttp] Loading state file for shares 85807 [2023-07-26T09:56:55.940] [6943] [DEBUG] [app] Array was updated, publishing event 85808 [2023-07-26T09:57:00.935] [6943] [DEBUG] [emhttp] Loading state file for shares 85809 [2023-07-26T09:57:00.938] [6943] [DEBUG] [emhttp] Loading state file for disks 85810 [2023-07-26T09:57:05.941] [6943] [DEBUG] [app] Array was updated, publishing event 85811 [2023-07-26T09:57:10.936] [6943] [DEBUG] [emhttp] Loading state file for disks 85812 [2023-07-26T09:57:20.938] [6943] [DEBUG] [emhttp] Loading state file for disks 85813 [2023-07-26T09:57:30.937] [6943] [DEBUG] [emhttp] Loading state file for disks 85814 [2023-07-26T09:57:30.941] [6943] [DEBUG] [emhttp] Loading state file for shares 85815 [2023-07-26T09:57:35.941] [6943] [DEBUG] [app] Array was updated, publishing event 85816 [2023-07-26T09:57:39.961] [6943] [DEBUG] [graphql] upc connected 85817 [2023-07-26T09:57:40.025] [6943] [DEBUG] [graphql] Subscribing to servers 85818 [2023-07-26T09:57:40.050] [6943] [DEBUG] [graphql] Subscribing to vars 85819 [2023-07-26T09:57:40.051] [6943] [DEBUG] [graphql] Subscribing to owner 85820 [2023-07-26T09:57:40.052] [6943] [DEBUG] [graphql] Subscribing to config 85821 [2023-07-26T09:57:40.053] [6943] [DEBUG] [graphql] Subscribing to registration 85822 [2023-07-26T09:57:40.939] [6943] [DEBUG] [emhttp] Loading state file for disks 85823 [2023-07-26T09:57:40.943] [6943] [DEBUG] [emhttp] Loading state file for shares 85824 [2023-07-26T09:57:43.418] [6943] [DEBUG] [graphql] upc disconnected. 85825 [2023-07-26T09:57:43.765] [6943] [DEBUG] [graphql] upc connected 85826 [2023-07-26T09:57:43.809] [6943] [DEBUG] [graphql] Subscribing to servers 85827 [2023-07-26T09:57:43.873] [6943] [DEBUG] [graphql] Subscribing to vars 85828 [2023-07-26T09:57:43.874] [6943] [DEBUG] [graphql] Subscribing to owner 85829 [2023-07-26T09:57:43.874] [6943] [DEBUG] [graphql] Subscribing to config 85830 [2023-07-26T09:57:43.875] [6943] [DEBUG] [graphql] Subscribing to registration 85831 [2023-07-26T09:57:50.939] [6943] [DEBUG] [emhttp] Loading state file for disks 85832 [2023-07-26T09:57:50.942] [6943] [DEBUG] [emhttp] Loading state file for shares 85833 [2023-07-26T09:57:55.942] [6943] [DEBUG] [app] Array was updated, publishing event 85834 [2023-07-26T09:58:00.939] [6943] [DEBUG] [emhttp] Loading state file for shares 85835 [2023-07-26T09:58:00.942] [6943] [DEBUG] [emhttp] Loading state file for disks 85836 [2023-07-26T09:58:05.944] [6943] [DEBUG] [app] Array was updated, publishing event 85837 [2023-07-26T09:58:10.940] [6943] [DEBUG] [emhttp] Loading state file for disks 85838 [2023-07-26T09:58:20.940] [6943] [DEBUG] [emhttp] Loading state file for shares 85839 [2023-07-26T09:58:20.944] [6943] [DEBUG] [emhttp] Loading state file for disks 85840 [2023-07-26T09:58:25.946] [6943] [DEBUG] [app] Array was updated, publishing event 85841 [2023-07-26T09:58:30.941] [6943] [DEBUG] [emhttp] Loading state file for disks

Don't really understand all these personally, so I just did some trials and errors. I found out it is when "add_header X-Frame-Options "SAMEORIGIN" always" is enabled in ssl.conf that will break the integration between nextcloud and onlyoffice. Upon further reading, this seems to be the expected behavior. https://forum.onlyoffice.com/t/error-message-when-opening-creating-a-document-from-update/4392/12 For anyone using swag and its template for nextcloud reverse proxy, comment out "proxy_hide_header X-Frame-Options" in the template so to pass nextcloud's security test as suggested in nextcloud's github issue #8550. Don't enable it within ssl.conf which will add this header to any proxy conf that calls for this file. # Hide proxy response headers from Nextcloud that conflict with ssl.conf # Uncomment the Optional additional headers in SWAG's ssl.conf to pass Nextcloud's security scan proxy_hide_header Referrer-Policy; proxy_hide_header X-Content-Type-Options; #proxy_hide_header X-Frame-Options; proxy_hide_header X-XSS-Protection;

@bigbangus I can see documentserver's welcome page from its subdomain url. Here is the update. If I revert the ssl.conf to swag's initial template state, then my onlyoffice works again. However, the only changes I made are in accordance to swag nextcloud's proxy template so to pass the nextcloud's security check (e.g. enabling add_header X-Frame-Options..., etc.). How do you deal with this?

@bigbangus I checked my reverse proxy conf file and noticed the default from swag's documentserver proxy conf template uses http/Port80 instead of https/Port443. I changed it to https and 443 just like yours and clear the cache of my browser. After restarting swag, I can access documentserver from my public domain url just fine. However, I am still suffering the same issue. No idea what is going on. For now I have setup up Collabora. Will revisit this if there is new update to either documentserver or the onlyoffice nextcloud plug in.

I encounter an issue similar to the post. The host (6.12.2) GUI became unresponsive but all my docker services (except binhex-qbittorrentvpn) and VM were still functioning normal. After SSH in and kill the qbittorrent container process, the host GUI became available again. There are some error events logged in the syslog. Jul 9 01:58:04 Gandor kernel: CPU: 1 PID: 10534 Comm: qbittorrent-nox Tainted: P O 6.1.36-Unraid #1 Jul 9 01:58:04 Gandor kernel: Call Trace: I tried switching over to hotio's qbittorrent-vpn docker, but I also saw related error to "qbittorrent-nox segfault" when stop/restart the container. I am not sure if these are related or not. Update: I switched over to hotio's qbittorrent-vpn "legacy" version, which uses libtorrent 1.2.x. So far has not see the segfault error message. I will keep this setup for the next 2 weeks or so and report back any findings. I think my issue is related to this. gandor-diagnostics-20230709-1925.zip

+1, I am having this problem as well. As far as I can tell, documentserver is working correctly. I can access through reverse proxy, and the example editor test works just fine. The nextcloud's onlyoffice plugin can connect to the document server. However, nextcloud can no longer open any of the office files within the browser. Using Edge/Chrome will result in the same error message "refused to connect." Using firefox will either show a blank page, or a warning message saying it cannot open an already embedded page within the tab.

Hi. Where can I find the updater.phar in this container? It is not in the usual /var/www/nextcloud directory.