wolstech

We accept Skrill, so that's fine. As for price, our smallest VPS is usually $4/month, but he may be willing to go lower (probably $2 or $3) since you only want 15gb of space (be aware that the operating system is going to use most of it...if it even fits). He might also be able to do 1 CPU to lower costs further as well. I do know the IP alone costs $12/year, so we'd have to charge at least $2 to make money on the actual server.

WP is garbage. I've seen WP get accounts suspended with no plugins at all. WP is the only CMS that causes load consistently too. As flazepe said, they keep patching it and have never bothered to actually fix the horrible mess of band-aided legacy code that the thing runs on... We'll let Krydos identify the file, but odds are he's going to list index.php due to WP's design. Unless there's malware or something, the system often can't identify a specific plugin or file that's affected when a user is running WordPress.

That's likely because we get a lot of junk sites on here (typically such content is abusive users who create accounts with the goal of setting up illegal stuff like phishing and ponzi schemes, or questionable content like MLMs, etc.). All major free hosts have this issue in our experience. We're more proactive than most, running our own dedicated systems to detect phishing and abuse (as opposed to relying strictly on abuse reports like most other hosts) and try to remove it as quickly as possible, but we can't remove undesirable content until we know about it. For the same reasons, many mail providers mark our mail as spam too. Also, our advertising sometimes promotes questionable content like online gambling, crypto-currency products, and dubious dating sites. We allow these ads because they pay substantially more than others, and we need all the money we can get to stay in business since we don't sell our product. It's possible their filter picked up on these ads when it tried loading your page. Finally, depending on the capability of their systems, it's likely possible that their system picked up on the fact the site was suspended and made the incorrect assumption that it was due to abuse when it was simply due to WP being too heavy for the server (typical for WP).

We can't change the username of an active account, but I know it's been done before with archives (usually when they fail to restore). Krydos can probably do the same here since it's still archived.

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 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.

Takes care of that then

What IPs need access (or do you want any)? Krydos has to do this for you.

I always thought the same thing until I ran into a same-day request and sent it to Krydos wondering why it kept suspending despite having no scripts that send email on it.

@yashrs: You can't unsuspend an account that sent too many emails the same day it was suspended or it will instantly suspend again. You have to wait for the mail counter to reset first (at midnight UTC). @etravel: We'll unsuspend this at later today once the mail counter resets.

Done.

It appears it is indeed a registrar suspension since it still doesn't work despite valid DNS on our end. Interestingly, Netcraft actually admitted the error and retracted their phishing report this morning: https://www.helionet.org/index/topic/38278-hh436573-issue-8135680-false-positive-report-httploucasodeveloperxyzlokamail/ @loucaso: You need to contact Namecheap and see if they suspended your domain for abuse. If they did, you'll need to get them to unblock it (they should be able to help once you provide a copy of the retraction notice). On our end, if you want your old account back, please let us know and I'll delete your new one and unban the old one.

That's weird. The DNS looks perfectly fine: https://bybyron.net/php/tools/dns_records.php?domain=loucasodeveloper.xyz&rec=ALL ...and I can resolve it against our name servers: >nslookup loucasodeveloper.xyz ns2.heliohost.org Server: UnKnown Address: 64.62.211.133 Name: loucasodeveloper.xyz Address: 65.19.143.6 But not against any major DNS service like Google: C:\Users\Owner>nslookup loucasodeveloper.xyz 8.8.8.8 Server: dns.google Address: 8.8.8.8 *** dns.google can't find loucasodeveloper.xyz: Non-existent domain Lets give it a few hours to propagate and see if it starts working.

Also, do you have a second account? Please keep in mind that you're only allowed one active account at a time (suspended ones don't count).

Weird. It should never have shown the server select or be awaiting validation. It should've gone directly to the username page. Make sure you pick a different username too. New invite sent.

Krydos needs to do this for you.

Someone else probably saw the abuse report as well and re-suspended you. I spent 20 minutes looking through this account and don't see anything on there (files or databases) to suggest phishing, so I have no idea why they flagged this. The folder linked in the email is an unmodified copy of AfterLogic Webmail Lite... Interestingly enough, this isn't the first time I've had someone get suspended for this exact software program. I think Netcraft has an issue with that particular product for some reason. Since this is the second time I've seen AfterLogic get someone a phishing ban, I've removed it from Softaculous as well. I've sent an invite for a replacement account instead this time around. Please create a new account and just don't use that mail program.

