certificate job fails #15

New Issue

Open

opened 2023-04-13 14:33:38 +00:00 by kiara · 1 comment

kiara commented

2023-04-13 14:33:38 +00:00

Owner

right now our certificate job presumes no running servers are bound to port 80, which is not realistic.
for e.g. server vergadering.bij1.net, i got the script to run having disabled ingang (sudo systemctl start ingang), greenlight (sudo docker stop ...), and nginx (sudo systemctl stop nginx).
that might have been more than needed, but we may need to change something to make our cron job for this actually reliable as well for various servers.

right now our certificate job presumes no running servers are bound to port 80, which is not realistic. for e.g. server `vergadering.bij1.net`, i got the script to run having disabled ingang (`sudo systemctl start ingang`), greenlight (`sudo docker stop ` ...), and nginx (`sudo systemctl stop nginx`). that might have been more than needed, but we may need to change something to make our cron job for this actually reliable as well for various servers.

kiara commented

2023-10-10 09:52:51 +00:00

Author

Owner

CRM:

sudo systemctl stop nginx
sudo certbot renew --standalone
sudo systemctl start nginx

had ansible sudo rechten tho?

CRM: ```sh sudo systemctl stop nginx sudo certbot renew --standalone sudo systemctl start nginx ``` had ansible sudo rechten tho?

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: bij1/infra#15

No description provided.