wolstech

Yeah, it's the same for both. Also, the thing about Ricky, is that we don't really promote Ricky. Everybody hates Johnny, and Tommy is promoted for speed and features. Ricky is just...there. He's meant to be a slimmed Tommy though, so we can't just randomly move people or he'd be a second Johnny instead. Someone definitely can donate and ask for a Ricky invite/move if for some reason they wanted that over Tommy (and I can only think of one good reason, Flask on 2.7).

@Luigi: A donation is required for that just like Tommy. We've moved them for free, but only when Johnny's problems made it impossible for us to fix something for a user.

That website works fine for me. WordPress is famous for being really slow and insecure though. Try removing your WordPress extensions, or better yet. using something that's not WordPress.

You can, but don't have to. You cannot reuse the username though, unless an admin renames your forum account first.

It's archived. Escalating to have it restored.

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. <br /><br />If you still see the suspended page, please clear your cache.<br /><br />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 consider trying paid hosting from our partner starting at only a cent for the first month. https://www.heliohost.org/partners/hostgator

Yes. All PHP files must be 644 or they won't work. When you use SFTP, they upload as 664 and need to be changed.

Your files are writable by the group. Change the permissions on them to 644 and it will work.

It's archived. Non-heliohost.org domains will show queued when the account behind them gets archived or deleted. Escalating to have it restored.

The subdomains in question are now working. CloudFlare is the issue. Also, please be advised that after inspecting your domains, I noticed on at least one page, there were links promoting hacking tools (they appear to be ads from wap4dollar). Please remove such advertising within 24 hours. Hacking tools and piracy are not welcome here.

Is the card capable of international transactions or transactions in other currencies (our transactions are all in USD)? Many cards aren't.

That's your mail client adding that as a security measure. Some clients do it, some don't. It usually appears when the rDNS of the sending server does not match the domain in the From header. Since you're on a shared server, the rDNS will resolve back to servername.heliohost.org. If you set the From as something@tommy.heliohost.org you wouldn't see that since the domains would match. Gmail is probably the most widely known one that does this. The idea behind it is to help users in scenarios where someone makes the From address something nefarious such as update-your-account@paypal.com, the via is there to make it easier for users to see it's phishing and did not actually come from PayPal.

Tommy will run software better than anyone, and also has an increased max connection limit compared to the other two servers, so that would be my recommendation as a next step.

That domain is now working. Please clear your cache.

Escalating.

There's a second domain attached to your account called instargam.ml. These are the sorts of domains we usually find instagram bots and phishing sites on.

We have mod_deflate I believe, not mod_gzip.

It's archived. Escalating to have it restored.

I believe yours was due to a fake instagram domain attached to the account. 99% of these domains and their content are phishing sites, or like/follower bots (which are also prohibited). Whether intentional or not, many of these bots, even ones that work, collect and store usernames and passwords for the social media service, effectively rendering them a phishing site by design. They also violate Instagram's Terms of Service and are therefore considered abusive. I'll escalate this so the content can be checked for phishing/bots/other impermissible content and see whether this one can be unsuspended. I can't view the content of a suspended account.

That account is suspended for Phishing. For security reasons, phishing accounts cannot be unsuspended, backed up, or deleted. You will need to create a new account and restore any backup you may have. Please be aware that you will not be able to reuse any domains on your suspended account, and will need to pick a new username. We apologize for any inconvenience this may have caused.

Try creating a CNAME record on CloudFlare's site, name it tube and set its value to atoz.ml. That should fix tube.atoz.ml if missing records are the issue. If that works, repeat replacing the "tube" with your other subdomain. You'll need to do this for any subdomain you create when using CF's DNS service. This process just lets CF know you created it how where the traffic should be directed. If that doesn't help, please change the nameservers to ns1.heliohost.org and ns2.heliohost.org, wait an hour, and your subdomains will probably work. You're still using CF's DNS service even though you're not using their caching service: https://bybyron.net/php/tools/dns_records.php?domain=atoz.ml&rec=NS

How did you configure the DNS on the domain? On Freenom's website, when you register the domain, you need to select "Custom DNS" and specify ns1.heliohost.org and ns2.heliohost.org as the nameservers. Also, what is the .tk domain you picked? I can't check on its configuration if I don't know what it is. The .tk domains definitely do work here, as we have hosted hundreds of them. Most issues with domains are a combination of improper domain DNS settings or failure to add the domain to your account (domains will always be queued if you have not added the domain to your account). We recommend using an Alias (shows same content as main domain) or an Addon domain (different content), though you may wish to change your main domain instead since the one you originally picked (the .org) is not registered.

CloudFlare does not play nicely with our more advanced features, and has been known to cause issues with some regular PHP apps as well. We recommend avoiding CF unless you have a specific reason for needing it (advanced DNS or static content performance are the two most common reasons). In addition, accounts configured with CF will be asked to remove it if you ask for support, so we can be sure that CF is not the cause of the problem.

This support request is being escalated to our root admin.

@Luigi123: Seeing he's on Tommy, he does need to request it, and yes, he must mean ASP.NET since classic ASP has been obsolete for years. If he actually means classic ASP...time to get new software. Escalating.