I recently added DevKinsta because I had a new project where I had to work with it (not one that I ever set up in LocalWP - totally separate site). The two do not at all seem to play nice as I can’t have both open at the same time. I also have to restart my computer after switching from one to the other.
Several months back I got a new Mac Mini and moved everything over from an old Apple Intel machine. Only today when I could not open MailPit for the first time ever did I see an error saying I should move to the Apple Silicon version.
Now on Apple Silicon, I get errors saying MailPit is not installed but will be next time I stop/start the site. I followed all the steps in other threads about deleting the MailPit folders and then start the site and see the folders being created again - all this happens but I still cannot open MailPit no matter what.
All sites say MailPit is missing, one randomly says there is a port conflict (although it still loads the local URL I am using just fine)
Opening AdminNeo works fine
I stop/start sites, quit LocalWP repeatedly, nothing ever seems to get MailPit to be recognized or open.
I recently added DevKinsta because I had a new project where I had to work with it (not one that I ever set up in LocalWP - totally separate site). The two do not at all seem to play nice as I can’t have both open at the same time.
This is normal, likely because both need the same port 80 to serve sites. You can’t have two apps using the same port, so you’ll have to use one or the other at once.
I also have to restart my computer after switching from one to the other.
This should not be required, at least for Local. You could try checking Activity Monitor for running servers such as nginx or apache after you quit both Local and DevKinsta, then kill those apps from Activity Monitor.
I’n not too concerned with DevKinsta + LocalWP (just wanted to give full context in case it mattered). My main concern is I currently can no longer use MailPit and it’s something I use a lot for developing/testing my plugins.
Yes, that is what I was explaining in my initial post that I have followed the steps to remove it and have it auto generated again. Clicking the button still does nothing. No error, no weirdness, just literally nothing at all.
I went through the steps again and now the MailPit folder is not being recreated anymore. I’m also getting errors saying “there is a port conflict” which I did not get just yesterday. The site still loads on their custom local URLs though so doesn’t actually seem to be a port conflict?
The port conflict sounds like you might have running services left over from previous Local launches. Mailpit failing to launch even after you’ve removed the old Mailpit files could be a versioning issue.
You can try this to fix both:
Quit Local.
Open Activity Monitor and quit any running nginx processes.
Take a backup of Local’s ~/Library/Application Support/Local/sites.json.
Update Local’s ~/Library/Application Support/Local/sites.json and make sure all Mailpit versions use 1.24.1 by finding and replacing any 1.12.1 values with 1.24.1, leaving this under each site:
In doing further testing, MailPit is not receiving any of the emails for any of my installs. If I add an Email Log plugin to the site they are being recorded there, but never seem to make it to MailPit.
Sorry to hear that, @sccr410. I can’t reproduce this with Local 9.2.6 so far (screenshot below), so it’s likely environment-specific.
Are you running any security or port filtering software (e.g. Little Snitch) that could affect running services?
If you create a new site, does Mailpit work there?
You’re welcome to share your latest logs after you fixed the versioning issue, as well as a screenshot or tree / ls output of your ~/Library/Application\ Support/Local/lightning-services/mailpit-1.24.1+0 directory.
Glad other sites are working after your reboot, and thanks for the screenshot and new logs, @sccr410. Your mailpit directory looks fine.
Have you tried changing that 10316 port in Local’s sites.json to another value? Local would normally automatically detect port conflicts and pick a new value for you, but it’s possible it’s not doing so for you here — from your logs it looks like you have another service running on the same port:
3791:{"class":"Process","level":"warn","message":"2025-08-18T16:05:36.427729Z 0 [System] [MY-010931] [Server] %%userDataPath%%/lightning-services/mysql-8.0.35+4/bin/darwin-arm64/bin/mysqld: ready for connections. Version: '8.0.35' socket: '%%site.runData%%/mysql/mysqld.sock' port: 10316 MySQL Community Server - GPL.","process":"mysql","thread":"main","timestamp":"2025-08-18T16:05:36.427Z"}
Also worth double-checking that your sites.json shows the new version of Mailpit for that site.
Little closer! I put in custom port numbers for this site (confirmed it is not being used by anything else) and now I can open MailPit! However, nothing is being received in there. I am also getting the “Port conflict” error at the top of the site in Local.
Sorry for the work this is causing you, @sccr410. Strange that Mailpit runs but you receive no mail, that suggests a problem with the php.ini config that routes mail to Mailpit.
At this point it would be worth trying to reimport the site as a new site. You can follow the steps here to try that, noting that you may need to give the site a new name when you drag the zip into Local:
