kricker

Members
  • Content Count

    756
  • Joined

  • Last visited

Community Reputation

4 Neutral

About kricker

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. I can't seem to get this to work at all. I am think it has more to do with my Google Nest router, but I am not sure. Is this using port 7 to send the magic packet? I am sniffing for the packet to reach my PC on port7 and port 9 but it never receives the packet.
  2. @Observe I tried out doublecommander docker and the search feature works in it.
  3. I am trying the Dolphin docker. When I use the "Find" feature it just replies "Invalid Protocol". Is there a way to enable the searching feature?
  4. I was having issues getting ProFTP running again after upgrading Unraid to version 6.9.1 using ProFTP 1.3.7a. ProFTP just would not start and I could not get anything in the log. I tried enabling debug logging, but still nothing. I removed the plugin and did a clean install multiple times and still nothing. Then I stumbled upon running this command in terminal sudo -u root /usr/local/SlrG-Common/usr/local/sbin/proftpd -c /etc/proftpd.conf which resulted in this error: 2021-03-30 20:12:19,459 TOWER proftpd[24730]: fatal: unknown configuration directive 'IdentLookups' on line 24 of '
  5. Yeah, should be easy enough. Thanks for letting me know what loop2 was!
  6. Ahh okay. The entire image...so all my dockers?
  7. I just saw this on boot up after a random system crash. The tower just became inaccessible vis web or SAMBA. I attached a monitor and after reboot I saw some strange errors after it got to the login prompt. I am currently in the middle of a parity rebuild (replacing a possible failing drive) so I don't want to re-power down just yet, but here is a snippet of the log and I'll attach the full diagnostic as well. Doing an intial search I saw some threads somewhat similar where new RAM seemed to fix the issue. I've had this system running perfect for years...I guess there is a chance the RAM has g
  8. I tried setting the users directory to that disk mount point such as ftpuser /mnt/disks/test, but that didn't seem to work. The users account still went to /mnt/usr and saw all the shares as normal. I'll try those two options you mentioned. Thanks! I think I must have something in my config file keeping everyone jailed to /mn/usr, because setting anyone to just ftpuser has the same result. I'll do some diggining.
  9. I am trying to add access to a disk outside of the array that is mounted using Unassigned devices. Is that possible?
  10. I just installed UD plus in Unraid 6.8.0 and I am a little confused. I my WebUI it looks different than before. I don't see the mount buttons and it just all looks different. I'm trying to get things setup so in Krusader I can copy files from a USB drive to the RAID, but I can't even seem to find where the disk is mounted as I no longer have a /mnt/disks location. I've probably skipped or looked over something. Any pointers?
  11. I did read the notes, but maybe I was in one rum too many. I guess I shouldn't drink and post 🥺I think Squid hit the issue. I am digging into it properly now. Edit: And that was indeed the issue. Sorry!
  12. I upgraded a server running 6.4.2 to 6.8.0. I did a manual upgrade copying all files except for the config folder. There server boots and works fine except for the web UI. When i login in all I get is the top banner stating the version and up time. The gray bar below is empty and there is nothing else on the page. Chrome has asked me multiple times to translate the page?!
  13. I upgraded a server running 6.4.2 to 6.8.0. I did a manual upgrade copying all files except for the config folder. There server boots and works fine except for the web UI. When i login in all I get is the top banner stating the version and up time. The gray bar below is empty and there is nothing else on the page. Chrome has asked me multiple times to translate the page?!
  14. I just ran into this issue on a Hp microserver with 4TB WD Reds. I could not get write cache enabled to stick on the drives after a reboot. I thought it may be a firmware issue with the drives. I checked another system which has the same drives and write caching was enabled as default. Turned out to be a setting in the HP micorserver's BIOS. I flipped that and write caching was now enabled as default. I thought I might add this here for anyone else that may run across this issue.