Hey! Hope you're doing well.

So, I finally got around to testing picoCMS—you know, that native macOS app for managing flat-file sites we talked about. I've been wanting to move a small blog off WordPress, and the idea of writing in Markdown with live preview and zero database sounded perfect.

Install was smooth—standard macOS app bundle, dragged to Applications, launched fine. The UI is clean: Finder-like sidebar for pages, dual-pane Markdown editor with live HTML preview. I created a new site from a blank template, wrote a quick test post, hit the "Local Server" button to preview… and got a browser window with "Unable to connect." The app showed "Server running" but nothing at localhost:8000.

The Wrong Turn I Took First

My first thought: "Maybe it's a port conflict." Checked if something else was using port 8000—nope. Tried changing the port in settings to 8080—same issue. Restarted the app, rebooted my Mac—still nothing. Spent 30 minutes convinced it was a bug in the local server feature.

The "Aha!" Moment

Then I remembered: macOS has gotten really strict about Local Network permissions, even for localhost servers. Went to System Settings > Privacy & Security > Local Network, scrolled down, and found picoCMS—toggle was off. Flicked it on, restarted the local server, and localhost:8000 loaded instantly.

I found this page with the system requirements that mentioned the network permission in the user comments: the resource I used. Saved me from giving up.

Quick Checklist

If picoCMS's local server won't connect:

  1. Open System Settings > Privacy & Security > Local Network
  2. Find picoCMS and enable the toggle
  3. Restart the local server—should work now

Apple's Local Network privacy guide explains why this happens. Once it's working, the app is fantastic—the live Markdown preview is buttery smooth. For publishing, Netlify integrates perfectly with the export feature.

Anyway, my WordPress-free site is finally live. Let me know if you try it!

Talk soon

Edit

Pub: 21 Feb 2026 10:57 UTC

Views: 13