Skip to content

Letsencrypt should have ferm as a tag #1587

@zak-wearecore

Description

@zak-wearecore

Version

1.24.1

What did you expect to happen?

Adding an SSL to an previously provisioned environment should enable the site to be loaded on port 443 over HTTPS.

Running

trellis provision --tags letsencrypt {{env}}

Should also run the ferm role to update the firewall for HTTPS traffic

What actually happens?

The certificate is issued by the letsencrypt role but ferm is not run so the firewall is still blocking HTTPS traffic.

ERR_CONNECTION_REFUSED is received when loading the site in browser

Steps to reproduce

  1. Provision a new site with:
    ssl: enabled: false
  2. Observe the site running correctly on HTTP
  3. Update wordpress_sites.yml to
    `` ssl:
    enabled: true `
  4. Run trellis provision --tags letsencrypt {{env}}
  5. Observe the SSL being issued correctly
  6. Observe the connection refused error in browser

System info

Ubuntu 24.04

Log output

Please confirm this isn't a support request.

Yes

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions