wolstech

I just sent another one, this time to the email on your forum account. See if that one works.

The /tmp folder was full again. I freed the space about 20 minutes ago. Original complaint thread: https://www.helionet.org/index/topic/39342-solved-internal-server-error/ The guy who did it: https://www.helionet.org/index/topic/39350-suspended-tommyshh/?view=getnewpost My sites seem to be running at decent speed at the moment, and at least one user in that first link reported his is working again as well. Are others still seeing this issue?

Please check your email for an invite to create a new account. Also, two things: Your domain is broken because of CloudFlare. Remove that to get your domain working.WordPress doesn't go over well here. Find another CMS for best results. WP is the #1 reason of just about every issue we see outside of intentional abuse. High load, hacked account, 500 errors, even accidental phishing bans if a hacker sets up phishing on a hacked WP install.

The guy who caused this just posted over in S&Q about his account...lets see if he can fix the issues with his software.

You're suspended for filling /tmp. Long story short, whatever software you are using is very broken. It's generating extremely large temp files with image magick and is not cleaning them up. When /tmp fills, MySQL stops working and pretty much every site on the server goes down. Whatever is on your account caused almost 45 minutes of downtime for 2827 websites. What do you plan to do to fix this, and can you guarantee this will not happen again?

This should be fixed. Are you still experiencing a problem?

As it turns out, a user with badly written software filled /tmp with image magick temp files. That user has been suspended and the temp files have been removed. MySQL is now working properly and applications should produce significantly fewer 500 errors.

Weird...Joomla is usually what we recommend as a replacement for WP. I've been seeing tons of complains about 500 errors lately on Tommy too, even though load doesn't look bad (http://heliohost.grd.net.pl/monitor/). I'll have Krydos take a look.

Agreed on WP, especially for Ricky users. The easiest fix for Wordpress...is to not use Wordpress. It's well known to be very problematic here, often causing all sorts of weird behaviors and results, ranging from 500 errors to load suspensions, to even accidental phishing bans if it gets hacked.

The midnight UTC does suck for some people. Back when I joined, it was midnight pacific...which made it 3AM for me. Yes I had to get up in the middle of the night to get the account... Luigi's method is the only way to get an account without getting up in the middle of the night for it. You can donate and the thank you email includes a link to create a tommy account without waiting.

The certificate for this domain (and another user as well...) is stuck for some reason. It's showing as pending in the queue now as of 11:14 EDT on April 18, but it still hasn't issued after 3 days. Krydos needs to fix it.

I'm not finding this account anywhere. I'll have Krydos take a look.

This account does not exist and has no record of ever existing from the looks of it. I don't see anything with that username, and nothing matching the email address on your forum account. Do you know what the domain was on your website?

Totally missed that. I don't believe we support old C scripts, but could be wrong. Most users are running Python scripts these days. I'll have Krydos answer this one since I'm not sure.

What language is the script in? Also, make sure your files use Unix line endings. If they have windows line endings, they won't work. You can use something like notepad++ to convert them if needed.

PM me the cert and I can install it manually. I need a .PFX file that includes the private key, as well as the password for the PFX file. Alternately, I can just add you to the shared server cert on the server if you prefer instead. That'll save you the hassle of sending me new certs every 3 months.

Nope, because you're physically located in the country of Iran from what the system shows. We are not allowed to do business with any person residing in or having an affiliation with Iran. This isn't us unfortunately, it's our government. We are located in the USA, which has made it illegal to do business with Iran. As a result, it is illegal for us to serve you. If our government could get along with yours, we would love to serve you, but until our laws change, that cannot happen for legal reasons. All US-based web hosts have the same restriction too, so it's not just us. You'll need to find a non-US-based web host.

That’s an Iranian domain... Due to federal regulations, HelioHost is unable to provide services to users in the country of Iran. Please back up your data and delete your account. If not deleted within 24 hours, the account will be permanently suspended.

Only our root admin Krydos can fix this. It may take a day or so before this gets changed for you.

What version of PHP are you using also?

That's not really a good idea here considering you only have 1GB of storage...you'll run out of space extremely quickly. You can buy 1GB extra for $5, but you can't get any more than 2GB maximum. You'd have to get a VPS instead. Nonetheless, how big is "large size"? I wouldn't recommend anything larger than 64MB (I know we've raised it to that on other servers or versions of PHP).

