wolstech

Those are the correct settings. Make sure you're using the username, not email address, for the username. Other than that, I'll escalate this to Krydos to see if he has any additional insights.

Please don't keep trying over and over, doing so will result in the server blocking you completely, which is why everything stopped responding. You've been unblocked. If your FTP account isn't working, try resetting your password. You can also manually change just FTP's password through Plesk.

You're probably thinking of the Laravel toolkit. We removed support for it because it was causing excessive load (Laravel is extremely bloated, arguably worse than Wordpress) and breaking people's domains when they later tried to uninstall it. Try using the Laravel options in Softaculous instead to install it if you really want to try Laravel.

That's normal unless you've requested to have that set up. Let's see if we can get that set up for you... (Krydos might do it, otherwise I'll do it when at a PC in the morning...on an iPad at the moment).

Also, the webmail.jmreece.com subdomain is working for me. DNS can be slow to update sometimes, especially due to caches.

Our name servers do not support DNSSEC (we do not sign zones), so domains using our name servers will always fail validation for it.

Account ebsug has been restored and ebsug1 has been suspended (it will delete itself automatically in time). Please update DNS for your domain to use the IPs shown in the Johnny account's Plesk and your domain should work.

Glad to hear. Let us know if you need anything else.

Changed

Domain added. For DNS, please use ns1.heliohost.org and ns2.heliohost.org as the name servers. If you want to use external DNS instead, the IP addresses for your domain can be seen in Plesk. The domain can take up to 2 hours to work.

It should be fixed now. If you remove it and set it up again, does it still warn you?

Yeah that's self signed...I've asked in a staff channel about why it isn't using the lets encrypt certificate...

HelioHost exclusively uses free certificates from Lets Encrypt, so if Apple has chosen not to trust "ISRG Root X1" by default, you may need to install that root certificate or mark the certificate as trusted in keychain. Does it say exactly why the certificate doesn't verify (common name invalid, root not trusted, etc.)? There may be an option to view/inspect certificate. If it's complaining about the root, what root certificate does it say the certificate is from? What common name is on the certificate? If one or both values are "Plesk" (self-signed), let me know as it means there's a mail server configuration issue.

We've never had much luck with using your domain as the host name for mail clients. It rarely works when using our name servers because of SSL issues, and is not supported at all if you use Cloudflare (especially with the proxy turned on...which you do), so that's sort of expected. We always recommend the server's hostname be used for mail instead as a result. This bypasses cloudflare since our server hostname is always pointed to our own NS, and it uses the system certificates instead of the SSL certs issued for your account. It sounds like your mail client or PC is incompatible with Plesk's mail server. Can you try it on a different device?

The SSL for webmail should start working in the next 2 hours. If you plan to send email, I highly recommend setting up DKIM as well if it's not already set up (the DKIM key can be had from Plesk's mail settings). SPF and DMARC are already there based on your picture. For the mail client, does your device support the let's encrypt CA root? The johnny.heliohost.org domain definitely has a valid certificate. If you're unable to get it working, it's likely an issue with your computer or mail client, as nobody else is reporting this issue.

Try it now.

I've removed the offending forwarder from your account and re-enabled mail service again, now waiting for it to unsuspend...

It immediately resuspended you. Argh. Let me try again...

It should work again in a few minutes. Tommy is being slow unsuspending you...

Yeah, forwarding will do it...each time it forwards an email, each recipient it forwards to would be counted as a sent message. Please remove the forwarder and fix the issue quickly. We can also raise the limit instead if you want, but I'd need to ask about that as this scenario is unusual (our usual process for increases is aimed at mitigating spam complaints from bulk email...forwarding between domains on the same account is kind of unusual in itself...). If you'd like me to look into that, let me know. Unsuspended.

The limit is 50/day. You also previously had mail service disabled for sending well over 100 on a prior day, but re-enabled your own mail (mail service removes itself when you exceed the limits, re-enabling it and continuing to send mail without contacting support results in a suspension for limit evasion). Can you explain why you were sending so many emails?

Also, make sure the CF proxy is disabled ("DNS only") for the webmail record.

Did you ever create a DNS record for webmail in Cloudflare? The reason this is looping is because it can't get a certificate. You need to create an A record pointed to the same IP as your domain for the webmail to work. Detail: DNS problem: NXDOMAIN looking up A for webmail.spanyolkonyvelo.es - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for webmail.spanyolkonyvelo.es - check that a DNS record exists for this domain I have no idea why the regular mail client doesn't work...the settings look correct. Can you try unchecking the option to configure automatically and specify the port?

Post a screen shot of the mail client settings so we can see what you're using. For the webmail, I responded to your other post as well. That's caused by having Cloudflare's SSL settings set to "Full (strict)". Change to "Full" without the strict mode and that should be fixed.

Try using johnny.heliohost.org as the host name when configuring mail clients instead of your domain.