wolstech

I did, but I don't believe that user considering what I found. The owner (or at least what I presume to be the owner, same username as the hosting account with fewer Ys) can be seen issuing bans for this sort of abuse in the warnings/bans tables of the database, so I can't say no effort was made or that he was welcoming the material in question. I suspect this is some combination of inadequate moderation, a pissed off user seeking revenge, and perhaps lack of effective means to prevent ban evasion. That said, if OP is unwilling or unable to fix this issue, he won't be welcome here.

I think I may be willing to give this site another chance. Looking through its database suggests that efforts are/were being made to remove or prevent the sort of abuse that got reported here, but that such effort was either simply not effective, not performed quickly enough, or not performed thoroughly. For example, I see the warnings table showing users being warned for "directed hatred and ignorance towards a protected group" and "saying n word", among other things. The ban list shows obviously racist users being banned as recently as 1/10 as well. If I unsuspend this, you'll need to agree to remove all racist and hateful content with 24 hours of unsuspension, and disable posting to your site until you can figure out how to keep this sort of content from returning (perhaps require approvals for new accounts, add more mods or even new software perhaps?). If we receive another complaint after that time, you'll be asked to find another host. Are you OK with this? If so, let me know when you're ready to clean the mess up and we'll unsuspend you.

I'll dig through the site when I get a moment and see what I think of the claims (I have two different users claiming the other is the one posting this crap, go figure...), but as I've already seen, this domain hosted content that is completely inappropriate. Regardless of who posted that content on the site, as I said above, HelioHost does not condone racism or other hateful content and it is the account owner's responsibility to make sure this content is not hosted here and that it's removed promptly when it is. At least one of the claims presented to me says the owner was himself engaging in the posting of this sort of content, which if true will result in a permanent ban. It may be a day or two before i can get to dig through this, however, in the meantime, this account is staying suspended.

I tested on 5.17.9 (latest). I'd have to download an old version when I get a moment to try that.

@Joeyseph: Content such as that posted in the screenshot (which I've hidden due to its content) is not welcome here, nor are insults. HelioHost does not tolerate use of our services to host racist, hateful, inflammatory, or unlawful content (including content that does things such as incite or promote violence). While we understand that people do run social media services on our service and it's quite possible that you were not the one who posted this content to your website, it is still your responsibility to moderate your own website and make sure it remains in compliance with our terms of service. That includes deleting racism, hate speech, and similar content immediately when its discovered, having an effective means for users to report such content for removal if they discover it, and being willing and able to ban users who post it to keep that content from coming back. Would you be able to effectively remove and prevent this sort of content from being hosted on your site again? Please keep in mind that if we agree to unsuspend you, you will only be given one chance to clean this up and keep it from happening again. If we discover or receive reports of this sort of content being hosted on your account again, you will be permanently banned.

Please keep in mind that the only account that works on SFTP is your cpanel username (not your email address!) and password. The "extra" accounts you can create are only valid when used over plain FTP on port 21. Unblocked.

Sadly we do not have a choice at the moment. Not only is it federally illegal to provide service to Iran, cPanel's terms of service also prohibit using the software to host Iranian users. Hosting an Iranian user can result in cPanel revoking our licenses or the federal government suing us, both of which would cause us to go out of business. As a result, we are legally required to issue Iranian users a permanent ban when they are found using our services.

Flazepe pretty much has it. It's illegal for us to serve users located in (or affiliated with) Iran since we're in the USA. You'll need to find another web host unfortunately

You need to set the domain's name servers to ns1.heliohost.org and ns2.heliohost.org at your registrar, then you just add the domain in cPanel under either Aliases (shows same content as your main domain), or addon domains (different content from your main domain).

Unarchived.

What IP address is blocked? (The one you posted from is not).

Paypal isn't available in his country (Turkey according to his IP). He'll need to donate using Skrill or crypto: https://www.heliohost.org/donate/ then post the transaction ID.

The system doesn't log this info. The connections are tracked by originating IP, not the domain they hit. The log just says "Failed IMAP logins". You'll need to check every mail client that's present at that IP, including things like phones.

Unsolved so he looks at it again.

lfd: Failed POP3 login Your mail client is configured incorrectly. Unblocked (it may take a few minutes to unblock).

Processes for none1632 have been terminated. This tutorial on building a Discord bot talks about starting/stopping long-running Python scripts: https://wiki.helionet.org/tutorials/discord-bot#how-to-get-started-with-a-discord-bot You should be able to adapt the start.py and stop.py from that to your application

Try signing in here: https://johnny.heliohost.org:2083/ I will say that load and performance issues are normal for Johnny though. That server is meant for experimenting and testing, not actually hosting a stable website, so it sacrifices stability and uptime to let more users have an account and the flexibility to run what they want. If you're to the point where you need to host a production website that works like you'd expect (i.e. is reliable and up all the time), you should move to Tommy. That server is intended for production use, and we much more tightly control load on Tommy to ensure it has good uptime. To give an idea, for the past few days, uptime for each server: Tommy: 100%Ricky: 99.27% (but really slow)Johnny: 96.2%

That account is not suspended. It's working fine when I open it.

Weird. cPanel is supposed to make sure the domain has an NS record = NS1.heliohost.org and NS2.heliohost.org before allowing an addon or alias domain. By design, this is not supposed to work. The fact it did is kind of odd. I thought maybe someone had turned on the allow remote domain option, but nope. I have no idea why this worked...

@Bailey: He can't. His attempt to add that will fail with a nameserver error because we don't support CNAME/A records for alias/addon domains. The only ways to make that domain work here is to use it as the main domain.

It is indeed a weird behavior. In the past we've tried setting up a specific page that's supposed to be shown for this, but it has never really proved reliable due to how cpanel works...

The weird page is because you're forcing SSL on a domain that doesn't have a certificate installed. When you do that, the server will serve the content of a random domain that has SSL installed (typically it'll be a random user's website, your domain just got lucky and the user's website looks like it could be from us). It fixes itself once AutoSSL runs and a certificate gets set up. I just manually ran AutoSSL for you so you can skip the 24 hour wait. Give it another few hours for the certs to install and Apache to restart again and it will work properly. You may need to clear your cache once its working in order to see it. 8:28:15 PM This system has AutoSSL set to use “cPanel (powered by Comodo)”. 8:28:15 PM Checking websites for “esn024” … 8:28:17 PM The website “thebrooksreflections.thebrooksreflections.heliohost.org”, owned by “esn024”, has no SSL certificate. AutoSSL will attempt to obtain a new certificate and install it. 8:28:19 PM The system will attempt to renew SSL certificates for the following websites: 8:28:19 PM thebrooksreflections.thebrooksreflections.heliohost.org (thebrooksreflections.com www.thebrooksreflections.com mail.thebrooksreflections.com webmail.thebrooksreflections.com cpanel.thebrooksreflections.com webdisk.thebrooksreflections.com thebrooksreflections.thebrooksreflections.heliohost.org www.thebrooksreflections.thebrooksreflections.heliohost.org) 8:28:42 PM The system has completed the AutoSSL check for “esn024”.

Changes can take several hours to take effect (Apache needs to restart).

Unpinning and locking due to being obsolete. Bailey, can you make a replacement post? I'll pin the replacement.

Unarchived.