alkastraverse

username: alkastraverse please reset my account. thank you so much!

Hi My username is alkastraverse Please add new domain: alk.helioho.st Thank you so much!

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

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

Same view 🫠

No problem:3

Full RAM or too much traffic on server 🐸

You have traveled through time 🐧

Wait, what's this? I think SMTP mail server is this domain🤔

Me too 😭

Lmao markdown is not working 🐸

If your goal is to get an additional TLS certificate (separate from the one automatically issued by SSL It! in Plesk), you won’t be able to use the normal webroot ACME challenge, because as you noticed nginx blocks direct access to `/.well-known/acme-challenge/`. A few alternatives you can try: - Use the **DNS-01 challenge** instead of HTTP-01. Let’s Encrypt supports this, and it doesn’t depend on webroot access. - If you only need the cert for client-side authentication, you could generate it via certbot or acme.sh on your local machine and then import it into Plesk. - Or simply rely on the default Let’s Encrypt certificate managed by SSL It! for the domain, since it’s already trusted by browsers/clients. If you don’t have a VPS, the easiest and most reliable approach is probably **DNS-01 validation** through your domain’s DNS provider. That way you can still issue a valid cert without touching nginx config. Hope this clears things up a bit!