Yep. I posted in the email topic. It was a false positive by Netcraft. Phishing reports have a ridiculously low false positive rate (like 1 in 200), and you're the lucky one Because we automatically suspend such reports, you were incorrectly banned for phishing. Your account has been unsuspended.

The domains rodrigo.cl and optidec.cl have been cleaned up. Try adding them now.

1. I suspect your contact form has a code issue of some sort. Assuming it's using something like mail() to send, the message should send regardless of the DNS records (though it may end up in a spam folder...). Also, keep in mind that some mail providers don't accept mail from us. You didn't say in your PM what email address the contact form is being sent to, but I can say that iCloud and GMX are not accepting mail from us at the moment. 2. For DKIM, you're seeing that error when you load Google's DKIM records because cPanel is expecting the DKIM records to be ours (ones that can verify the private key stored on your account). To fix this and allow both servers to send mail properly, you need to make Google use the same key as us. That way, both Google and Tommy will sign mail with a signature that verifies with our DKIM record. Set the DKIM records to the cPanel suggested ones, then download the required private key in Email Deliverability->Domain->Manage->View the Private Key. You'll need to check with Google for instructions on how to configure DKIM on Google's system to use that key. If Google is unable to accept an outside key, you can ignore the warning and set Google's DKIM records here against cPanel's recommendation. Just be aware that mail that originates directly from Tommy (e.g. stuff sent via mail() and the like) will not pass DKIM checks in this configuration and will often end up marked as spam. 3. For the SPF, try this: v=spf1 +mx +a +ip4:65.19.143.6 include:_spf.google.com ~all (this basically means "SPF check will PASS if your domain has an MX or A record for the sending server, if the sending IP is 65.19.143.6, or if any of the conditions provided by _spf.google.com match, FAIL if anything else"). 4. PTR is a Reverse DNS record. DNS takes names and translates them to IPs. Reverse DNS does the opposite (takes an IP and finds the domain name). Email systems sometimes use it as one method for reducing spam by comparing the PTR record of a server's IP to the name the server announces itself as. If a dubious server announces itself to another mail server as "tommy.heliohost.org", but a reverse DNS query for that dubious mail server's IP comes back as "imnottommy.com", there's a good chance the server at imnottommy.com is impersonating tommy.heliohost.org to send questionable mail. If you notice in cPanel, you'll see a notice about an alternate HELO for the mail server that doesn't match your domain name. The mail server identifies itself as tommy.heliohost.org when it sends mail, because you're on a shared IP address. A reverse DNS query for the shared IP 65.19.143.6 will always resolve to "tommy.heliohost.org", so the mail server must announce itself as such in order to pass this check. This message is there just to inform you of what our mail server announces itself as. The PTR's value should always match what the server identifies as. 5. The Authentication button is no more. Email Deliverability did indeed replace it in the newer version of cPanel.

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

Replace bornmx.ml in the server address with johnny.heliohost.org. You will not be able to use your domain for many of these sorts of features (cardDAV, mail, webdisk, etc.) because you use cloudflare.

It's due to Cloudflare. Subdomains won't work with Cloudflare unless you manually go to CF's website each time you create one and add a record to your DNS zone for your new subdomain. (Create a record with the subdomain as its name, type can be either a CNAME with the value set to your main domain, or type A with the value set to your server's shared IP address). As always our recommendation is to remove cloudflare and use the name servers that Luigi listed above. By doing this, you eliminate the need to configure DNS manually for each subdomain you create.

Sounds like Tommy got its act together (Accounts sometimes take a little while to work once they get moved, looks like Java is the same way...). Solved.

I don't see why not, but I'm not sure whether the cron will have the access necessary to connect to your databases when it runs. The cron should run as your user account. If you need to provide other credentials, read up on the .pgpass file. You can create it and put it in your home folder to provide credentials for psql to use.

Use johnny.heliohost.org as the host name instead of your domain. You can't use your domain as the host name because you're using Cloudflare.