wolstech

Another interesting thing, PHP is still able to send mail...I received a daily report email from one of my programs without an issue overnight (it's sent with mail() so that's at least working...)

Done. Note that when your current cert expires, AutoSSL will not provide coverage for the mail domain because it won't validate (this is normal since mail usually redirects to cPanel anyway). It might also not renew on its own the first time around because the current cert does cover mail and the replacement wouldn't. If that happens, let me know and I can run it manually for you. 9:54:54 AM This system has AutoSSL set to use “cPanel (powered by Comodo)”. 9:54:54 AM Checking websites for “deny” … 9:54:56 AM The website “vonitsanet.denied.gr”, owned by “deny”, has a valid SSL certificate, but additional SSL coverage may be possible for the domain “www.vonitsanet.denied.gr”. The system will attempt to replace this certificate with one that includes this additional domain. 9:55:00 AM WARN The domain “mail.vonitsanet.gr” failed domain control validation: “mail.vonitsanet.gr” does not resolve to any IPv4 addresses on the internet. 9:55:00 AM WARN The current SSL certificate for “vonitsanet.denied.gr” secures the domain “mail.vonitsanet.gr”. However, this domain failed local domain control validation. In order to maintain SSL domain coverage for this domain, the system will not attempt to replace the current certificate. 9:55:00 AM The system has completed the AutoSSL check for “deny”.

Fixed. /var/tmp was full because some clown filled it trying to update drupal. I cleaned out the update temp files and it freed 30%. There's a lot of other stuff in there that looks like it could go too, but some of it looks like cPanel stuff so I'll leave that for Krydos. The /var/tmp was to blame for PHP acting up, but I still have no idea why exim won't start. I'm guessing it's the swap file, but there's tons of regular RAM free.

PHP 5.6 and newer are currently unavailable on Tommy due to technical issues with the server. Also, mail services are currently down on Tommy regardless of software version. PHP 5.4 and 5.5 are working properly. PHP 7.2: https://krydos.heliohost.org/72/phpinfo.php (broken, 500 error) PHP 7.1: https://krydos.heliohost.org/71/phpinfo.php (broken, 500 error) PHP 7.0: https://krydos.heliohost.org/70/phpinfo.php (broken, 500 error) PHP 5.6: https://krydos.heliohost.org/56/phpinfo.php (broken, 500 error) PHP 5.5: https://krydos.heliohost.org/55/phpinfo.php (working) PHP 5.4: https://krydos.heliohost.org/54/phpinfo.php (working)

There's 2 solutions for this. Change the name servers entire for a few minutes to add the domain as an addon, then change them back after adding it and create an A record. You might need to use a different registrar if your current one can't do this for some reason. Note your domain will stop working for the duration of the change and setup. Or, use domain.com as your main domain and set an A record pointed to us instead. Note that in either configuration, the DNS, mail, and subdomains functionality won't work unless you create all the required dns records manually every time you do something. It might be easier to transfer the domain and use us for the DNS, and add the google records manually instead.

I saw you tried to sign up again under your new username. Unfortunately the server is currently experiencing issues related to being out of memory, so the creation failed. We'll send you an invite for an account as soon as its fixed so you can sign up. The issue we're waiting on to get you set up again is this one: https://www.helionet.org/index/topic/35377-mail-issuetommy-swap-full/

Unblocked. It should be effective within 10 minutes.

That domain is working properly for me. Is it still not working for you? (Ricky has been experiencing severe load and a lot of downtime today, so you probably tried in the middle of such an event). http://heliohost.grd.net.pl/monitor/

It depends. If it was a case where something like WP got malware, we make them remove the infected software and reinstall it to clean it up. If it was intentional spam (usually more of a Johnny issue...), yeah, banned.

