uploads.kosmos.chat nginx getting stuck #345

New Issue

raucao · 2021-10-21T14:43:31Z

raucao commented

2021-10-21 14:43:31 +00:00

Currently expired: https://uploads.kosmos.chat/791c7ed148e453f934ef56e1a4acb79a30845f0f/8SBtwY2eToAhPIaAy0IKaWUTNVH0oBwNh38k8crs/chilis.jpeg

raucao added the

bug

label 2021-10-21 14:43:31 +00:00

raucao commented

2021-10-22 09:22:09 +00:00

I just restarted nginx on uploads-1, and the new cert was immediately available. So it was renewed, but somehow not picked up by nginx.

There's no difference between most other Chef recipes using LE and this one.

There is definitely a certbot timer for renewal, and a deploy hook that should reload nginx. But I think last time the cert renewed, it also wasn't picked up by nginx.

I just restarted nginx on `uploads-1`, and the new cert was immediately available. So it was renewed, but somehow not picked up by nginx. There's no difference between most other Chef recipes using LE and this one. There is definitely a certbot timer for renewal, and a deploy hook that should reload nginx. But I think last time the cert renewed, it also wasn't picked up by nginx.

raucao added this to the Current operational issues project 2021-10-22 09:27:32 +00:00

raucao changed title from ~~TLS certificate not renewed automatically for uploads.kosmos.chat~~ to New TLS certificates not served immediately for uploads.kosmos.chat

2021-10-23 09:30:27 +00:00

raucao commented

2022-05-20 09:07:07 +00:00

I hadn't actually checked in depth last time, but nginx crashed after the renewal last night. Unfortunately without logging an error. But I suspect that this was the case before as well.

raucao commented

2022-10-21 12:24:38 +00:00

Closing this until it happens again.

raucao closed this issue

2022-10-21 12:24:43 +00:00

raucao changed title from ~~New TLS certificates not served immediately for uploads.kosmos.chat~~ to uploads.kosmos.chat nginx getting stuck

2023-01-17 06:52:22 +00:00

raucao commented

2023-01-17 06:53:20 +00:00

I think this has nothing to do with the renewal hook and rather with a bug in the Perl script we're using there.

Added an uptime robot monitor for it, so at least we can get notified when it happens.

I think this has nothing to do with the renewal hook and rather with a bug in the Perl script we're using there. Added an uptime robot monitor for it, so at least we can get notified when it happens.

Sign in to join this conversation.

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: kosmos/chef#345