Problems with Sage installation on macos

I’m running WP on my local MacOS using MAMP.
Have installed Bedrock and ran the WP installation, and all is running as expected - my website opening on localhost:3000.

The problem starts when I try to access the site after installed Sage. I am receiving Error occurred while trying to proxy: localhost:3000/ and I have no idea why I am getting this.
The moment I stop Sage, MAMP delivers the site. If I try to run Sage again, the error returns.

Just to make it clear, so I’ll won’t be doing some crazy mistake -

  1. I have installed Bedrock.
  2. Have installed Sage as a theme.
  3. Mamp is pointing to Bedrock’s folder, and website’s port is configured inside Sage’s bug.config.js
    Any idea what can I be missing?

Reading this thread, I am able to curl localhost:3000 (recieved perfect html output), but unable to curl the proxied URL example.test:

curl: (7) Failed to connect to example.test port 80 after 3 ms: Couldn't connect to server

ENV: npm: 9.8.1, node: v16.20.2/v18.17.1 (tried both versions).

Steps I did to figure out whats going wrong:

  • Have gave Full Disk Access to /sbin/nfsd (reference).
  • Have disabled MacOS firewall
  • Have tested to see if problem persists as well on theme’s dev-main branch
  • Tried switching between Nginx & Apache, on MAMP

BTW- I was looking at the package.json file, and I have seen that Sage appears, inside the devDependencies, as version 6.12.12. Its the latest version from the git repo. Is this means that I am using sage’s version 6? Doesn’t exist version 10?

Discovered the problem:

bug.config,js arrives with the follwing configuration:

    .watch(['resources/views', 'app']);

It is missing the port number on the proxied url


I’ll open a PR

This is generally more of an environment-specific thing.

While using Herd or Valet I have never had to specify a port in .setProxyUrl(). :confused:

I’d definitely check out Herd and DBngin if you’re on macOS and open to trying new things. They’re pretty nice compared to “environments” like MAMP in my experience.


I understand.

  1. Inside bud.js repo, it is written with port number:
  2. Thank you for the tips regarding the Dev Environments. Does HERD is made for running WP? I see its dedicated for Laravel.
    2.1 Found it -
  3. I thought on configuring WP alone, without using MAMP. Does HERD & Dbing really gives big advantages? Besides managing version of php & db?

It will work with pretty much everything out of the box with zero configuration, including Bedrock & Radicle.

No need for this guide, honestly.

Yes. It’s blazing fast, requires zero configuration, making a new site is as easy as just making a new folder in ~/Herd (or whatever directories you add) and immediately foldername.test is available, you can isolate PHP versions, everything is bleeding edge and fully up to date, everything is configured very nicely out of the box, sharing and securing is as easy as can be, etc.

I definitely don’t see any disadvantages.

1 Like

Hey @Log1x . Long time not seen.
Can you help me with a doubt I am having?
So again I am here, but now, running my project under HERD (without DBngin, since mysql is running on my mac with docker, and I already have DBeaver on my computer).
And I must say that running wp projects, is exactly like you said: as simple as creating a folder!

I have tried Trellis, and running VirtualBox on my computer. It made me think if trellis worth the trouble, cause:

  1. Finding an linux image for VM on Mac M1, is really hard. The one I have found perform slow and heavy. I ran VirtualBox and it got freezed and crushing, so ill give a try to VMware-fusion tomorrow, and hope it will out perform VB.
  2. Running my WP instalation inside HERD is so smooth, so I wonder why to search for alternatives. I get that Trellis provides lots of configurations, but still, the smoothness of working with herd, makes me think twice about giving up on it.

I have only used Trellis for deployment. Using it’s dev environment is optional.

I think it’s perfectly sane to stick with something native like Herd for WordPress development.

For deployment, you can use Trellis with pretty much any host/environment. The most common guide is the one for deploying to Kinsta but it really just comes down to swapping out the project roots, etc.

Another option is to use something like Envoyer for deployment. I recently wrote GitHub - Log1x/envoyer-deploy-commands: Simple deployment with Envoyer using Artisan which has been pretty nice to use so far (works with Acorn).

Thanks Brandon.
Taking advantage of this thread, does exist some manual that explains how to turn Sage into FSE?
I’m aware about sage10-fse, but it shows several known-issues, which make me wonder how much Sage is FSE compatible.
I walked through dozens of threads, speaking here about this subject, and

  1. I couldn’t find an explicit answer on how to activate FSE
  2. The docs speaks about Gutenberg, but it’s unclear, especially for a Sage newbie like me, what do do with the information over there.
  3. The only option i found that worked out, is to copy code from sage10-fse.

Is there a manual/tutorial/video that explain this matter in details, and you can provide me?

Thank you for all your help!

No idea. I have no interest in FSE at the moment.

1 Like

So sites that you are creating, are classic themes, with ACF & gutenburg editor?

Yeah, otherwise I’ve mainly been working with

Edit: I unlisted this thread since it has gotten off-topic and I don’t want to keep bumping it.