“All I did was run
trellis upwhat happened??”
A couple of recent upstream changes, to macOS Monterey’s nfs settings and GitHub’s public keys specifically, have broken older Trellis instances, causing previously working Trellis environments to break seemingly on their own. While we’ve corrected these issues in the latest versions of Trellis, trying to figure out which changes to back port into your specific project without breaking something else can be a challenge. In this post I hope to help you fix a few of the more common issues, and consolidate a known-good fixes for breaking Trellis changes.
This is not a thread to report new issues with Trellis.
A change in how macOS Monterey handles IP addresses locally broke some older Trellis projects. If your Trellis project hangs at:
==> default: Mounting NFS shared folders...
And eventually times out:
mount.nfs: Connection timed out
trellis/vagrant.default.yml find the following around line 2:
trellis/hosts/development find the following around line 38:
Also find the following around line 41:
Destroy your Trellis VM and re-create it:
# From your trellis directory vagrant destroy && trellis up