Kairion

Hi @ceomega, Since you are unable to remove/manage your files due to the suspension, I'm escalating your case so one of our root admins will remove them for you.

This support request is being escalated to our root admins.

Unfortunately, Plesk does not provide that level of configuration to the hosting accounts. To allow those PHP directives we would have to also allow other that may lead to security or performance issues. Now that it is explained why we cannot allow users to change them, let's analyze your list: log_errors: Its default is already set to "On". error_log: That one has no default set. I'll take your suggestion to our root admins so they can check if it is desired to add it to all servers/user accounts. display_errors: Its default is set to "On". As wolstech said, it is possible for our root admins to change it per domain if a user requests it. error_reporting: Its default is set to "22519", which is equivalent to "error_reporting(E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED);". I believe it is also possible for a root admin to change it per domain if a user requests it, but only them can guarantee if it is possible. date.timezone: That one also has no default set. But considering our servers default time zone is set to "UTC" (which is a good practice when dealing with different, multiple or even unknown time zones) I do not see what would be the problem here.

This support request is being escalated to our root admins.

Hi @atesin, I do am aware there are such alternatives depending on someone's using scenarios, they just do not fit the HelioHost's use-case, as someone hosting here will: Like to have an actual email server (i.e. sending and receiving emails through their (sub)domain), Not use email at all, Use a script/software/library that already has SMTP support for sending emails through an external server. Changing from Postfix to any of those alternatives would remove a hosting feature and break the use for an uncountable number of our users. Using any of those alternatives you have pointed out is possible on a VPS, where you have full control of the entire operational system and it is all yours, thus you can install and manage it however you like, without the need to take into consideration anyone else's use-case.

By default, the PHP mail() function can only send emails through your local mail server and cannot be configured to use external SMTP servers. However, if you are on a Virtual Private Server (VPS), you can change your Mail Transfer Agent (MTA) settings, such as sendmail (as you mentioned), to use an SMTP relay. This allows your mail() function to send messages through your local server, which then uses the external SMTP server to send the emails. For example, I have set up my MTA to relay messages through Google Workspace's server. This enables me to use Google Workspace's security features and also keep copies of the emails my server is sending. It's important to note that this configuration affects all users on the same server, so it's not possible on shared hosting environments like Tommy, Johnny, Ricky, and Lilly. If you want to use external SMTP servers on a shared host, you will need to use a library such as PHPmailer or Symfony Mailer or create your own. Regarding your comments about your customizations: While customizing software can be useful for learning and testing purposes, it's important to be cautious when making changes to standard software in a production environment. Any customizations should be thoroughly tested, and you should be aware that any changes to standard software may require you to fork and maintain the customized version with its upstream version to avoid security risks and ensure compatibility, which usually is more trouble than it is worth.

I'll escalate your case to Krydos.

As your request needs DNS changes, Krydos is the who usually deals with that. He only checks the forums like once a day, and it's usually in the evening or late at night. Typical response time is 24-48 hours for things needing Krydos' attention.

Hi, atesin. You are starting from a false premise that the PHP mail() function is not enabled at HelioHost servers, but that is not the case, as this function is enabled, and any user is free to use it. If users do not want to use that function, they can also use external PHP mailer libraries, such as PHPMailer, which you pointed out. About being listed on blacklists, it happens with every single email provider. When it happens, the provider must deal with that. In HelioHost's case, we count on our users to let us know if they have any issues with their emails, and we fix them when that happens. We also do have the following email quota limits (which can be changed upon request to our root admins, which may or may not allow it), which help us to stay out of blacklists: Account's email quota of fifty (50) emails per day, Email account's quota of ten (10) emails per hour. After someone reaches any of those limits, that someone is unable to send new emails until the limit is reset at midnight UTC. You need to note that any solution you adopt is subject to being blacklisted/undelivered, as it is outside of the sending server/provider scope (even if the sending server/provider is not on a blacklist, the email can still not be delivered or be flagged as spam, as it is solely a decision made by the receiving email server), meaning there is absolutely no 100% way of guaranteeing your emails will be delivered to someone else's email server, much less to their inboxes. If you want to have a different email provider, there are some free alternatives: Zoho Mail has a "free forever plan", but unfortunately it does not allow IMAP/POP3/SMTP connections (email access is only possible through their mobile apps or via their webmail on the free plan) but could be useful if a user only needs free email hosting (up to 5 free email accounts). For sending bulk emails, you can check https://influencermarketinghub.com/free-bulk-email-marketing-services/, which has a list of some services that may provide free sending bulk emails, though with some limitations or on trial plans.

