Your free hosting server ip address is nulled for 24 hours due to DDOS, if you need your site online today you can upgrade to a premium plan.
Please let us know if there is anything we can do.
Other Information
Sorry, but I have so many questions:
Actually, my website is a small artistic site where I sell my art. It only gets a few clicks per day, so I don’t understand why I would be targeted by a cyberattack. Why would that happen?
I don’t want to upgrade to a paid plan, but my question is: if I don’t upgrade, will I still be able to keep my website?
After 24 hours, will the website return to normal on its own?
Is my website lost forever?
Am I at risk of being banned permanently from Infinityfree because of this attack?
As you can see in the System Issues topic, the IP address your website was on was down recently due to an attack. And apparently, the server admins believe that your website may have been the target of that attack.
Given that this attack caused tens of thousands of websites to be down for an extended period of time, I hope you can understand that we want to take action to prevent that from happening again.
And one way we do that is to identify the websites that were targeted and take them down. Because a website that was targeted once is likely to be a target again.
This is understandably very frustrating if your website was targeted, because you didn’t want this to happen and probably didn’t cause it yourself. But please understand that we have to make decisions that benefit the platform as a whole, even if it comes at the expense of a few individual website owners.
I have just got cyber attack too, then my account has been suppended and I’ve config my script again and use IP Block. It’s quite good. Try it and good luck !
Yes, extractly, I filter request once @ cloudflare, then I block evil IP in .htaccess, finally I tweak my PHP script to block IPv6. Then you see, 48 hours passed, everything work well.
Please note that our servers don’t support IPv6, but IPv6 support at Cloudflare is mandatory. By blocking all IPv6 traffic on your website, you will block all visitors who can use IPv6.
Also, in my opinion, blocking individual IPs is a fools errand, because attackers can easily get new IPs. A dynamic solution, like Cloudflare’s Under Attack mode is far more effective and easier to use too.
Yes, Admin, due to we can’t filter IPv6 via .htaccess then I use cloudflare to filter danger IPv6 first, just a simple iptables rule support in cloudflare, then I use blackhole (Blackhole Pro | Plugin Planet) to tweak the PHP to filter it again in hosting. As you see in .htaccess, with IPv4 I don’t block IP per IP, I block all list evil IP Range. Now almost fine, everything work well, IPv4 and IPv6 can access my site but botnet is not.
I understand your decision, but honestly, I’ve invested a lot of time and money into my website, and the risk of losing it to someone else is devastating. Since I’m a newbie, could you provide a step-by-step guide on what to do now and after this situation? I’m really not sure where to start or what steps to take. Thanks!
If there was a single process that will stop every type of DDoS attack for any website, don’t you think we would have applied that by default already?
I can’t give you step-by-step instructions because I can’t even tell you which direction to go in.
All I know is that server admins suspended your website because they believe it to be the target of a DDoS attack. What kind of attack was launched at your website, or whether your website was the target of the attack at all, I can’t say.
Maybe it can be stopped through Cloudflare, maybe it can’t, maybe the attackers didn’t go through Cloudflare and attacked the hosting server directly, or maybe your website was flagged as a false positive and there was no attack on your site to begin with.
So…my opinion is…you need to change DNS to cloudflare and carefully read the logs first then we can check the logs to find solutions to defence.
In fact there is no perfect solution for DDoS, however we can find defensive solutions for each type of attack through the logs.
(Attention: Our hosting current have no support logs manage module, then you should make a logging function by yourself).
Easy PHP Blackhole Trap with WHOIS Lookup for Bad Bots | Perishable Press <— Sample for tweak PHP code defense bad bot with live demo.
Simple to understand this skill is trap the bot. You know, human can not see the hidden link but bot is can, so we place a hidden link on website and check the logs, IP access to hidden link 100% is bot, not human then we lock that IP range via .htaccess or any firewall then done !
Good luck !
Which will prevent the attacks from hitting your PHP code, but they will still be counted against your hits limit, and can still cause damage.
And it can help against some attacks that involve bad crawlers, but won’t do anything against e.g. attacks directed at the WordPress login page or just DDoS attacks that just send a ton of traffic to your site to take it down. Because a DDoS attacker doesn’t care about the page they hit, as long as it causes damage.
I agree with you, as I talk before. There is no comprehensive solution, but we have solutions for each specific case. For example in case attacker flood heavy request data to login form of Wordpress, mysql with be damaged then to protect mysql system our solutions should be use captcha embed with WordPress login form or something like that.
You know, each types of attacks have different defense solutions. The important thing is we need to know clearly how hackers attack and that is the importance of the logging system which is still not support in current InfinityFree web hosting services.
To Helmort:
As my tracert result, your website get a tons of connect in this time due to AI request to grab your art and use it to train data. You should checkout this link to find solutions to protect your art. ( How to keep your art out of AI generators - The Verge )
This is some artist they are a victim of AI Generator and you see they protest to against AI crawler:
Did you read the first post in the topic? It clearly says that the problem is a DDoS attack. None of your proposed solution will do anything against DDoS attacks, which is largely because DDoS attacks are very hard to stop in general, and cannot be stopped effectively with website level security measures.
It’s probably the best thing you can do right now. As for whether it’s enough, only time will tell.
