For transparency: the error was quite simple: at one point in time, public subscription pages got deactivated for some reason or another. Apologies for the efforts!
Laktasekampagne
Posts
-
Fehler: {"message":"Dieses Feature ist nicht verfügbar"} / this feature is not available -
Fehler: {"message":"Dieses Feature ist nicht verfügbar"} / this feature is not availableThank you Girish -subscribed there :).
-
Fehler: {"message":"Dieses Feature ist nicht verfügbar"} / this feature is not availableHi there
at some point in updating, somewhere around 1. of July, our subscription form has stopped working when being requested from another domain.
newsletter-2/:1 Access to fetch at 'https://listmonkdomain/api/public/subscription' from origin 'https://otherdomain has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
The Settings do not seem to include means to whitelist a domain. GPT suggests this is handled in a configuration.toml file, which does not exists and the Listmonk-Docs mention the configuration might be handled in the env-file.
If someone might have an idea how Listmonk handles CORS-related issues on Cloudron, I would be very happy.
-
Error - Briefly unavailable for scheduled maintenance. Check back in a minute.Hi Joseph, thank you for your reply - autoupdates where enabled for plugins. Let me check if that solves the issue :).
-
Error - Briefly unavailable for scheduled maintenance. Check back in a minute.Hi there :),
I am getting a "Briefly unavailable for scheduled maintenance.[..]" regularily with the Managed Version. I tried to change that by allocating more ressources, but neither did that help nor seem ressources to be the problem according to the usage.
When checking the log, these requests seem to happen when the error occurs:
Apr 29 08:18:10 Executed the cron event 'wp_version_check' in 11.85s.
Apr 29 08:18:10 Success: Executed a total of 3 cron events.
Apr 29 08:18:20 - - - [29/Apr/2025:06:18:20 +0000] "GET /wp-includes/version.php HTTP/1.1" 403 292 "-" "Mozilla (CloudronHealth)"
Apr 29 08:18:30 - - - [29/Apr/2025:06:18:30 +0000] "GET /wp-includes/version.php HTTP/1.1" 403 292 "-" "Mozilla (CloudronHealth)"
Apr 29 08:18:40 - - - [29/Apr/2025:06:18:40 +0000] "GET /wp-includes/version.php HTTP/1.1" 403 292 "-" "Mozilla (CloudronHealth)"If someone has just a hint on what I could check next, I would be glad :).
-
PHPMailer - SMTP Error: Could not connect to SMTP host. STARTTLS command failed Unrecognized commandThank you Joseph - that helped a lot. Then, everything just works fine :).
-
PHPMailer - SMTP Error: Could not connect to SMTP host. STARTTLS command failed Unrecognized commandHi Joseph,
sorry for being unclear here - the mail is being send out if I set $mail->SMTPSecure = ''; like in the example mail at https://docs.cloudron.io/apps/lamp/#email. However, once setting it to $mail->SMTPSecure = 'tls'; I get the error above.
Will $mail->SMTPSecure = ''; use TLS anyways if the outbound relay is configured to do so?
-
PHPMailer - SMTP Error: Could not connect to SMTP host. STARTTLS command failed Unrecognized commandHi there,
I am trying to send a mail via SMTP and PHPMailer.
The script works fine unless I try to set SMTPSecure to tls. This causes_"SMTP Error: Could not connect to SMTP host. STARTTLS command failed Unrecognized command"
587 is set as port and the outbound relay is looking okay.If someone could point me in a good direction, I would be very thankful :).
Remaining arguments:
$mail = new PHPMailer(true);
$mail->isSMTP();
$mail->Host = getenv('CLOUDRON_MAIL_SMTP_SERVER');
$mail->SMTPAuth = true;
$mail->Username = getenv('CLOUDRON_MAIL_SMTP_USERNAME');
$mail->Password = getenv('CLOUDRON_MAIL_SMTP_PASSWORD');
$mail->SMTPSecure = '';
$mail->Port = getenv('CLOUDRON_MAIL_SMTP_PORT');$mail->setFrom(getenv('CLOUDRON_MAIL_FROM'), 'Mailer'); $mail->addReplyTo($email, 'Hello back'); $mail->addAddress('dummymail@dummy.com', 'Cloudron Test'); $mail->Subject = 'Hello World'; $mail->Body = json_encode($content, JSON_PRETTY_PRINT | JSON_UNESCAPED_UNICODE); $mail->CharSet = 'UTF-8'; $mail->Encoding = 'base64';