Honestly, either I do not understand your concept, or you do not understand the points I am raising. The question stays the same: what if a user never changes the primary domain? E.g., I have the account kairion.helioho.st. I have no reason to change my main domain, even if I add new ones into my account. If I (against HelioHost ToS) decided to create a new account abc.helioho.st and start a new site with different, unrelated content to kairion.helioho.st, it would still be a ToS violation, as a user is allowed to have only one account with 1000 MB (unless that person does a donation of $5 or multiples of it, receiving +1000 MB for each, up to the maximum of 5000 MB). Where the script is running, while still is an issue, does not exclude the impact HelioHost servers, as that hypothetical computer would have to access data from all of them, thus consuming their resources. Using a laptop is also not workable, as it would be outside of our datacenter network creating a new security concern (and thus leading to human and computational resources necessary in securing that connection). Though it is a concern to avoid users creating multiple accounts for cross-hosting, the greater concern (and what is more common to happen, at least in my experience), is having users creating multiple accounts for hosting different sites without being limited to our 1000 MB per user/account. That would be a philosophy debate about morals and ethics. If we consider only the technical side, someone will need more resources than we can provide before having a website/app/service capable of earning enough to be a millionaire, thus they would have their accounts suspended long before that happens (and invited to either move to a VPS, which also has its physical limits, or would have to move to either an enterprise solution or create their own infrastructure).

This support request is being escalated to our root admins.

This support request is being escalated to our root admins.

All the above posts are originally from the topic account suspended?... i just created the account a couple hours ago! and have been split into this new topic. There are a few issues: What if the user never changes the primary domain (as there is no reason to do that in first place)? If you are talking about changing the domain's content (i.e., files and databases) that would not be doable, like the above option, for the same reason explained below. HelioHost has four shared hosting servers now (Tommy, Johnny, Ricky, and Lilly) and there are plans for a new one (Morty). New ones can also be created in the future. Each one has more a lot of (sub)domains, and resources that are now used to provide free services would have to be redirected to that check running. It also would not escalate well (as it would be necessary to run it for any changes). It would have a lot more of false-positive matches than the current method (checking multiple accounts using the same IP address), because as you pointed out: "[...] for example, imagine i am browsing the web and i found a very interesting info that i put on my website, without knowing that info is ALSO hosted in heliohost ... additionally, if some user deploy a public modifiable content (say a forum or blog) ANYBODY could publish heliohost cross hosting links in his/her site, triggering the alarm [...]", It would still be useless against users hosting multiple sites (i.e., different sites / different contents, but the same owner) or using multiple accounts for file hosting. There is no specific item in HelioHost Terms of Service (ToS) ruling about "reselling hosting", so technically someone could do that if. The same goes to profiting while doing that. However, it should be noted that, according to that same ToS: Which means that, if our root admins consider it to be an abuse and unfair use of the free service provided, they could (1) act to stop that use by deleting, changing, or editing the account and (2) changing the ToS. A possibility that would not be against the ToS: that "single guy" could sell the webdesign service (since this is that person's work, it is obviously not ruled by HelioHost at all) and help the clients to set up their own free HelioHost accounts for webhosting.

Well, you kind of pointed out all the problems/downsides with all your suggestions. About checking referrer headers for cross hosting, it would be useless against users that are only avoiding our 1000 MB disk space per account limit to host different websites (or just using for file hosting). WHOIS lookup also is not doable because: The majority of HelioHost users use free services like Freenom, eu.org, or even HelioHost own subdomains (something.heliohost.us and something.helioho.st), People with their own domains may have, according to their registrar rules, WHOIS privacy protection, e.g., https://mxtoolbox.com/SuperTool.aspx?action=whois%3akairion.eu.org&run=toolpage. You cannot get a single detail about me by doing a WHOIS lookup to kairion.eu.org.

