wolstech

4:25:18 PM This system has AutoSSL set to use “cPanel (powered by Comodo)”. 4:25:18 PM Checking websites for “icnsofto” … 4:25:22 PM The website “staging.icnsoft.org”, owned by “icnsofto”, has a faulty SSL certificate (OPENSSL_VERIFY:0:18:DEPTH_ZERO_SELF_SIGNED_CERT). AutoSSL will attempt to replace this certificate. 4:25:30 PM WARN The domain “staging.icnsoft.org” failed domain control validation: The system queried for a temporary file at “<a href="http://staging.icnsoft.org/.well-known/pki-validation/9E51985B8B1E954F1E5A79B734C6ADEF.txt">http://staging.icnsoft.org/.well-known/pki-validation/9E51985B8B1E954F1E5A79B734C6ADEF.txt</a>”, but the web server responded with the following error: 404 (Not Found). A <abbr title="Domain Name System">DNS</abbr> or web server misconfiguration may exist. 4:25:30 PM WARN The domain “www.staging.icnsoft.org” failed domain control validation: The system queried for a temporary file at “<a href="http://www.staging.icnsoft.org/.well-known/pki-validation/E59B2E3DF59EB4C0C35BBF77BA85315C.txt">http://www.staging.icnsoft.org/.well-known/pki-validation/E59B2E3DF59EB4C0C35BBF77BA85315C.txt</a>”, but the web server responded with the following error: 404 (Not Found). A <abbr title="Domain Name System">DNS</abbr> or web server misconfiguration may exist. 4:25:30 PM The system has completed the AutoSSL check for “icnsofto”. That error is usually because you have some sort of forced redirect. AutoSSL does not support these forced redirects and requires a plain HTTP connection to the .well-known folder to verify the domain. Remove the forced SSL redirect or add an exception for the URLs given above and let me know so I can run it again.

[65.19.143.6] Your account does not appear to be configured to use the dedicated IP for mail for some reason. Escalating to have this fixed.

That account is on Johnny, which has crashed. Please see the most recent posts over in https://www.helionet.org/index/forum/1-news/ for more information.

Johnny has died. See the recent posts in https://www.helionet.org/index/forum/1-news/ for more information.

That's Johnny...that server died a week ago. See the recent posts over in https://www.helionet.org/index/forum/1-news/ for details. Long story short, it has to be rebuilt and backups of your data are going to be made available for you to download in the coming days. In the meantime, you can sign up on Ricky or Tommy at midnight UTC if you wish. (Both servers have a much better reliability track record anyway and are also much faster.)

It will be back. Right now we are more concerned with making sure nobody loses their data. Once the backups are ready, we'll be emptying Johnny out and rebuilding him. Our Ricky and Tommy servers are completely unaffected by this issue as well. If you wish, you can sign up on one of those servers for free when we offer free accounts at midnight UTC each day.

It's archived, but I can't unarchive it because it belongs on Johnny which has died. If you want to donate, I can move it to tommy and restore it there though. Otherwise, just wait for the announcement when backups are available so you can download the archive.

It's not blocked...what's not working for you?

Unblocked. It might take up to 10 minutes to take effect.

Done.

Percentages are based on uptime over the course of one week.

Yeah, we have to for that server. Cpanel doesn't offer any way to install old versions. Its not that the customization we use is incompatible, so much as it is that we have to spend time re-modifying everything each time its installed/updated.

I've seen servers at 0 before (the last time Johnny died...)

If we rebuild the server, they'll be deleted as part of the server rebuild. You'll need to sign up again, and wait in line again, though the wait will likely be rather short if you sign up as soon as it becomes available again. Tommy only has a one day java wait though, so if you move to that server, you can get back to work faster. Also, you can deploy your own WARs on tommy, no need to ask us to do it.

Because we heavily modified cpanel to do what we did here. Cpanel is only meant to handle about 400 accounts on a server. We cram in thousands of them. Cpanel's own support has recognized us as one of (if not *the*) most extreme uses their product has seen... Updating it would break all of our custom code, so it simply never gets upgraded unless there is a server rebuild or a very compelling reason to upgrade.

Escalating.

They won't expire for inactivity while the server is down. However, if we do rebuild the server, the accounts will be deleted and everyone will need to sign up again and restore a backup.

Reason: Causing high server load. 218% more cpu than #2. You're suspended for severe high server load. Let's see if Krydos can find out wha caused it. We'd prefer you know how to fix it before we unsuspend you so you don't cause this sort of load again.

Well, it is suspended for high load, but it doesn't really matter at this point since the server you're on died. https://www.helionet.org/index/topic/32759-johnny-backups/ You won't be able to make a backup yourself at this point. You'll likely need to until we make and offer them instead. In the meantime, feel free to sign up on Ricky or Tommy when registrations are open if you wish.

No problem. Let us know if you need anything else

Just watch in the News forum. When they become available, they'll be announced. All I know is that the archived accounts were backed up yesterday, not sure whether /home/ was already done or not.

Whitelisting them means accepting the abuse instead, which would lead to more compromised accounts. The whole reason the IP blocks exist is to prevent someone from easily sitting there and guessing passwords. You'd need a large botnet to overcome it (so you have all the public IPs of the bots at your disposal, with each bot having 5 tries). If you have a botnet, you're probably DDoSing instead of breaking into servers anyway. If we whitelisted a ton of IPs that anyone can easily use, we've defeated the purpose of our own protection. Besides, contrary to what many think, CF is not just for security...they also offer platforms for running applications like Amazon and Google do.

They unblock themselves over time by falling off the bottom of the block list (there's a max number of blocks that can exist at one time), but that can take a week or two typically. Considering Tommy is stable, I'd personally recommend just not using CF if this is a concern.

I think we did have it on one of our servers at one point in the past, but it tends to cause a lot of load and will almost certainly get you suspended for high load because it uses a ton of resources. I wouldn't recommend it, but if you really want to, I can ask whether this can be installed.

The usual cause of this is cybercriminals running bots through CF to break into servers. It's not something you did, but rather the fact that your connections to our server appear as a CloudFlare IP. which you share with thousands of other people (some of which are abusing it).