After further scrutinizing your CLI output a bit, I see this:
wp_home: staging.ar-advies.nl
wp_siteurl: staging.ar-advies.nl/wp
Notice that the defaults include the http:// protocol, so try this instead:
wp_home: http://staging.ar-advies.nl
wp_siteurl: http://staging.ar-advies.nl/wp
Then (maybe destroy/rebuild droplet and) rerun server.yml and deploy.yml.
If the site still doesn’t load after that, you may want to compare your various customizations with the Trellis defaults, trying to catch customizations that might be problematic (like dropping the http:// protocol above).
If that still doesn’t work, my honest best recommendation is something I’ll quote from another thread: "…with all that you’ve learned…
…my next recommendation would be to 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 think if you make a fresh clone of the latest Trellis you’ll understand enough now to work through the setup steps in the README and have a successful provision and deploy.
One supporting argument for cloning the latest Trellis and working from its README and the Trellis docs are that they will be up to date. I skimmed over the setup tutorial you linked to and it looked pretty good but I noticed at least one item that was out-of-date related to ssh keys (github_ssh_keys was replaced with users 6 months ago ; more info in ssh-keys docs ).
1 Like