All Activity

I think this has happened before...Krydos can exclude it. Escalating.

Honestly, you should avoid using PHP's mail(). - Many shared hosts disable it. - Even if it works, emails often land in spam. - It doesn’t support authentication or encryption. PHPMailer (with SMTP) is much more reliable and is considered the best practice for sending emails in PHP today.

PHPMailer is more reliable than PHP's mail(), and works well on shared hosting without Composer. Steps: 1. Download PHPMailer ZIP here 2. Upload the folder to your host (e.g. /phpmailer/) 3. Use this sample code: <?php use PHPMailer\PHPMailer\PHPMailer; require 'phpmailer/src/PHPMailer.php'; require 'phpmailer/src/SMTP.php'; $mail = new PHPMailer(); $mail->isSMTP(); $mail->Host = 'your_email_server'; $mail->SMTPAuth = true; $mail->Username = 'your_email@example.com'; $mail->Password = 'your_app_password'; $mail->SMTPSecure = 'tls'; $mail->Port = 587; $mail->setFrom('your_email@example.com', 'Your Name'); $mail->addAddress('recipient@example.com'); $mail->Subject = 'Test Email'; $mail->Body = 'Hello, this is a test email sent via PHPMailer on shared hosting.'; echo $mail->send() ? "Sent!" : "Error: ".$mail->ErrorInfo; ?> PHPMailer + SMTP ensures better deliverability, supports HTML emails and attachments

I am working with google oauth. The URL that is called by google seems to be blocked by heliohost. In the Web Application Firewall I added the security rule ID 210580, but that didn't help. From this forum post it seems like you need to adjust the rule on your side: https://helionet.org/index/topic/63233-solved-google-login-not-working-calling-a-403-error/ Would you be able to do that? My domain is https://knowledgebase.heliohost.us Here is the error [client 2a02:21b4:1a35:d800:7573:34c7:4ad9:cef7] ModSecurity: Access denied with code 403 (phase 2). Matched phrase ".profile" at ARGS:scope. [file "/etc/httpd/conf/modsecurity.d/rules/comodo_free/08_Global_Other.conf"] [line "57"] [id "210580"] [rev "2"] [msg "COMODO WAF: OS File Access Attempt||knowledgebase.heliohost.us|F|2"] [data "Matched Data: .profile found within ARGS:scope: email profile https:/www.googleapis.com/auth/userinfo.email openid https:/www.googleapis.com/auth/userinfo.profile"] [severity "CRITICAL"] [tag "CWAF"] [tag "Other"] [hostname "knowledgebase.heliohost.us"] [uri "/api/auth/callback/google"] [unique_id "aK7wBxk6NpbxASBBcBFsRQAAAU8"]

Do you think your site has a configuration error (eg. Php,...)🤔

It causes high traffic 🗿(or not)

Hmm... I think a bad robot is using brute-force to crack the password

Change both the outgoing and incoming mail sever settings to johnny.heliohost.org as above and try again. Many programs don't like when you use your domain in the mail server fields because the server identifies itself as johnny.heliohost.org when you connect. Also, (while not the case here) some people use Cloudflare, which can't pass mail connections.

That feature is only available for Morty users.

Your account has been reset, check your email for a new invite to recreate it.

pls reset my account for me

Pls i want to reset my account, and start over, new start, new domain, new building

im on johnny the username is cfcatboy and i want it on cfcatboy.heliohost.us/lightbulb please

can i please have WSGI Control Access my domain is cfcatboy.heliohost.us

Domain added. it can take up to 2 hours to start working.

Hello, I would like to add the domain: evigroup.org to my profile. My username is chapmjs. Thank you!

The email that I'm trying to setup with Hubspot is for yieldandco.com. I have been able to access all the email accounts from webmail just fine. For some reason the IMAP/SMTP is not syncing up correctly. Here's the server settings: Outgoing mail server (requires authentication) yieldandco.com Incoming mail server yieldandco.com

Have you tried using johnny.heliohost.org as the hostname?

My username is joyusecommerce. I'm trying to connect Hubspot CRM to my email via IMAP/SMTP. Hubspot is getting an error that it can't set up the email with a server side error. I have triple checked the information, performed it twice, the third attempt I tried mail in front of the domain and it didn't work either. Please help, since I don't see a log for the actual error that is occurring. The settings that I have are 993 for IMAP and 465 for SMTP.

Account has been reset, and a new invite was sent to your email address.

Yes, Please

I already fixed like 10 errors and they kept leading to exponentially more and more errors. I'm not going to waste 6+ hours screwing around with it, and even then may not be able to fix everything. We're all volunteers and we don't get paid to work on your VPS. There are more important things like setting up the new Ricky server that would benefit the community more. You're welcome to hire a third party to fix the issues for you, but you're probably looking at $100+ per hour to fix issues like this. You're also welcome to start reading the error logs and fixing the issues yourself, but depending on your skill you may make things worse. It's really not difficult to backup your data and restore it after the rebuild. I rebuild my VPS every 6 to 12 months anyways just to keep them running at top performance.

Got it, thank you

You wouldn't create an A record pointed to the name servers, you'd make an A record pointed to the IP shown in Plesk (the one ending in .94 in your case). The IPs for a domain can be seen in Plesk at the bottom of the domain below all the options. Note that by using external DNS, some features of our service will not work properly or may require additional configuration. The most notable is that your domains will stop working due to an IP address change if your Morty account were to ever move to Tommy due to nonpayment. (If you use our NS, we just change the records for you and you experience a zero-downtime move). Email service will also not function properly unless you create the additional records on your DNS server to support it (there's an MX record and several TXT records that are required, plus an A record for webmail if you want that).

Correct. Use mydomain.com/landingpage instead. Wildcard certs will technically work on the server if you were to manually generate them (you'll need to use external DNS as well as a third party tool to do this) then upload them to Plesk, but you'll have to do this process manually every 90 days. It's specifically the automatic issuance and renewal of wildcard certs that's not supported, not the certificate itself.