Everything posted by [email protected]
-
Parity drive reports "disk has read errors"
Hi, my parity drive reports "disk has read errors" I ran the SMART extended self-test and it reports "Completed without error" Should I ignore the problem in the Fix Common Problems plugin or do I need to do something to fix it? thebox-diagnostics-20240323-2258.zip thebox-smart-20240323-1553.zip
-
have had a few crashes
I have had a few crashes the last month or so, I was hoping last os update would fix it. I even turn off tdarr to see if it was stable. If some one could look at my diagnostics file I would appreciate it . edit: I was looking in docker.txt and it says level=warning msg="containerd config version `1` has been deprecated and will be removed in containerd v2.0, please switch to version `2` and in btrfs-usage.txt it says I have over 75gig unallocated on my cache drive, whats that about? thebox-diagnostics-20230725-1650.zip
-
Pterodactyl Panel Install & Configure on Unraid using DOCKER (2021)
since we don't have an .env file to edit I added trusted proxies to the pterodactyl template and the NGINX Specific Configuration that they talk about in the official documentation to my proxy configs for panel and node , https://pterodactyl.io/panel/1.0/additional_configuration.html#reverse-proxy-setup
-
Pterodactyl Panel Install & Configure on Unraid using DOCKER (2021)
Nice, I love your videos. could you update the text guide with a template for swag too please? not sure if mine is 100% correct or secure. I think I read some place that you shouldn't proxy the node thru Cloudflare but you did in the video. I'm still a little confused about that part. looking forward to pterodactyl video 2.0 and the time I have upload-speeds to use it.
-
Pterodactyl Panel Install & Configure on Unraid using DOCKER (2021)
I got it working at last. they should redo the video, they miss a lot. like half the config.yml , the text version is more accurate. https://docs.ibracorp.io/pterodactyl-docker-1/ I tested it with swag so i made my own proxy config. not sure if its secure or perfect. I'm not using pterodactyl now but I plan in the future when i get a better connection. I only tested to make a rust server and log in to it and that worked but i forgot to define the rcon port so ill have to do it again some day, its just for testing for now.
-
Pterodactyl Panel Install & Configure on Unraid using DOCKER (2021)
I never got the proxy config and the config.yml file to work only managed to proxy the panel so I never used it did you follow IBRACORP guide on youtube?
-
Pterodactyl Panel Install & Configure on Unraid using DOCKER (2021)
I'm trying to get pterodactyl working with swag. the docs is not made for unraid. https://pterodactyl.io/panel/1.0/webserver_configuration.html Any help is appreciated.
-
Display Name
can I change my display name to something else? don't want my mail here.
-
use DUO 2FA on Unraid login page
seen ppl ask for 2fa a few times before, don't think there's any option. You should not expose login page directly to the internet. just use it local or with a vpn. (wireguard is built in)
-
CronRAT and NginRAT malware
I have plex (32400 ), wireguard (51820) and swag, nextcloud, organizr and ombi. I used to have a rust game server (28015-28016). I think the problem started the one time i forgot that i left some ports open to test things, server cpu was at 100% and things stopped working, pulled the power on server and fixed my router settings. It was the same time ubiquiti had a log4j problem so I did a fw reset, update and change pw to router. now only Cloudflare is allowed to connect to 443 that I mapped to 1443 for swag but that was not the case back then. everything works but I'm worried since I can't get rid off the LD_L1BRARY_PATH thingy.
-
CronRAT and NginRAT malware
thebox-diagnostics-20220126-0856.zip
-
CronRAT and NginRAT malware
If i start over with a new usb, is there anything i can/should save from my previous usb?
-
NGINX Proxy and Cloudflare
did you try your address with https?
-
NGINX Proxy and Cloudflare
why not the swag container? I don't know much but you don't need 80 if you do ssl cert via Cloudflare. it uses dns, and I limit connections to 443 so that only traffic from Cloudflare gets through. https://www.cloudflare.com/ips/
-
Log4J Attack on Docker container! How bad is the Damage ?
are you sure it was log4j? did you test your containers with log4jscan?
-
CronRAT and NginRAT malware
same thing without dockers. root@Thebox:~# sudo grep -al LD_L1BRARY_PATH /proc/*/environ | grep -v self/ /proc/14386/environ root@Thebox:~# sudo grep -al LD_L1BRARY_PATH /proc/*/environ | grep -v self/ /proc/14396/environ root@Thebox:~# ps PID TTY TIME CMD 14035 pts/0 00:00:00 bash 14425 pts/0 00:00:00 ps root@Thebox:~#
-
CronRAT and NginRAT malware
I cant kill the process since its a new one every time and don't even show up with ps. I was thinking of making a new Unraid usb and transferring my key but that sounds like a last resort, I tried scanning with antivirus but nothing. any feedback would be appreciated.
-
CronRAT and NginRAT malware
I also see different process ID every time I run sudo grep -al LD_L1BRARY_PATH /proc/*/environ | grep -v self/ But I blocked the payload ip, what can I do more? root@Thebox:~# sudo grep -al LD_L1BRARY_PATH /proc/*/environ | grep -v self/ /proc/10704/environ root@Thebox:~# sudo grep -al LD_L1BRARY_PATH /proc/*/environ | grep -v self/ /proc/10759/environ root@Thebox:~# sudo grep -al LD_L1BRARY_PATH /proc/*/environ | grep -v self/ /proc/10895/environ root@Thebox:~# sudo grep -al LD_L1BRARY_PATH /proc/*/environ | grep -v self/ /proc/10907/environ root@Thebox:~# ps PID TTY TIME CMD 10685 pts/0 00:00:00 bash 11253 pts/0 00:00:00 ps root@Thebox:~# sudo grep -al LD_L1BRARY_PATH /proc/*/environ | grep -v self/ /proc/11451/environ root@Thebox:~# crontab -l # If you don't want the output of a cron job mailed to you, you have to direct # any output to /dev/null. We'll do this here since these jobs should run # properly on a newly installed system. If a script fails, run-parts will # mail a notice to root. # # Run the hourly, daily, weekly, and monthly cron jobs. # Jobs that need different timing may be entered into the crontab as before, # but most really don't need greater granularity than this. If the exact # times of the hourly, daily, weekly, and monthly cron jobs do not suit your # needs, feel free to adjust them. # # Run hourly cron jobs at 47 minutes after the hour: 47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null # # Run daily cron jobs at 4:40 every day: 40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null # # Run weekly cron jobs at 4:30 on the first day of the week: 30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null # # Run monthly cron jobs at 4:20 on the first day of the month: 20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null