Waiting for “exim” to start ……Job for exim.service failed because a configured resource limit was exceeded. See "systemctl status exim.service" and "journalctl -xe" for details. …Waiting for exim to shutdown ... not running. Job for exim.service failed because a configured resource limit was exceeded. See "systemctl status exim.service" and "journalctl -xe" for details. …Job for exim.service failed because a configured resource limit was exceeded. See "systemctl status exim.service" and "journalctl -xe" for details. …Job for exim.service failed because a configured resource limit was exceeded. See "systemctl status exim.service" and "journalctl -xe" for details. …Job for exim.service failed because a configured resource limit was exceeded. See "systemctl status exim.service" and "journalctl -xe" for details. …failed. Cpanel::Exception::Services::StartError Service Error (XID ykg3fs) The “exim” service failed to start. Startup Log Mar 19 20:38:43 tommy.heliohost.org systemd[1]: Failed to fork: Cannot allocate memory Mar 19 20:38:43 tommy.heliohost.org systemd[1]: exim.service failed to run 'start' task: Cannot allocate memory Mar 19 20:38:43 tommy.heliohost.org systemd[1]: Failed to start Exim is a Mail Transport Agent, which is the program that moves mail from one machine to another.. Mar 19 20:38:43 tommy.heliohost.org systemd[1]: exim.service failed. Mar 19 20:38:43 tommy.heliohost.org systemd[1]: Starting Exim is a Mail Transport Agent, which is the program that moves mail from one machine to another.... Mar 19 20:38:59 tommy.heliohost.org systemd[1]: Failed to fork: Cannot allocate memory Mar 19 20:38:59 tommy.heliohost.org systemd[1]: exim.service failed to run 'start' task: Cannot allocate memory Mar 19 20:38:59 tommy.heliohost.org systemd[1]: Failed to start Exim is a Mail Transport Agent, which is the program that moves mail from one machine to another.. Mar 19 20:38:59 tommy.heliohost.org systemd[1]: exim.service failed. Mar 19 20:38:59 tommy.heliohost.org systemd[1]: Starting Exim is a Mail Transport Agent, which is the program that moves mail from one machine to another.... exim has failed. Contact your system administrator if the service does not automagically recover. Swap's full. Odd it can't allocate memory though, there's only 70% usage on the actual RAM...

There is not. It's intentionally disabled due to a history of abuse (botnets and pirated/nulled software). Your only option would be to buy a VPS, where you can install anything you want: https://www.heliohost.org/vps/

It's probably a few things actually. Time of day is a big factor (the worst time for our servers is around 8PM EDT because we accept our day's worth of new account registrations during that time). I also banned a few accounts on johnny this morning that were probably contributing to load (they were running a spambot, those are notorious for causing load, ignoring the fact that sending spam is itself abuse).

This phishing content has already been removed.

Suspended.

In its heyday it was, but we have very old hardware by today's standards because of changing economics making it impractical to replace. Tommy's track record over the past week was about 99.94%, but that doesn't account for the several hour outage yesterday because one of its partitions is full. Ricky has actually been up 99.41% over the past week, but it's slow. Johnny has a 95% uptime due to overloading and abuse. If you're curious about how we actually perform, all of our server performance and uptime history back to 2010 is available here: http://heliohost.grd.net.pl/monitor/ (This is an independent monitoring service that is NOT not owned or operated by HelioHost, as a result, it provides an independent view of our performance as seen from an outside organization).

Byron already sent you a new invite, but for your information, based on the time I'd suspect your first one failed because the server was down due to the disk being full at that time. That issue has since been fixed.

675MB free as of this writing...http://heliohost.grd.net.pl/disk-space/

Unblocked.

This should be resolved for the time being. For the interested, the issue is the /var line under Tommy here: http://heliohost.grd.net.pl/disk-space/ When it hits 0, the server goes down because a lot of stuff doesn't like running out of space (PHP especially, can't save session data).

Done. Your account is now on Tommy. Thank you for the donation. If you see a queued page or 404 error, please clear your browser cache and flush your DNS resolver cache.

The username is actually naser01. Unarchiving...

Moving...

From what I can tell, your WordPress installation is either misconfigured, broken, or too bloated with extensions. The domain and server are working properly as evidenced by the phpinfo file I created: http://shgmta.ml/test.php For what it's worth, we highly recommend not using WP because it's poorly coded and laughably insecure. I'll let Krydos take a look at this and see what he thinks.

The server was down until about an hour ago due to a disk space issue. Try logging in now. If it still won't work, try logging in here: https://tommy.heliohost.org:2083/ using your username instead.

500 errors are not generally caused by these settings. The most common problem is file permissions needing to be changed. Start by verifying that all of your files are set to 644, and rename your .htaccess file to something else so it's ignored. Code errors can also cause this, but only if errors are turned off.