[bug] adding additional altnames requires restart #44

New Issue

coolaj86 · 2020-04-25T18:14:52Z

coolaj86 commented

2020-04-25 18:14:52 +00:00

Problem

At first I had added a single domain to the cert:

npx greenlock add --subject 'example.com' --altnames 'example.com'

And later I ran this:

npx greenlock add --subject 'example.com' --altnames 'www.example.com'

I could see from the logs that a new certificate with both example.com and www.example.com what issued.

I expected that immediately, just by visiting www.example.com that the new certificate would refresh, but it did not.

Workaround

I didn't wait to see what would happen when the cache timeout occurred, though I suspect that may have resolved the issue.

Instead I restarted the service.

## Problem At first I had added a single domain to the cert: ```bash npx greenlock add --subject 'example.com' --altnames 'example.com' ``` And later I ran this: ```bash npx greenlock add --subject 'example.com' --altnames 'www.example.com' ``` I could see from the logs that a new certificate with both `example.com` and `www.example.com` what issued. I expected that immediately, just by visiting `www.example.com` that the new certificate would refresh, but it did not. ## Workaround I didn't wait to see what would happen when the cache timeout occurred, though I suspect that may have resolved the issue. Instead I restarted the service.

Sign in to join this conversation.

No Label

No Milestone

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: root/greenlock-express.js#44