mirror of
https://github.com/requarks/wiki.git
synced 2026-03-02 22:06:55 -05:00
SSL certificate expiry dates do not match #2425
Labels
No labels
BETA
BETA
accessibility
backlog
bug
can't replicate
contrib-easy
contrib-hard
contrib-medium
deferred
documentation
duplicate
duplicate
editors
enhancement
invalid
localization
migrate
ui
under review
v3
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/wiki-requarks#2425
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ravenzachary on GitHub (Jan 22, 2021).
Originally assigned to: @NGPixel on GitHub.
Describe the bug
If you look at the certificate expiration date on the Let's Encrypt SSL Certificate in the browser and then compare that the certificate expiration date in the Admin > SSL section of the Wiki, the dates do not match. Currently, the Admin panel is showing an expiration date of 29 January 2021 and the browser cert details lists 22 April 20201.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The SSL certificate expiration date should be the same.
Screenshots
Host Info (please complete the following information):
Additional context
Add any other context about the problem here.
@cashewnuts commented on GitHub (Jan 29, 2021):
This problem causes using up the rate limit of Let's encrypt.
If I switch wiki.js server on and off on daily basis, it will end up the error 5 days later.
https://letsencrypt.org/docs/rate-limits/
@PaulKlumpp commented on GitHub (Feb 23, 2021):
I experience the same problem. It will try to update the cert far too often.
@JetForMe commented on GitHub (May 16, 2021):
Came here to post the same screenshot :)
@dazzag24 commented on GitHub (Jun 7, 2021):
Same behavior here. Just upgraded to wiki.js version 2.5.201 and I still see the issue.
@rogersgt commented on GitHub (Sep 23, 2021):
@NGPixel Is there any update on this? My company's wiki site is completely down due to this, I believe. The error logs are spitting out the
letsencryptthrottling error. The strange part is I haven't tried to restart the server until it was unreachable (after the throttling limit was reached). Is there at least a workaround for this?What I believe is happening...
I have the following settings enabled:
The server worked really well for a month, and then this. I'm unable to reach the UI via HTTP or HTTPS. I can access the database, but I'm not really sure what I should be trying to do in order to reset/get around this. Any help would be appreciated ✊
@NGPixel commented on GitHub (Sep 23, 2021):
@rogersgt A simple restart of Wiki.js will trigger a certificate renewal. However it seems you exceeded the API limit so that won't work. I suggest disabling HTTPS for now (see https://docs.requarks.io/troubleshooting#how-to-manually-disable-https-ssl-redirection) and consider using a reverse proxy like Cloudflare or put an nginx instance in front.
@biji commented on GitHub (Oct 24, 2021):
for temporary solution, you can edit
letsencrypt.payload.expiresin tablesettings@snarum commented on GitHub (Nov 17, 2021):
Doen anyone know when the certificate is actually attempted renewed? to me it looks like the code is either run when the server is started, or when the Renew button is clicked in the gui. But I can't find any code that would run the certificate check regularly.
Right now my SSL page says the certificate is expired yesterday, and letsdebug.org says there is no renewal requests.
@NGPixel commented on GitHub (Nov 18, 2021):
@snarum That's correct. There's no automatic renewal at the moment and yes, it needs to be added.
@jonystorm commented on GitHub (Feb 17, 2022):
Hi all! I have a problem directly related to this one, I'm using versión 2.5.275, and got the email from let's encrypt my current cert only has a few days left, I have the "Renew certificate" button on the SSL admin section but the request triggered from clicking it returns an error of "Empty response", any suggestions? or anyone else having this issue?
@scott-dunt commented on GitHub (Feb 17, 2022):
Suggest you restart your docker containers.. I hit that error before and restarting the containers cleared it up.
@FiretronP75 commented on GitHub (Aug 29, 2023):
I confirm this is still a problem. For me it seems to be showing the issued date rather than the expiration date.
@charlezkwan commented on GitHub (Nov 13, 2023):
@NGPixel , any update on automatic renewal certificate feature?
@miller-coffee commented on GitHub (Jan 25, 2024):
I can confirm this is still a problem with Wiki.js 2.5.300
@integrity-develop commented on GitHub (Mar 1, 2024):
I can confirm this issue is still present in Wiki.js 2.5.301. Will this issue cause SSL requests to begin failing when the displayed date has passed? This is the first SSL I have issued for my Wiki.js deployment and I can't quite tell if this is just an issue with what is displayed in the interface or if it is an actual configuration problem that is going to manifest as failed requests. The newly issued SSL certificates display as fine in a browser. Appreciate any information someone can give me on this, and will be investigating nginx implementation in the meantime.