wolstech

You could also install your own copy of PMA on your account and use whatever theme you want

Lets Encrypt isn't even required on Ricky. The server would have gotten a certificate for you after 24 hours if don't have any sort of forced redirects on your domain that would block plain HTTP connections. Anyway, SSL certificates can take several hours to start working on Ricky after installation. If you just installed them, the inactive page is normal until they take effect.

Moving so Krydos can get this installed for you. Correct. Mail sometimes uses 65.19.143.6 by default...

We made the backups for you and they'll be made available at some point in the near future for you to download.

Autossl installed on the domain staging.icnsoft.org but apache hasn't restarted yet. Once apache restarts it should begin working on normal 443. Also, be aware that autossl did not apply to the main icnsoft.org domain because it's been excluded due to cloudflare. Only the staging.icnsoft.org domain received a certificate.

8:58:00 PM This system has AutoSSL set to use “cPanel (powered by Comodo)”. 8:58:00 PM Checking websites for “icnsofto” … 8:58:07 PM WARN AutoSSL will not generate a certificate for the website “icnsoft.org” because every domain for that website has been excluded from AutoSSL. at /usr/local/cpanel/Cpanel/SSL/Auto/Report.pm line 137. 8:58:07 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. 8:58:14 PM The system will attempt to renew SSL certificates for the following websites: 8:58:14 PM staging.icnsoft.org (staging.icnsoft.org www.staging.icnsoft.org) 8:58:19 PM The system has completed the AutoSSL check for “icnsofto”. 8:59:12 PM The queue contains a request for a certificate for “icnsofto”’s website “staging.icnsoft.org”. The system last polled for this certificate at May 8, 2018, 12:58:18 AM UTC. The next poll will be no earlier than May 8, 2018, 1:03:18 AM UTC. 9:04:26 PM Polling for “icnsofto”’s new certificate for “staging.icnsoft.org” (order item ID “376686803”) … 9:04:28 PM The certificate is available. The system will now attempt to install it. 9:05:03 PM SUCCESS The certificate is now installed! The domain staging.icnsoft.org now has a certificate. That certificate will renew on its own when it nears expiration provided you don't block the domain validation again. I'd advise creating a folder to put the WP install in so it doesn't conflict, instead of installing it in the domain's root. Please note that it may take up to 2 hours for it to take effect.

Fewer accounts and much newer hardware on Tommy. We also have somewhat tighter resource controls. Ricky's hardware (Stevie) is actually the oldest in our fleet. Tommy's hardware (Eddie) is I believe either the newest or second newest server based on date of manufacture.

It may or may not. The number of accounts per day on Ricky won't decease overnight since virtually nobody is going to move Ricky->Johnny. Similarly, the number created each day won't decrease since the limit is going to stay the same. Historically though, over time the servers tend to smooth out. New users come and old users go, which means the software being run by them changes over time and thus the load behaves differently.

Modded MC on an rPI? My i7-6700K based server can sometimes have a hard time with modded MC 1.7.10 (yeah, old school). It handles well up to 5-7 players, but beyond that, it's lag city. If I let it have the whole box (instead of half of it in a VM), I'd get ~20 players online at once on a $1200 box. To answer, I don't think so. Game servers are very resource hungry. You'd need a ton of resources to offer such a service, and such resources quickly get expensive. They also don't lend well to advertising or other similar ways of making money, so I can't imagine such a service staying in business without selling something.

To an extent, yes. More accounts = more load. We actually had to reduce the number of accounts per day on Ricky for this reason.

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.