sdballer

I am periodically getting files that I cannot open. Is there a way to set krusader as root?

Yup, did a reinstall awhile back and clicked the wrong one! Back on yours again! Thanks.

After some updates I am no longer abled to edit files? I installed kate via apt-get update, apt-get install kate and this works, but I have to do it every time the docker is rebooted. Is there no editor included anymore?

Are there any differences from this lsio docker opposed to the other labeled as “official” inside community apps?

Would be great to see an option to automatically include new docker apps into a default folder.

This circumvents the "I have read checkbox" ... just fyi.

Any reason why I can’t move directories and files together? Keep getting 500 error. I can move files into folders, no problem.

same problem here!

NUT 404 on WebUI?

Just the logs folder or the entire docker is ok at 755?

Started getting this error recently. ⚠ warning Error: Command failed: logrotate /etc/logrotate.d/nginx-proxy-manager error: skipping "/data/logs/default-host_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/fallback_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-10_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-1_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-2_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-3_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-4_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-5_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-6_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-7_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-8_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-9_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/redirection-host-1_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/redirection-host-2_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/redirection-host-3_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/default-host_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/fallback_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-10_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-1_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-2_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-3_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-4_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-5_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-6_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-7_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-8_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/proxy-host-9_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/redirection-host-1_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/redirection-host-2_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/redirection-host-3_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. /mnt/user/appdata/nginxproxymanager: total 0 drwxrwxrwx 1 root root 30 Nov 26 2021 ./ drwxrwxrwx 1 nobody users 894 Jul 31 11:03 ../ drwxrwxrwx 1 root root 132 Aug 2 18:06 data/ drwxrwxrwx 1 root root 114 Aug 2 18:06 letsencrypt/ /mnt/user/appdata/nginxproxymanager/data: total 484 drwxrwxrwx 1 root root 132 Aug 2 18:06 ./ drwxrwxrwx 1 root root 30 Nov 26 2021 ../ drwxrwxrwx 1 root root 0 Nov 26 2021 access/ drwxrwxrwx 1 root root 0 Nov 26 2021 custom_ssl/ -rw-rw-rw- 1 root root 495616 Aug 2 18:06 database.sqlite drwxrwxrwx 1 root root 0 Nov 26 2021 letsencrypt-acme-challenge/ drwxrwxrwx 1 root root 1410 Jul 30 22:00 logs/ drwxrwxrwx 1 root root 186 Nov 26 2021 nginx/ /mnt/user/appdata/nginxproxymanager/letsencrypt: total 0 drwxrwxrwx 1 root root 114 Aug 2 18:06 ./ drwxrwxrwx 1 root root 30 Nov 26 2021 ../ drwxrwxrwx 1 root root 56 Nov 26 2021 accounts/ drwxrwxrwx 1 root root 36 Nov 26 2021 archive/ drwxrwxrwx 1 root root 112 Nov 26 2021 credentials/ drwxrwxrwx 1 root root 720 Jul 24 20:00 csr/ drwxrwxrwx 1 root root 720 Jul 24 20:00 keys/ drwxrwxrwx 1 root root 48 Nov 26 2021 live/ drwxrwxrwx 1 root root 66 Jul 24 20:00 renewal/ drwxrwxrwx 1 root root 26 Nov 26 2021 renewal-hooks/

Getting tons of "unable to reach the origin service" errors, but working fine... Anyway to solve that?

I can't move a directory with files inside from disk1 to disk2 (using /mnt/ as the share path), but I can create a directory and move those files. How come I am getting 500 error when trying to move the folder and files together, but separately no problem? Log: 2022/07/07 16:34:46 /data/downloads/SomeMovie (2022) (1080)/: 500 192.168.1.31 read /srv/data/downloads/SomeMovie (2022) (1080): is a directory

Same problem.

I keep getting 500 server error when trying to move a folder. What could be the issue?

When the array automatically starts a parity check, I pause and resume without enough duration to fully complete the check. Therefore once the resume function starts, it will keep going into the second day during the time when I would want the system to pause. Basically the issue is the initial pause is only a few hours. So I need to check the parity over more than just 1 day, without disrupting high load times with users.

Can I add multiple cron times per pause, resume? The reason I ask is being once paused and resumed, the resume continues too long where it would normally be paused on the 2nd and 3rd day. I need to pause, resume, pause, resume to fully complete a check without disturbing primary working times. Or an option to repeat until check is complete, while maintaining pause time(s). Pause; 0 2 2 * *, 0 2 3 * * Resume; 0 7 1 * *, 0 7 2 * *

Offline version yet

Does this docker work if my isp blocks port 80? I tried the other guys repo and it was a no go so I stuck with swag. Hoping to finally use npm…

Hello - I am running the original "Pi-Hole Template" and I recently found out about this DoT DoH version. After downloading DoT DoH, I have disabled/turn off the original PiHole. I have matched all the same fields into the DoT DoH version: 1) Fixed IP : 192.16.1.198 2) Server IP : 192.16.1.198 3) Router DNS 1/2 : 192.168.1.198 After doing so I am unable to access the WebUI. I am however able to access it if I switch the IP to xxx.197 and turn back on the original Pi at xxx.198. In this situation I am able to run both UIs, but clearly the DoTDoH is not actively enabled on my router. Can anyone explain what I might be doing incorrectly here? Big thanks

Does this require port 80 to be open? My ISP blocks that and I only have access to 443/SSL. I believe this was an issue before when I tried using DNS validation... is this still accurate as of today? thnx

Is there any way to remove/disable the login password prompt?

I modified this file: /mnt/cache/appdata/letsencrypt/www/index.html to have: <meta http-equiv="refresh" content="0; URL='http://www.google.com'" /> This just redirects to google.com since I don't use my root domain.

Yes I was able to get it working with Letsencrypt. Sure would be great with your user interface!!

How do deal with port 80 being blocked by ISP?