Trellis provisioning ansible server yml fails when root login not permitted

[fullyint]

@jordash

Many thanks for your highly detailed reply, I’ve seen similar lengthy and detailed replies on other topics and I commend you and the rest of the roots team for that.

Thanks for the thanks. It does take a lot of work.

@jordash

I think i’m just going to destroy and rebuild the droplet and start again and see how I get on as I was also having issues with the letsencrypt SSL implementation as playbook kept skipping it for some reason.

Sounds good. Rebuilding seems to be the most efficient option at this point, assuming your staging server can afford the downtime.

Off the top of my head, the only reason I can think of for why letsencrypt role would skip is if these two conditions were not met:

• SSL must be enabled: true
• SSL must be provider: letsencrypt

@jordash

1. i’m using db_import on the wordpress_sites.yml file, would the db import have any effect on the users role task, or on the letsencrypt task? I presumed not but want to cover all bases.

No effect that I can think of.

@jordash

2 . I’m right in thinking I do not need to pre-create admin_user on the server before provisioning? The user role takes care of this.

You are correct. You should not need to pre-create any user at all, assuming your VPS provider gives you at least one user with SSH access. This is commonly root (e.g., DO) or ubuntu (AWS). See this thread for discussion of the situation when the VPS provider does not make available an SSH user at VPS creation time.