The server is too slow for the validation to work...it's timing out while trying to get the validation file. I think this one is going to be a matter of waiting for load to come down...Ricky is running a load of 42.88 at the moment. I'd suggest you just set your site up without SSL for now and see if it gets a cert when the load drops. Log for the AutoSSL run for “byeyou”: Saturday, April 18, 2020 11:20:47 AM GMT-0400 (cPanel (powered by Comodo)) 11:20:47 AM This system has AutoSSL set to use “cPanel (powered by Comodo)”. 11:20:47 AM Checking websites for “byeyou” … 11:20:52 AM The website “contoh1.example.heliohost.org”, owned by “byeyou”, has no SSL certificate. AutoSSL will attempt to obtain a new certificate and install it. 11:21:06 AM WARN The domain “contoh1.biz.st” failed domain control validation: The system failed to fetch the <abbr title="Domain Control Validation">DCV</abbr> file at “<a href="http://contoh1.biz.st/.well-known/pki-validation/3965DB3DC595E98028603A6E9073D259.txt">http://contoh1.biz.st/.well-known/pki-validation/3965DB3DC595E98028603A6E9073D259.txt</a>” because of an error: The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> “GET” request to “http://contoh1.biz.st/.well-known/pki-validation/3965DB3DC595E98028603A6E9073D259.txt” because of an error: Timed out while waiting for socket to become ready for reading . 11:21:19 AM WARN The domain “www.contoh1.biz.st” failed domain control validation: The system failed to fetch the <abbr title="Domain Control Validation">DCV</abbr> file at “<a href="http://www.contoh1.biz.st/.well-known/pki-validation/B3396AC8C4E850918ED232D3E6DEF873.txt">http://www.contoh1.biz.st/.well-known/pki-validation/B3396AC8C4E850918ED232D3E6DEF873.txt</a>” because of an error: The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> “GET” request to “http://www.contoh1.biz.st/.well-known/pki-validation/B3396AC8C4E850918ED232D3E6DEF873.txt” because of an error: Timed out while waiting for socket to become ready for reading . 11:21:29 AM WARN The domain “mail.contoh1.biz.st” failed domain control validation: The system failed to fetch the <abbr title="Domain Control Validation">DCV</abbr> file at “<a href="http://mail.contoh1.biz.st/.well-known/pki-validation/690E0310CA31425F0D99A4B529D8166C.txt">http://mail.contoh1.biz.st/.well-known/pki-validation/690E0310CA31425F0D99A4B529D8166C.txt</a>” because of an error: The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> “GET” request to “http://mail.contoh1.biz.st/.well-known/pki-validation/690E0310CA31425F0D99A4B529D8166C.txt” because of an error: Could not connect to 'mail.contoh1.biz.st:80': Connection timed out . 11:21:40 AM WARN The domain “cpanel.contoh1.biz.st” failed domain control validation: The system failed to fetch the <abbr title="Domain Control Validation">DCV</abbr> file at “<a href="http://cpanel.contoh1.biz.st/.well-known/pki-validation/134C17EC80BAE055F1E1EE32340318F6.txt">http://cpanel.contoh1.biz.st/.well-known/pki-validation/134C17EC80BAE055F1E1EE32340318F6.txt</a>” because of an error: The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> “GET” request to “http://cpanel.contoh1.biz.st/.well-known/pki-validation/134C17EC80BAE055F1E1EE32340318F6.txt” because of an error: Timed out while waiting for socket to become ready for reading . 11:21:51 AM WARN The domain “webdisk.contoh1.biz.st” failed domain control validation: The system failed to fetch the <abbr title="Domain Control Validation">DCV</abbr> file at “<a href="http://webdisk.contoh1.biz.st/.well-known/pki-validation/4B0740AF44273833D706225E5CC75F38.txt">http://webdisk.contoh1.biz.st/.well-known/pki-validation/4B0740AF44273833D706225E5CC75F38.txt</a>” because of an error: The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> “GET” request to “http://webdisk.contoh1.biz.st/.well-known/pki-validation/4B0740AF44273833D706225E5CC75F38.txt” because of an error: Timed out while waiting for socket to become ready for reading .

I run into this error at work. It's not us, it's caused by either the device or the network you're using (work and school networks very often see this problem). Solution is find a different device or internet connection, to use plain FTP on port 21 to connect instead.

That account cannot be unarchived because you already have another account. Users are limited to one account, so unarchiving this would result in both of them immediately ending up suspended.

Krydos has to do this.