MailerPress

[patrickvanelk]

Hi,

When using MailerPress on a site, I get a lot of 502 errors / "WordPress environment not running". I also tried it with a fresh site with only MailerPress and MailerPress Pro, created a list and tag, created a new page with a MailerPress form and set the list and tag. Is this a setting or bug in SpawnWP or am I doing something wrong?

Bye, Patrick

[tts-empire]

Hi Patrick,

Thanks again for the detailed report — it led us to three real bugs at once:

1. The edge proxy in front of every site had no explicit timeout and fell back to nginx's 60s default, well under PHP's own execution limit — so any request that ran long (like MailerPress sending mail) got cut off and showed as "WordPress environment is not running," even though WordPress was still working underneath.
2. WP-Cron was force-disabled on every site with no substitute trigger, so scheduled/queued sends had nothing to fire them.
3. Outgoing mail was only routed to Mailpit on the Development blueprint, not the others.

All three are fixed as of SpawnWP 0.5.28. If you're on an existing site, run spawnwp update (or update from the cockpit) — the fix applies to already-running sites automatically, not just new ones.

Could you update and let us know if MailerPress behaves correctly now? If you still see the 502 / "environment not running" message afterward, please reopen with the exact steps (which mail action triggers it, list/tag size, etc.) and we'll dig further.

[patrickvanelk]

Thank you for the fast response! Unfortunately, it didn't help for my situation. But I think I know what the problem is: MailerPress assumes the WordPress install is not in a subfolder. I see links like /wp-admin/admin.php?page=mailerpress%2Fcampaigns.php&path=%2Fhome%2Fsettings&activeView=licence instead of /website/wp-admin/admin.php?page=mailerpress%2Fcampaigns.php&path=%2Fhome%2Fsettings&activeView=licence.

So, this is probably something you can't fix/work around; I will report this bug to MailerPress.

Thanks again, I appreciate the quick follow-up!

[tts-empire]

Hi Patrick,

Thank you — you were right, and the exact URL you shared let us pinpoint the problem. We inspected the public MailerPress 2.0.6 package. The License destination is hardcoded twice in build/dist/js/mail-editor.js as:

/wp-admin/admin.php?page=mailerpress%2Fcampaigns.php&path=%2Fhome%2Fsettings&activeView=licence

MailerPress already exposes a path-aware adminUrl to its JavaScript, populated from WordPress with admin_url('admin.php'), and uses that value elsewhere. These two links bypass it. On a SpawnWP site they therefore drop the /<site>/ prefix and send the request to the domain root, which explains the 502 / “WordPress environment is not running” response.

Exact source references:

• the compiled file containing the two hardcoded License links
• the PHP source that already provides adminUrl via admin_url('admin.php') (line 117)

So reporting this upstream is the right solution. Replacing those root-relative URLs with the localized adminUrl should make the links work on WordPress installations hosted below a path. SpawnWP cannot safely rewrite every arbitrary root-relative URL globally because multiple independent sites share the same host and such rewriting would be ambiguous.

A correction on our side: the 0.5.28 proxy-timeout, WP-Cron, and Mailpit changes fixed three real independent issues, but they were not the primary cause of this specific navigation failure. Our previous reply was too definitive. Thank you for testing it and returning with the decisive URL.

We have also added a compatibility note to the documentation: https://spawnwp.com/docs/troubleshooting/#a-plugin-link-loses-the-site-prefix

If MailerPress sends you a patch or test version, we will be happy to verify it as well. Please let us know how it goes.