I’m setting up a new 3.x server on self-hosted AWS; I’m able to successfully start docker. However, when I create a ssl using certbot, after I change the nginx.conf file to point to the new .pem files, nothing works (like it normally does in our other running instance).
Package 'horticulturalist':
Service 'horticulturalist':
Status: Up
Up: 2832 seconds, Restarts: 0
Attributes: watched, running, expected
Service PID: 360, Supervisor PID: 344
Package 'medic-api':
Service 'medic-api':
Status: Up
Up: 2832 seconds, Restarts: 0
Attributes: watched, running, expected
Service PID: 405, Supervisor PID: 387
Package 'medic-core':
Service 'couchdb':
Status: Up
Up: 2832 seconds, Restarts: 0
Attributes: watched, running, expected
Service PID: 435, Supervisor PID: 426
Service 'nginx':
Status: Failure
Up: 72008 seconds, Restarts: 0
Attributes: watched, expected
Service PID: None, Supervisor PID: 405
Service 'openssh':
Status: Up
Up: 2832 seconds, Restarts: 0
Attributes: watched, running, expected
Service PID: 542, Supervisor PID: 527
If I try to restart nginx it doesn’t work.
root@ip-10-2-3-212:/home/ubuntu# docker exec -it medic-os /boot/svc-restart medic-core nginx
Warning: Service 'medic-core/nginx' is not currently running
Fatal: Failed to restart service 'medic-core/nginx'
All I did was try to get the new ssl certs from certbot, and then update the nginx.conf file to point to the new .pem files and not the default ones; but now it won’t even connect at all; and the connection is still not secure.