Configuration Adjustments for Resolving Apache2 and Let's Encrypt Integration Issue in SaltStack

[Shafiya-Heena]

Issue Description

During the process of provisioning a chapters stage server using the Salt master, we encountered an issue related to the startup of the Apache2 service. This issue stemmed from the absence of Let's Encrypt configuration for HTTPS (port 443), resulting in the failure to initiate the Apache2 service.

---

      ID: apache2 service
Function: service.running
  Result: False
 Comment: Job for apache2.service failed because the control process exited with error code.
          See "systemctl status apache2.service" and "journalctl -xe" for details.
 Started: 15:52:41.608590
Duration: 230.483 ms
 Changes:

---

Recommendations:

To address the encountered issue, the propose steps for modification in the Salt configuration file:

• Ensure that Apache2 starts with HTTP (port 80) by adjusting the configuration settings appropriately
  • config file /etc/apache2/sites-available/creativecommons.net_http.conf
• Execute the Let's Encrypt state by applying the configuration from /etc/letsencrypt/domainsets.yaml
• Subsequently, configure HTTPS (port 443) to enable the secure connection
  • config file /etc/apache2/sites-available/creativecommons.net_https.conf

Implementing these adjustments should help resolve the startup issue and establish a functional Apache2 service with the necessary Let's Encrypt configuration.

Related Links

• creativecommons/sre-salt-prime: docs/Orchestration.md