Missing Mailpit v1.12 on Silicon M3 MacBook Air

Support
1

What issue or error are you experiencing?

When I select my site from the left menu, a red title bar appears which reads:

Missing Mailpit v1.12. Don't worry. We'll reinstall it next time you start your site.

But it never does. Each time I restart Local, and select any site, I receive that message.

The site still runs, but the error is annoying and I’m concerned it could mask a more serious issue should one arise.

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

  1. Start Local
  2. Click a site in the left menu
  3. See message

image
image879×233 22.7 KB

System Details

  • Local Version: Version 9.2.7+6877

  • Operating System (OS) and OS version: Apple M3 Silicon, 15.6.1 (24G90)

Local Logs

local-logs.zip (954.8 KB)

Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

2

Note that I’ve attempted to manually delete mailpit directories from /Users/amatthews/Library/Application Support/Local/lightning-services as directed in other tickets. After deleting everything beginning with mailpit (rm -rf mailpit*) Local successfully downloads mailpit-1.24.1+0, but not mailpit-1.12.x+x.

3

Thanks for this report, @commadelimited.

For your Mailpit 1.12 sites, you could try following this advice to update them to 1.24 for now:

https://community.localwp.com/t/cant-open-mailpit/51177/7

4

If it makes a difference, I don’t send mail from any of my local sites. Is there a way I can just turn turn this feature off?

5

@commadelimited Not at the moment, as Mailpit is still catching general transactional email (new site info, new user info etc.) even if you don’t actively send mail.

6

Great. The steps you listed in the linked thread did the trick. Thank you @nickc!

2 Likes