wolstech

You already have another active account. Users are only allowed one account at a time, so in order to unarchive this, you'll need to delete postfre2 first.

These aren't exact instructions, but should give you an idea: Remove the line from the hosts file, this is not supported on our service.Change the main domain to something that ends in .heliohost.org, so strokesupport.heliohost.org would work.Move the contents of the stroke folder directly into public_html.Wait 2 hours.Clear browser cache.Modify the appropriate mysql values to configure WP to use the domain strokesupport.heliohost.org (google will explain this process).Access your site at (if you use the above example): http://strokesupport.heliohost.org/Perform any changes you wish to make to the site.When you're ready to move the domain: Modify the appropriate mysql values to configure WP to use the domain strokesupport.inChange main domain to strokesupport.inWait 2 hours.Set name servers to ns1.heliohost.org and ns2.heliohost.orgWait for DNS propagationClear browser and DNS cache. As above though, we highly recommend not using WP. If you're interested in just tossing out the site and building a new one: Remove the line from the hosts file, this is not supported on our service.Change the main domain to something that ends in .heliohost.org, so strokesupport.heliohost.org would work.Delete the stroke folder.Wait 2 hours.Access your site at (if you use the above example): http://strokesupport.heliohost.org/Build your new site in public_html or create a folder for it if desired (keep in mind if you use a folder, you'll need to set up a redirect in public_html or add the folder name to the end of the URL (e.g. strokesupport.heliohost.org/stroke/ ) every time.

Krydos has to do this for you...

Unarchived.

To get this working in the meantime for testing, go here and change your main domain to the domain you're putting in your host file: http://heliohost.org/classic/support/scripts/domain After that, wait 2 hours, then clear your browser cache and try again. Also, for what it's worth, WordPress is the one program we really love to hate on around here, and will always recommend that people not use. It's poorly written and very insecure by design. As a result, it's a leading cause of performance issues, load suspensions, and even accidental bans (usually when it gets hacked...which is more often than we'd like...with the result generally being a phishing site getting set up). You'll probably need to be on Tommy for decent performance.

Using the IP address of the server with the host file is not supported. You might be able to get limited functionality by setting your domain as the account's main domain, waiting 2 hours, then try using it that way, but most functionality will not work in this configuration. For the service to perform properly, you need to actually use a real domain and point it to our name servers (ns1.heliohost.org and ns2.heliohost.org) at the registrar.

There are two ways an account gets fully deleted: someone deleted it, or it came due for archive and was suspended for a reason other than inactivity (suspended accounts won't archive, they just delete, this is done so we don't archive phishing and other abusive accounts). Either way, that account does not exist, so you'll need to sign up again.

You'd have to toss it out and start over. That's the one downside. Most people we make this recommendation to are newcomers, so they haven't built anything yet.

The best solution to WordPress problems is to not use WordPress. Just about any other CMS is better. Luigi explained why above.

It has to be a code issue because nobody else is reporting this issue. My site as well as 99% of others on here all use PHP sessions and have no issues with them. Why do you think the sessions aren't working?

For development/testing, most people would use something like xampp on their computer: https://www.apachefriends.org/

For what it's worth, the email was changed to a random qq.com address, so someone in China probably did this. If you need your domains removed from the stolen account, please let me know.

Unsuspended. Give it a few minutes and it should work. I also pushed the login date on the lily account our by two years so it won't go inactive again for a while. It appears the login date sync for your account isn't working for some reason, so I'll need to troubleshoot that. It's supposed to stay in sync with the tommy account...

Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. If you still see the suspended page, please clear your cache. If you need help figuring out why your site is causing such high load let us know and we can try to help. If the high load is simply because your site is getting a lot of traffic, you might want to consider purchasing a VPS instead. https://www.heliohost.org/vps/ VPS hosting gives you an entire virtual server to yourself, including no load limits, a dedicated IP address, and full root access.

Krydos can cancel this for you.

@Sohamb03: This would sort of work if he used it as his main domain and put in an A record to the shared IP. The downside to this configuration is that a substantial number of things in cPanel would be broken in that configuration (namely all DNS options, email, webdisk, and a few others).

We intentionally don’t do this by default for several reasons. First, users on Johnny don’t even get SSL certificates so it’s not going to work without extra efforts there. Two, SSL causes tons of load, by making people set it up if they want it, we reduce load and thus can cram more users into the hardware we have because most people don’t bother. Being a nonprofit that hasn’t been in the black in years, we have to get what we can out of the hardware we can afford to buy. Third, we actually get quite a few of the opposite complaint. Many of us run old code and other stuff that either doesn’t need or doesn’t support SSL. Fourth, cpanel’s automatic SSL feature doesn’t work if HTTPS is forced through some methods. It requires the .well-known folder be available via plain HTTP in order for certificates to validate, and .htaccess with an exception for that folder is the easiest way to accomplish forced SSL with an exclusion.

Tommy’s very quick about it, 24 to 48 hours is for Johnny. In fact the new domain is already working. Auto SSL might take a few hours for that to run but it won’t fail for the domain being too long now, so it should get you a certificate.

Since you’re on Tommy it should take affect within an hour or two.

It's one account per person. You and your friend can each have one account. We do require ID to prove there's two users though. Each user needs to scan/photo a valid ID and send it to us along with the username of the account that is theirs. Please either PM the pictures or email them to me at wolstech@heliohost.org. Do not post it publicly. Once verified you can delete the pictures. A government ID is preferred, however since this appears to be for educational use, we can accept a school ID as well. Please keep in mind that it may take a little while for me to get back to you once you send them. The third account will need to be deleted.

You have 3 accounts, cvsuccjc, cvsuccj (both on Johnny) and cle2019 (Tommy). All have ridiculously long and similar domains, all are from the same IP address, and all appear to be for the same purpose. Since there's an AutoSSL help topic for cle2019 on Tommy (and Tommy is far superior to Johnny anyway), please delete the two Johnny accounts. Tommy PHP 7.1 already has mbstring installed.

Yes. Make it something short like thesis2019.heliohost.org and it would work. You can change it here: http://heliohost.org/classic/support/scripts/domain

The officially supported configuration is to not use cloudflare at all. You mention being on tommy, so autossl could handle the certs for you, however autossl and CF are incompatible with each other. Also, keep in mind that the flexible option on CF is a terrible idea that shouldn't even exist from a security standpoint. It leaves the CF to heliohost part of the connection unencrypted despite telling the user they have a secure connection (which they do...only up to CF).

You don't qualify for a certificate because your domain name is too long. 10:12:48 AM WARN (XID yd5ccu) The value “cvsu-ccj-cle-reviewer-mobile-application-admin-thesis2019.heliohost.org” for “commonName” is too long by 7 bytes. The maximum allowed length is 64 bytes. at /usr/local/cpanel/Cpanel/SSL/Auto/Provider/cPanel.pm line 206. WARN AutoSSL cannot secure any of “cvsu-ccj-cle-reviewer-mobile-application-admin-thesis2019.heliohost.org”’s domains. at /usr/local/cpanel/Cpanel/SSL/Auto/Provider/cPanel.pm line 210.

That's exactly what an addon domain is...a subdomain with a domain parked on top. When you add an addon domain, the system just creates a subdomain and then immediately parks the domain specified on top.