EwanL

Members
  • Posts

    18
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

EwanL's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Well its accessible via the home network so I definitely wanted authentication on it. I appreciate the help anyway
  2. By UD do you mean Unassigned Devices? I have that installed but the share has no relation as far as i'm aware. SMB is disabled on the Unassigned Devices Settings page. This share was setup through the regular unraid shares page: The user account i'm accessing with via windows 10/SMB has Read/Write permissions to this share.
  3. Yeah i've tried 000, 002, 022 and it doesn't seem to have an effect. I've just changed it back to 000 and run another test and had the exact same result The folder permissions after download. All the other lines are folders after previously running the permission fixer tool.
  4. Hello Binhex and everyone else, I am experiencing access denied errors when trying to access files/folders recently downloaded with this binhex-qbittorrentvpn community app. I have a rootshare that I can read and write to from a networked windows 10 machine successfully with a username/password setup in unraid. When I run the permission fix tool over the Downloads folder the permissions are fixed and start working for the auth user setup in unraid. I believe it's related to the UMASK setting - but I haven't been able to figure out what specifically to change to resolve new downloads getting the wrong permissions set. The current docker settings are: UMASK 002 PUID 99 PGID 100 Is there anything you can suggest to help me fix the permissions issues?
  5. Thanks for this link. I've set the "Power Supply Idle Control" to "typical current idle" as per the link. I'll test and see how it goes.
  6. Happened again this morning. Syslog shows me disabling dockers and then slowly restarting them to see if there was anything jumping out in the logs. Nada. I then went out and came back a couple hours later to find it fully unresponsive again. Had to hard reboot to get it to respond. olympus-diagnostics-20230613-1135.zip
  7. I'm a bit confused about what the syslog should look like. I think i've configured it to save persistent logs to one of my shares - but again i can't see anything obvious as to why the server is shutting down. I have replaced the PSU with a brand new one. The server is no longer powering off - but it does randomly become unresponsive on the network. syslog-1686494658 syslog syslog-1686532690
  8. Twice in the last 3 or 4 days i've gone to access my unraid box (one time accessing a network share, the other trying to load Plex content) and found it powered off without my intervention. We haven't had any issues with any other devices so I don't believe it's due to power outages. I've had another PC on the same electrical circuit running all day unaffected. I looked through the diagnostics export but I can't see any indicators about errors or a crash. I've attached the file in case anyone can spot something I haven't. Cheers in advance Can anyone think of any reason why it would be turning itself off inexplicably? olympus-diagnostics-20230527-1911.zip
  9. I've had a handful of Out of Memory Errors happen in the last few weeks. They seem to coincide with a lockup of all the CPUs at 100%. At first i thought it as due to an extremely large torrent through binhex-qbittorrent docker. But i've since disabled that and had two more of these total freezes. I'd appreciate any insight. Diagnostics attached. olympus-diagnostics-20230301-0824.zip
  10. That did the trick. Thank you! I can't believe I missed the literal previous comment with the same issue.
  11. I have successfully installed the Piwigo docker from CA, but every time I edit the instance (to map a shared folder) I am presented with the Install.php configuration form again. It doesn't look like any configuration files are being saved to appdata/piwigo which I guess means the docker drives are being blown away each restart. Edit: has anyone else had this issue and managed to solve it?
  12. I followed the installation instructions for the Skin: https://www.mediawiki.org/wiki/Skin:Minerva_Neue and the extension, https://www.mediawiki.org/wiki/Extension:MobileFrontend: I tried manually installing both the 1.35 and 'latest' versions for both skin and extension, including modifying the LocalSettings.php to include the wfLoadSkin/Extension lines. When i tried accessing the wiki using the local IP, or via a reverse proxy (which otherwise works when i comment out the wfLoad lines) i get a 500 error in chrome and firefox. LocalSettings.php looks like:
  13. I'd love the walkthrough for the extension if you were able to get it working with your unRaid setup We can probably skip the skin though if it isn't needed for the extension to work.
  14. @d8sychain Yeah I tried the plugin separately and got the same error about requiring MW core version 1.35 or 1.36 (extension=latest). I'm not sure how to download the old 1.33.4 version of that extension though. Either way I'm in no hurry with it. Just a minor annoyance to not have a good mobile UI.