wolstech

Gmail does not accept email from our servers by default. What domain is the email coming from? It likely needs spf and dkim set up. Also, keep in mind that even with this, the messages will likely end up in the spam folder on gmail. Pretty much all email from our servers is considered spam by gmail, even stuff like our invites and announcements goes to spam for these users. They only start delivering to the inbox on gmail once a user finds them in spam, and clicks "not spam".

This was already resent in the other topic you posted.

That account was actually on the old cpanel Johnny, but the result is the same. It's not suspended, it was deleted. An invite for a replacement johnny account has been sent to you.

Krydos has to do this.

Manually sent. It'll probably be in your spam folder.

Krydos will need to do this since I’m on mobile at the moment…

Krydos had to do this.

This is the 4th account you've created and subsequently deleted this year...considering you usually need it again after a few months, it would probably be better to let it go inactive and you can just renew it when you're ready to come back. Do you still want me to delete it?

Domain changed. Escalating to have the MX's changed. For the domain, please make sure you either set your name servers to ns1.heliohost.org and ns2.heliohost.org, or create A and AAAA records pointed to the IPs shown in Plesk. It may take up to 2 hours to start working.

I merged the forum accounts and then forgot to escalate the rest of this to Krydos.

Escalating to get this enabled.

Changed. Please make sure to configure DNS to point to the IP addresses shown in plesk. The domain can take up to two hours to work.

Krydos can do this for you.

Uncheck the wildcard certificate box and try again. We don't support wildcard certificates at this time.

I'll let Krydos handle the domains due to the recent events... I'll merge the forum accounts shortly.

We’re being hit by ddos attacks (see News section). When that happens we have to get our ISP to mitigate it by null routing the IP, which takes the associated websites offline. Until we can resolve this (or the attacks subside), random outages like this may occur.

They do this automatically when they're not pointed to our servers. In this particular case, I suspect this happened because your account has moved IPs as a result of the recent DDoS attacks (see News section for more information) and the domain is now pointed to an invalid IP address. The new IP address for your account can be found in Plesk.

It was. We keep getting his by a DDoS attacker targeting an as-yet-unknown website on Tommy. When he hits, everything goes offline until our ISP can mitigate it for us. We're blocked by Malwarebytes because we have a history of hosting phishing sites. That's been that way for 2 or 3 years at this point and they're the only company we're aware of that so far refuses to fix it (I sent them an email early last year since I'm a paid user and they simply said it was flagged because of phishing activity and that they do not remove sites by request). I use MBAM on my home PC and had to put *.heliohost.org and helionet.org in the whitelist.

Weird, it doesn't show as being a 2000MB account in the admin tools. I just checked in Plesk and it shows it though. Regardless it's now showing on only 646MB used anyway... Escalating so the space weirdness can be checked and the domain can be changed.

Before we do that, you're over quota and need to either delete something or buy more disk space ($5 for an extra 1000MB, max of 6000MB per user). You're currently using 1200MB on a 1000MB account. If you decide to buy disk space, please send us the money and post the transaction ID of the payment so I can apply the space for you and get your domain moved. If you decide to delete files, please let us know when you've done so and we'll recalculate the space use and get your domain moved.

1. Your site is working for me. The default page and downtime are related to mitigations for repeated DDoS attacks, and should resolve within a few hours on their own when they occur. 2. What files and programs are you referring to? 3. See #2. 4. Krydos can set external MX records for you if you want. If you want to use the mail server on Tommy, you only need the default MX records which point the mail to the same server as your domain. You should have Krydos set up SPF and DKIM if you plan to send email though (please open a new topic for this if you want it).

We cannot troubleshoot this because the domains are currently aimed at Weebly. Keep in mind that accounts are subject to downtime with a default page showing as part of DDoS mitigation while we work to resolve the repeated cyberattacks. Each time these mitigations kick in, accounts may experience outages or default webpages as the mitigations take effect. The site should recover on its own when the mitigations are fully applied, provided you're using our name servers.

It's working for me and has already corrected itself just as before. We were hit again this morning around 12:30PM EDT, mitigations kicked in about an hour later. These default pages are a side effect of the mitigations kicking in and last until Apache restarts and stale DNS caches expire (about 2 hours for most people). As long as the idiot that keeps DDoSing us decides to keep it up, this may happen when his attacks succeed. We're working on determining what is being targeted so we can deal with it more permanently, but each step requires we wait and be attacked again to gather more data. If you need something that won't shows these screens after an attack, you'd need to buy a VPS or move to Johnny (which is not currently a target). It will still see downtime during the initial attack, but once the mitigations stop the traffic, your account would come back more quickly.

I can't find anything wrong with this one. It's not even suspended on my end, and is only using 293MB. Are you still seeing this message?

As above, please pick ONE, not two accounts. Also, you can host more than one site in a single account and can buy extra disk space if that's a concern, so there is never a good reason to need two.