try.gitea.io certificate expired #10667

Closed
opened 2025-11-02 09:14:53 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @ianw on GitHub (Apr 17, 2023).

Description

Hello,

In trying to replicate something for another bug report, I found the certificate for try.gitea.io expired on Sun, 16 Apr 2023 09:23:44 GMT. It's now 17 Apr 01:29 GMT so I'm guessing if there is an automatic renewal it might have gone wrong.

Gitea Version

1.19.1

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Upstream site

Database

None

Originally created by @ianw on GitHub (Apr 17, 2023). ### Description Hello, In trying to replicate something for another bug report, I found the certificate for try.gitea.io expired on Sun, 16 Apr 2023 09:23:44 GMT. It's now 17 Apr 01:29 GMT so I'm guessing if there is an automatic renewal it might have gone wrong. ### Gitea Version 1.19.1 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Upstream site ### Database None
GiteaMirror added the type/bug label 2025-11-02 09:14:53 -06:00
Author
Owner

@techknowlogick commented on GitHub (Apr 17, 2023):

Thanks, I've renewed it and we're now using caddy on that server so it doesn't happen again :)

@techknowlogick commented on GitHub (Apr 17, 2023): Thanks, I've renewed it and we're now using caddy on that server so it doesn't happen again :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#10667