Jump to content

alkastraverse

Members
  • Posts

    28
  • Joined

  • Last visited

Everything posted by alkastraverse

  1. Wow, that's absolutely amazing, I just tested it on Mail-tester and got a perfect 10/10 score. Thank you so much, Krydos, for setting up everything including DMARC so quickly. You're a lifesaver! Love this community support.
  2. Hi Admins, I successfully generated the SSL certificate thanks to your help. However, when I try to send an email from contact.me@alk.helioho.st to Gmail, the messages are completely blocked with a 550-5.7.26 error because SPF and DKIM authentication failed (DKIM = did not pass, SPF = did not pass). Could you please add the standard SPF and DKIM TXT records to the DNS zone of alk.helioho.st so Gmail can authenticate my mail server? Domain: alk.helioho.st Server: Tommy Username: Alkastraverse Thank you very much!
  3. Hi Admins, I am using a free subdomain provided by HelioHost on the Tommy server. Since I do not have direct access to manage the root DNS records for this domain extension, I am unable to resolve some SSL issuance errors via Let's Encrypt in Plesk. When I try to secure my domain, I encounter the following issues: webmail.alk.helioho.st returns a 404 Not Found during the HTTP-01 challenge. mail.alk.helioho.st returns an NXDOMAIN error (missing A/AAAA records). Could you please help me check the DNS zone configuration or manually fix the aliases/routing for these mail subdomains so they can be successfully secured? Here are my account details: Main Domain: alk.helioho.st Server: Tommy Plesk Username: Alkastraverse Thank you so much for your amazing support!
  4. Hi My username is alkastraverse Please add new domain: archive.alk.xx.kg Thank you so much!
  5. username: alkastraverse please reset my account. thank you so much!
  6. Hi My username is alkastraverse Please add new domain: alk.helioho.st Thank you so much!
  7. 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.
  8. 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
  9. Do you think your site has a configuration error (eg. Php,...)?
  10. It causes high traffic ?(or not)
  11. Hmm... I think a bad robot is using brute-force to crack the password
  12. No problem:3
  13. Full RAM or too much traffic on server ?
  14. You have traveled through time ?
  15. Wait, what's this? I think SMTP mail server is this domain?
  16. Lmao markdown is not working ?
  17. 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!
  18. I think you should check realtime in time.is then you can click before some second
  19. If you want a cool polygonal background with connected dots like **ipscore.io**, you can use **particles.js** or **tsParticles** ? Here’s a quick example with **particles.js**: <!-- Step 1: load the library --> <script src="https://cdn.jsdelivr.net/npm/particles.js"></script> <!-- Step 2: create the container --> <div id="particles-js"></div> <!-- Step 3: CSS to make it full screen --> <style> #particles-js { position: fixed; top: 0; left: 0; width: 100%; height: 100%; z-index: -1; /* stay behind content */ background: #0a0a0a; } </style> <!-- Step 4: configuration --> <script> particlesJS("particles-js", { particles: { number: { value: 80 }, size: { value: 3 }, move: { speed: 1 }, line_linked: { enable: true, distance: 150, color: "#00ffcc", opacity: 0.4, width: 1 }, color: { value: "#00ffcc" } } }); </script> ? The result: your website will have a dynamic dots-and-lines background just like ipscore.io ? If you want even more effects, check out **tsParticles**: https://particles.js.org/
  20. Hi HelioHost Support, Please help me add the following subdomain to my hosting account: Username: alkastraverse Subdomain to Add: alkverse.mooo.com Thank you for your support! Best regards, alkastraverse
  21. I believe the issue is caused by `$this->results[$queryKey]` being overwritten when you run a new query inside `getCategory()`. So when you call `$this->fpdb->query(...)` in `getCategory()`, it updates the `$this->results` map and the current query key, which breaks the loop in `getProperties()` because `fetch_object()` now references the subquery instead of the original result set. To fix this, you can store the result of the main query in a temporary variable before entering the loop, like this: function getProperties() { $s = "SELECT * FROM properties"; $result_set = $this->fpdb->query($s, return_result: true); // store raw result $result = []; while ($r = mysqli_fetch_object($result_set, Property::class)) { $r->category = $this->getCategory($r->cid); $result[] = $r; } return $result; } This way, even if `getCategory()` runs a subquery internally, it won't interfere with the loop iterating over your original `$result_set`.
  22. Looks like this board is a bit quiet recently. Just sharing in case someone finds it useful later.?️
×
×
  • Create New...