Skip to content
This repository was archived by the owner on Oct 24, 2021. It is now read-only.

Commit da21b59

Browse files
Update source/expired-certificate.md
Co-authored-by: Filipe Névola <filipe@meteor.com>
1 parent af33e41 commit da21b59

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

source/expired-certificate.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ If your server is accessing external let’s encrypt resources with an old Meteo
4141

4242
As stated before, Galaxy issues Let's Encrypt certificates automatically for all clients. This is source of confusion, as if you are depending on older clients being able to access your website, this won't work.
4343

44-
If Let's encrypt certificates are not good for your clients you would need to acquire other certificate from a different provide and upload your custom certificate into Galaxy.
44+
If Let's encrypt certificates are not good for your clients you would need to acquire other certificate from a different provider and upload your custom certificate into Galaxy.
4545

4646
You can also generate a Let's Encrypt certificate manually and upload to Galaxy, but specifying an alternative preferred chain on certbot:
4747

0 commit comments

Comments
 (0)