Torrent Helper 📢
RED's IRC server has been affected by a DDOS attack. This is the post from staff in the forum: "Hi all, As you may have noticed, our IRC server is currently offline. Our first IRC server outage was due to an unexpected, unjustified ddos attack. We managed…
#RED
[Redacted | RED] - Credential Stuffing Attack
Many of you may be aware of an ongoing credential stuffing attack. This is a kind of attack where stolen account credentials containing lists of usernames and passwords are used to gain access to user accounts. You may have seen messages in your inbox indicating login failures.
The key to thwarting these types of attacks are to use a unique and strong passwords to secure your RED account. Two factor authentication is an extra step that is strongly recommended. Instructions on how to enable 2FA on your RED account is available at Two-Factor Authentication.
You are responsible for your account, even if it is compromised. Make sure you keep your account safe. If your RED password is a password you use on other sites, please change your password now.
____
إدارة تراكر RED تقول أن الموقع يتعرض لإختراق للأسف.
هذا النوع من الاختراق اللذي بناءاً عليه يتم سرقة قائمة من أسماء المستخدمين وكلمات مرورهم للوصول إلى حساباتهم.
من الممكن أنك لاحظت انه تم فشل تسجيل دخول لحسابك من مكان آخر.
حل هذه المشكلة يتم عن طريق استخدام كلمة مرور مستقلة عن أي موقع آخر + تفعيل 2FA.
إدارة RED تنوّه ان المستخدم مسؤول عن حسابه حتى لو تم سرقته!
لذلك يرجى الحذر و اتخاذ الاحتياطات.
جدير بالذكر أن التراكر أيضاً تعرض لهجمات DDOS قبل ٣ أيام على سيرفرهم في IRC.
#privateTR
[Redacted | RED] - Credential Stuffing Attack
Many of you may be aware of an ongoing credential stuffing attack. This is a kind of attack where stolen account credentials containing lists of usernames and passwords are used to gain access to user accounts. You may have seen messages in your inbox indicating login failures.
The key to thwarting these types of attacks are to use a unique and strong passwords to secure your RED account. Two factor authentication is an extra step that is strongly recommended. Instructions on how to enable 2FA on your RED account is available at Two-Factor Authentication.
You are responsible for your account, even if it is compromised. Make sure you keep your account safe. If your RED password is a password you use on other sites, please change your password now.
____
إدارة تراكر RED تقول أن الموقع يتعرض لإختراق للأسف.
هذا النوع من الاختراق اللذي بناءاً عليه يتم سرقة قائمة من أسماء المستخدمين وكلمات مرورهم للوصول إلى حساباتهم.
من الممكن أنك لاحظت انه تم فشل تسجيل دخول لحسابك من مكان آخر.
حل هذه المشكلة يتم عن طريق استخدام كلمة مرور مستقلة عن أي موقع آخر + تفعيل 2FA.
إدارة RED تنوّه ان المستخدم مسؤول عن حسابه حتى لو تم سرقته!
لذلك يرجى الحذر و اتخاذ الاحتياطات.
جدير بالذكر أن التراكر أيضاً تعرض لهجمات DDOS قبل ٣ أيام على سيرفرهم في IRC.
#privateTR
problems here.
The domain registration issue with our tracker domain flacsfor.me was a bit unfortunate timing here, but essentially the renewal was supposed to be automatic using our account funds, but I think auto-renewal may have been disrupted somehow and can't really trace the issue down to any one particular fault. Our DNS TTL is set to 300 seconds, meaning that the tracker IPs can be changed quite frequently without anyone having to flush their DNS cache. Unfortunately, when the domain expired, our provider handed out their own DNS records, which had a much higher TTL and resulted in issues that lingered throughout the rest of the day. We do have calendar reminders for every renewal across our entire infrastructure, but we didn't anticipate issues with our domain renewals since they are usually handled without intervention.
Lastly, the upload error was completely unpredictable and very hard to trace because despite seeing a "5xx" error code while trying to upload, we didn't see anything in our error log files. We were, however, able to narrow down the problem to the proxy servers (frontends) not having enough disk space to handle the file upload buffers that are proxied down to the backend. We increased our logical volume space on both frontends and ensured that nginx had a temporary directory with ample free disk space, since we typically run these servers as light as possible and use a lot of defaults.
Thank you for reading through and I hope everyone has a great new year! As always, if you experience any site issues, feel free to use our IRC (#red-help) or help forum, or you can always open a staff PM if it's more sensitive.
Cheers,
***
#privateTR
The domain registration issue with our tracker domain flacsfor.me was a bit unfortunate timing here, but essentially the renewal was supposed to be automatic using our account funds, but I think auto-renewal may have been disrupted somehow and can't really trace the issue down to any one particular fault. Our DNS TTL is set to 300 seconds, meaning that the tracker IPs can be changed quite frequently without anyone having to flush their DNS cache. Unfortunately, when the domain expired, our provider handed out their own DNS records, which had a much higher TTL and resulted in issues that lingered throughout the rest of the day. We do have calendar reminders for every renewal across our entire infrastructure, but we didn't anticipate issues with our domain renewals since they are usually handled without intervention.
Lastly, the upload error was completely unpredictable and very hard to trace because despite seeing a "5xx" error code while trying to upload, we didn't see anything in our error log files. We were, however, able to narrow down the problem to the proxy servers (frontends) not having enough disk space to handle the file upload buffers that are proxied down to the backend. We increased our logical volume space on both frontends and ensured that nginx had a temporary directory with ample free disk space, since we typically run these servers as light as possible and use a lot of defaults.
Thank you for reading through and I hope everyone has a great new year! As always, if you experience any site issues, feel free to use our IRC (#red-help) or help forum, or you can always open a staff PM if it's more sensitive.
Cheers,
***
#privateTR