Unfortunately, there are no correct answers considering the resources we have available. We could demand a government ID to allow signups (which would be an enormous resource-consuming solution, as those systems are pretty expensive), and even that would not be enough to guarantee people would not have multiple accounts. Thus, we use what is less resource-consuming: blocking/suspending multiple accounts with the same IP address. It is one of HelioHost's Terms of Service and part of the Suspension Policy that a user can only host multiple sites on the same account. Users could abuse and host multiple sites on different accounts (avoiding the 1000 MB disk space limit). Of course, there are cases, like yours, where there is no terms or policy violation, as only one account is yours, the other being from your organization, which is why we have that forum section for our root admins to analyze cases of suspended accounts. Remember that HelioHost is a non-profit organization, which means it does not have a lot of resources (monetary or human), as it is kept only with users' donations and the signatures of VPS plans (whose payments give some extra funds to keep up the bills).

Thank you for providing the necessary information, @sylvain. I am escalating your case to our root admins.

Hi @ojplanet, As per your request, your account was deleted, and an invite to create a new one has been sent to your account's email address. Please let us know if you need help with anything else. PS.: I have split your post into a new topic since it is a new support request. Also, are you sure it is really needed to wipe your account? Personally, I have nothing against it, but on a shared host I cannot imagine why you would need to wipe your account in such a close time span since your last wipe.

Could you please post that screen without it being mirrored and upside-down? Please also post new, unrelated to this topic subject, questions/issues into a new topic(s), so we can keep our forums organized. PS.: I moved the topic to the "Website Management and Coding" section as it was a question unrelated to HelioHost services but to Gcore services.

E-mail management is kind of difficult because we are dealing with servers over which we have absolutely no control at all (recipients' email servers). For starters, getting a 9/10 or even a 10/10 at mail-tester.com is the basic. Then you would need to pay attention to your domain suffix (though they should not, some email providers do treat some suffixes differently than others, e.g., some of the Freenom ones are treated as spammers by some email providers). Your domain's age could also play a role here (older active domains have a better "score" with some email providers). Some providers even have unknown/undisclosed rules to define what emails go to your spam or inbox. But overall, the truth is you did everything you could do now, just ask your recipients to unmark your emails as spam on their providers, and that will improve your delivery to that provider's inbox. For email providers that strictly follow email-related RFCs, you should get your emails delivered to their inbox if you have a 9/10 or a 10/10 at mail-tester.com.

Hi @ojplanet, It is kind of impossible to help you without knowing what errors are being thrown. Trying their instructions and then coming here without letting us know the entire history of your issue makes us unable to provide assistance. Regarding that message you copy-pasted, it is talking about rules that you may have created at Gcore, meaning it has no relation to where you are hosting your website. We also have absolutely no way of knowing which rules you (may have) created at that CDN, as it would require access to your account's dashboard. As far as I could check from the page that your copy-pasted message linked, it is necessary to create a rule with the system template "Let's Encrypt HTTP-01 challenge", as it will create a proxy from yourdomain.com/.well-known/acme-challenge/TOKEN to Gcore's generated token so you can get a Let's Encrypt certificate through them without your webserver (in your case, HelioHost) gets involved. Unfortunately, as a non-Gcore services user, this is the furthest I could go with the information you gave us.

Hi @c00lcr4b, I have sent you a new invite. Please note our invites are valid only for up to 7 days. Please let us know if you managed to recreate your account, and if you have any other questions or issues feel free to contact us anytime.

Hi @cielitoangelo, The topic that you linked also explains how to get your DKIM records: Please let us know if that works for you or if you have any questions.

I will move this topic to Contact HelioNet, as it is a request related to our forums. As soon as a root admin fulfilled your username change request, they will let you know.

Unfortunately, I am quite sure it is not possible, but either way, the definitive answer should be set by our root admins. This support request is being escalated to our root admins. Edit: As an alternative, you could request a free eu.org "domain" at https://nic.eu.org/. They do take a while to approve domain requests (all process is manually verified by a person) but it will effectively give you an address that you can host its DNS anywhere[1] you want and use it on your HelioHost account as well. E.g. https://kairion.eu.org/. [1] I would recommend Cloudflare, Hurricane Electric Hosted DNS, or deSEC.

Thank you for sharing the email address, @Raven. As you said, I have found your registration, and you are right; it was registered with your email address without its dash (hyphen). I have removed that email address from our database and have sent you a replacement sign-up invite to your correct email address. Please let us know if you have received it and managed to create your account.