Trouble Setting Up SSH Forwarding, I think

[fullyint]

To clarify, regarding the steps of SSHing into the server and 1) trying a git clone and 2) removing keys from known_hosts on the server, the purpose was for debugging a problem, as was appropriate in the context above. These steps are not standard, not required for typical Trellis use.

To get your environment all set up for Trellis, and to discover how once your environment is set up, Trellis typically just works…

@fullyint

I’d suggest starting by getting a vanilla trellis working, with all default settings (but change admin_user). Then start adding customizations one at a time, testing as you go. Might sound obvious, but the getting started process – and potential debugging – seems unnecessarily difficult sometimes when people start right in with a lot of customizations.

@fullyint

see if you can get a vanilla trellis clone to work, making essentially no modifications other than your server IP and domain name. Compared to the long hard road of starting with a bunch of customizations and trying to get Trellis to work, it seems like a quick and easy road to get Trellis working with its defaults so that you know that your environment is ready and only then adding in customizations a piece at a time.

I’d be very surprised if the issues earlier in this thread were to appear on a fresh Trellis clone without modifications. Maybe just plug in your server IP in hosts/production and change the repo in wordpress_sites to

repo: [email protected]:roots/roots-example-project.com.git

for the sake of testing.