Peuuuur Noel

You can try to post the screenshot of the inspector on the plex forum, maybe the moderator will have an idea about it.

@Jase If it was a driver or GC related issue, I think you should also have this same issue on local web client and desktop/tv/mobile app. They use same API calls to your plex server. Just to rule out this possibility, have you tried clearing browser cache or testing in private browsing? (I know it sounds stupid but sometimes it solves connection issue). Like the plex forum moderator on the post you linked below, I also see a client disconnect in your logs.

@Jase I see a lot of ns_binding_aborted (page load has been stop), ns_error_connection_refused (refused by server) and even a CORS error (refused by security policy). Remote web client is not allowed to access your playback content on your local server due to security policy issue.

Ok, so if the issue is only on remote web client, I don't think it's drivers issue but a network issue. Check if you have network error on your browser by using the Inspector (right click on the page, Inspect) and checking connections in the Network tab while playing a file.

Which plex container are you running? Official, binhex, linuxserver, etc...? You access to web client through https://app.plex.tv/ (remote plex web server) or local ip address (web client embedded in container)? Remote and local web clients are distinct and may differ. Have you tried to start from a clean plex appdata folder? Stop the container, rename/move/backup plex appdata folder, start it again, claim your server (if needed), create a new library for the test and test a playback. To rollback to your previous install, put back your old plex appdata folder.

I don't know if the tooltip was present in "small" style, but there is something in the code that prevents it.

@Meniak @AgentXXL As I thought, this file wasn't changed when you updated this plugin (maybe locked by a process?). Reinstalling it or restarting your server will fix it.

@AgentXXL @carthis @Meniak Strange behavior, please can you check if these changes (L153-155 and L179-180) have been applied in this file? /usr/local/emhttp/plugins/nut/nutFooter.page It continues to split string on semicolon ";" even if it's no longer in code.

Which version of Unraid are you running and what browsers are you using? Also can you post a screenshot to see how it looks? Thx

@SimonF yes, I noticed it a few minutes ago. PR done. Sorry for this mistake.

Indeed. Value sent by your UPS used even if you manually set Nominal Real Power with different value from your UPS (and greater than 0). Fixed on my side, PR sent to @SimonF

@SimonF I made some changes in code for better calculation and display in settings/footer/dashboard between apparent power and real power, depending of what NUT retrieves from the UPS. Feel free to review it. https://github.com/SimonFair/NUT-unRAID/pull/4

@SimonF yes, ups.realpower has a wrong value. If @xsweb can do an usbhid-ups for a minute it should help to check if raw value for this UPS is reliable or not.

I think nut reports wrong value from the UPS. In the screen cap from his post ups.power.nominal=5 with a 1200VA UPS (PowerWalker VI 1200 SHL), should be 1200. Same for ups.realpower=0 with load at 10%. In general in this plugin, maybe I'm wrong, there are some mistakes in display of values for the power. Mixes of apparent power (VA) and real/true power (W), apparent power displayed in Watt and not in VA.

The "/run" is full because the Nvidia runtime logs are filling it up. Update your Nvidia plugin and restart your server. Log level was changed to reduce logs. Issue discussed in this post.