wolstech

Perhaps I wasn't clear about the details. Specifically, your account cannot be unsuspended because it has an Iranian domain attached to it. For legal reasons, we cannot host any domain ending in .ir (the country code for Iran). If I recall correctly, these country domains require you prove you're affiliated with that country to purchase, so even if you're in the Netherlands as you claim, you've proven you have a connection to Iran simply by owning that domain.

Care to explain why you have an Iranian domain on your account? We are not able to host any domain ending in .ir for legal reasons.

HelioHost services are not available to users in the country of Iran. Because we are based in the USA, which has an embargo against the countries of Iran and North Korea, federal law forbids us from offering our services to any user in those countries. Your account cannot be recovered or unsuspended.

This is probably something Ashoat would need to provide. I’m not even sure if Krydos can provide it, but he reads the forum a lot more than Ashoat does.

Unarchived. It may take up to 2 hours to start working.

Done. You should now be able to log in and your website should start working within 2 hours.

Unarchiving...

Done. You should now be able to log in and your website should start working within 2 hours.

Unarchiving...Ricky accounts usually take a while.

Done. You should now be able to log in and your website should start working within 2 hours.

Your username is iglake, not iggy. Unarchiving.

So, digging into this further, this is definitely a DNS issue somewhere. I can't get your domain to resolve at all on major DNS providers like Google. Until that works, AutoSSL won't work either. > vidon.net 8.8.8.8 Server: [8.8.8.8] Address: 8.8.8.8 *** 8.8.8.8 can't find vidon.net: Server failed > vidon.net 8.8.4.4 Server: [8.8.4.4] Address: 8.8.4.4 *** 8.8.4.4 can't find vidon.net: Server failed > If I query our own NS, that doesn't resolve either (comes back as "No response from server"), even though the zones exist and are in sync. Oddly, the domain works if I visit it. I'm going to remove and re-add your domain and see if that makes a difference since the registrar is insistent it's not them.

That's a question for the registrar. Have you contacted them?

Answered on discord.

I noticed this in WHM today while trying to manually run AutoSSL for someone...apparently AutoSSL is hitting a rate limit from LE for some reason. Is there a reason Tommy is using LE? I thought we specifically didn't use LE for AutoSSL because of these severely undersized limits?

Done. You should now be able to log in and your website should start working within 2 hours.

"Rate limit preventing DCV" sounds like the server is asking for too many certificates...

Unarchiving...

Yeah, they won't delete if they're archived. Now that it's working, you should be able to delete it. Keep in mind that when you delete an account, the account will go inactive until the deletion actually occurs.

What version of PHP is this running on? Do they match? Tommy and Johnny default to PHP 7.x nowadays. if you're developing on PHP 5.x, you need to change the PHP version in cpanel. Also, are you sure the database settings are correct? That code will not work if the database connection fails. Your code lacks error checking for database errors, so unless it exists inside the Database class, your code would simply die quietly if the connection fails.

The accounts are suspended for multiple reasons. First, you're only allowed one account. Creating more than one will cause all of them to get suspended. Second, we have reason to believe that all of these accounts (and yes, there are more that are very similar that you didn't list...) are intended for phishing activity. HelioHost does not tolerate phishing or related illegal activity, and permanently bans any account that appears to be involved in, or that is likely to engage in, such activity.

Installed Python modules on Johnny can be found here: https://krydos2.heliohost.org/cgi-bin/modules37.py Most of your list is missing from this one. Krydos will need to install them.

You'd have to provide a class called cpanel in order for it to be defined. There's no such class defined by default. If your code doesn't provide such a class, you can't use what doesn't exist. If it exists and isn't being loaded, ensure you included it or that a class loader is detecting it. It's worth noting that if this is intended to be an api for the hosting control panel, we don't offer api access to the hosting system (though curl has been used by some in the past to automate the UI).

I doubt it will. The system verified the domains already, but for some reason is unable to get certificates from the CA for these domains. WHM is showing them all in the AutoSSL queue as pending: www.vidon.phink.heliohost.org vidon.phink.heliohost.org phink Feb 2, 2020 4:21:01 PM 822437841 Pending vidon.phink.heliohost.org vidon.phink.heliohost.org phink Feb 2, 2020 4:21:01 PM 822437841 Pending webdisk.vidon.net vidon.phink.heliohost.org phink Feb 2, 2020 4:21:01 PM 822437841 Pending cpanel.vidon.net vidon.phink.heliohost.org phink Feb 2, 2020 4:21:01 PM 822437841 Pending webmail.vidon.net vidon.phink.heliohost.org phink Feb 2, 2020 4:21:01 PM 822437841 Pending mail.vidon.net vidon.phink.heliohost.org phink Feb 2, 2020 4:21:01 PM 822437841 Pending www.vidon.net vidon.phink.heliohost.org phink Feb 2, 2020 4:21:01 PM 822437841 Pending vidon.net vidon.phink.heliohost.org phink Feb 2, 2020 4:21:01 PM 822437841 Pending www.jeep.vidon.net jeep.vidon.net phink Feb 2, 2020 9:25:44 AM 822329703 Pending jeep.vidon.net jeep.vidon.net phink Feb 2, 2020 9:25:44 AM 822329703 Pending Lets have Krydos look at this. AutoSSL on Tommy is usually pretty quick about getting certs, so I suspect these are stuck.

Those certs are sitting in the queue waiting to be issued by the CA, so it's not even us that's causing the issue. They've been sitting in there since yesterday according to the system. Not sure why they're taking so long...the domain validation passed fine. Once they get issued they'll be installed on their own. If for some reason they don't get issued in the next day or so, let me know and I'll have Krydos look at it. In the meantime, I'd suggest just removing your SSL redirects so people don't see the security warnings. I took a look at your site, and there's not really anything that needs SSL, so the lack of security should be negligible until this is fixed. You don't have any forms or the like that I could find.