You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Polyscope breaks herd nginx file when generating a workspace #182
All of herds .test domains refused to connect after opening polyscope for the first time and assigning it to a Sites/Repo on my mac. claude helped me track the root cause to a malformed vhost written by polyscope.
1 server {
2 listen 127.0.0.1:80;
3 #listen 127.0.0.1:80; # valet loopback
4 server_name silver-lobster.test www.silver-lobster.test *.silver-lobster.test;
5 return 301 httpspasted10:36 AMClaude responded: Confirmed — line 27 rewrite ^ "" last; (and line 70).Identified broken placeholder configuration and prescribed remedial stepsIdentified broken placeholder configuration and prescribed remedial stepsConfirmed — line 27 rewrite ^ "" last; (and line 70). nginx 1.25.4 rejects the empty "" replacement, and that's fatal for the whole config. This whole file is a Polyscope placeholder vhost — root /, fastcgi_index "", SCRIPT_FILENAME "", the blank rewrite — it's a skeleton for a workspace that never got a real document root wired in. Broken as written, and it's been taking all of Herd down with it.
I fixed it by removing the file
mv ~/Library/Application\ Support/Herd/config/valet/Nginx/silver-lobster.test
However that gets herd working but not polyscope. I'm unsure why its causing a malformed vhost?
It's a bit tricky to find the source of this; I suspect you did not allow Polyscope to control Herd when macOS asked you to?
You can reset that permission by running tccutil reset AppleEvents com.getpolyscope.app, restarting Polyscope and creating a workspace that runs herd secure in the setup script. That should retrigger the permission.
If that's the source of that issue, I'll see we ask for that permission at a better point than during the background process.
Activity
mechelon commentedon Aug 6, 2026
It's a bit tricky to find the source of this; I suspect you did not allow Polyscope to control Herd when macOS asked you to?
You can reset that permission by running
tccutil reset AppleEvents com.getpolyscope.app, restarting Polyscope and creating a workspace that runsherd securein the setup script. That should retrigger the permission.If that's the source of that issue, I'll see we ask for that permission at a better point than during the background process.