Development / Master version and `enable_ssl.sh`

[BrendonKoz]

Overview of the Issue

After installing Screenly-OSE and rebooting, I then run the enable_ssl.sh script. It succeeds, and I reboot to make sure all changes are finalized, but upon attempting to access https://<screenly-ip_address> I am presented with an "Unable to connect" message in the browser. HTTP continues to work appropriately.

Reproduction Steps

Steps to reproduce this issue:

1. Install Raspberry Pi OS using Raspberry Pi Imager (OS build dated March 3, 2021)
2. Run apt update and apt upgrade, setting locale via raspi-config, then running apt full-upgrade [nothing to do] and reboot
3. Run bash <(curl -sL https://www.screenly.io/install-ose.sh) and choose the development version, don't manage network, allow full-upgrade.
4. Run ~/screenly/bin/enable_ssl.sh
5. Script completes successfully, but HTTPS does not connect. Error as mentioned above.

Environment

• Raspberry Pi Hardware Version: Pi 3B
• Raspberry Pi Network Setup: Ethernet with statically assigned IP via DHCP
• Screenly OSE Version: Not entirely sure where to find this to be honest...

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ealmonte32]

This is because the web server/nginx container was built without https and enable_ssl was mostly done for the production branch which is non-dockerized version.. if you want ssl you would need to modify the nginx config files for the nginx container prior to building the container..

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.