wolstech

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.

Is there an error_log file being generated in the folder where the app is installed? There's tons of things that can cause a 500 error. Permissions and bad htaccess files are the most common reason, but the fact the login screen works and you used softaculous makes me think that's not the case. It's more likely to be incompatible software or even just high load in this case.

Received. Incoming transfer: Hash: a3213831c9e8bd225b5113fe7db424ca5126ee914faabdfc31323b19f0bf6a32 Block height: 2243349 Timestamp: 2020-02-01 00:32 Amount: 50,000.00 TRTL

The wallet has to rebuild because of a software update. That usually takes hours or even days to finish, so I won't know until tonight or tomorrow.

User account nomaedox was found hosting the xupload.ir domain today and has been suspended. Regardless of who purchased it, .ir domains are not welcome here because the ICANN-assigned registrar for them is in Iran (even if the user is not). We are legally prohibited from doing business with Iran as explained above. Also, doing some research on the IP...it belongs to a Microsoft Azure instance. I'd be willing to bet there's a VPN exit being hosted there. The IP on both otchau and nomaedox is also the same.

I don't know what happened on discord since I wasn't on there at the time, however I can say that your suspension is not a bug. You're violating our terms of service by having two accounts. You're only allowed one. Which account would you like to keep? I'll be glad to unsuspend you once I know which one you want.

The reset link on our website doesn't work right half the time. Things like server load tend to cause it to fail. Try using this instead to reset it: https://tommy.heliohost.org:2083/resetpass?start=1 , then try signing in here once you complete the reset process: https://tommy.heliohost.org:2083/

Your IP suggests Virginia (google says its assigned to Microsoft or Xerox), which makes sense. I'll let Krydos take a look. I suspect something suspended you based on your domain, and you might be the unfortunate circumstance of being a US citizen with an Iranian domain. Keep in mind you may be asked to privately send us a scan of your ID to prove you live in the USA, but I'll let Krydos decide if that's necessary.

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.

Our services are not available to users in the country of Iran. Because HelioHost is based in the USA, Federal Law forbids us from offering our services to users in Iran and North Korea.

It was for failed cPanel logins. Unblocked. Also, if you use https://heliohost.org/login/ instead of the direct cPanel login screen, this won't happen to you.

The domain xupload.ir has been released and is now available for reuse. As for what happened, this is an interesting one. You left your domain pointed to our name servers, but had no account with us for a period of time, so the domain was not associated with an account. A domain thief signed up a few weeks ago and attached every unassociated domain to his account, presumably so he could abuse them to serve malware, ads, or phishing. For security reasons, when we detected and banned the domain thief, we didn't release any of the domains to avoid him doing it again. The error you were seeing was a result of the domain being owned by another user (the thief's banned account).

I don't know if anyone has ever done this here honestly. We only have a few people who use Python, even fewer of those use flask, and to my knowledge exactly zero use flask with postgres. Sadly you're unlikely to get help for this one, if anything you'll be told to use mysql instead. Krydos can probably answer #2 for you (.htaccess file comes to mind, but I have no idea whether that would work with flask/python). He can also enable postgres remote access for you. What IP would need access to it (or should we allow any)?

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