Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 12/08/2022 in all areas

  1. You may have noticed some downtime off and on over the last few weeks. Someone on Tommy has been getting targeted by some intermittent DDoS attacks. Due to the nature of the attack it's not possible to tell which of the about 2000 websites on Tommy is being attacked. These attacks have caused short downtimes for Ricky, all of our VPS, our main website, and forum as well, until the DDoS protection kicks in and takes the targeted IP offline. We've been moving accounts around between different IP addresses to help narrow down who is being targeted, and mitigate the downtime for domains that are being attacked. If you use HelioHost's nameservers, ns1.heliohost.org and ns2.heliohost.org, your A record will be automatically updated to follow the move, but if you use Cloudflare or some other external DNS we have no way of updating it for you so your website will show the Plesk default page until you update the IP manually or your account gets moved back to the original IP that it was on. If your website is currently showing the Plesk default page please let us know so we can get it fixed as soon as possible. Our ISP has been working with us to help keep everything online, and we have been moved to a new upgraded network hardware that should help reduce congestion during an attack. We've also purchased a bunch of new ipv4 that we can use to split users on Tommy into groups to help narrow down which group is being attacked. This should all result in better uptime for everyone. If you think you are being targeted, or may be targeted in the future please contact us so we can work with you to help keep your website online, and eliminate the number of innocent accounts that are experiencing downtime because of this. Let us know if you have any questions or comments.
    1 point
  2. 65.19.141.77 port 5432 Remote access to any IP is already allowed.
    1 point
  3. 60 seconds was the same timeout that cPanel had. The reason the limit is there is to help prevent load from getting too high if people run insane php scripts that run forever. This value can be raised for just your one domain if you want, but it might cause your load to get too high which may cause your account to be suspended. Let us know the domain if you'd like to proceed. Eventually you'll have graphs and warning emails to alert you that your load is high. For now I've just been pinging people on Discord or emailing them manually if there's an issue. If they don't respond and don't fix it then we suspend them. The PHP function proc_open is a security vulnerability on shared hosting. It has never been enabled on cPanel either, and it won't ever be enabled on any of our shared hosting servers. If you need this function you have to host it on a VPS.
    1 point
  4. Remote access enabled. Note to self: We might need to set a limit to the number of remote access per account until we implement a way for users to enable remote access themselves. 😂
    1 point
  5. That is a known issue if you change your main domain. I intend to fix it eventually. Does it work now?
    1 point
×
×
  • Create New...