Open bgoosman opened 1 year ago
My web browser reports the surge.sh certificate, but surge certs
reports my letsencrypt certificate (R3)
Today, I'm getting the correct cert! Should I be expecting the process to take hours?
From what Broc said it may have been an issue with the certs not being applied to the edge nodes. My feeling here is that it was corrected (would default to support on that though)
My understanding is that this should be instant, as the SSL cert is installed on the server across all nodes, so it should work once applied.
My implementation is a bit different, in where I'm using the new 'encrypt' tag off the latest branch but it should be the same regardless.
surge@0.24.0-rc.12
is the best version to use when it comes to cert management.@sintaxi
Does the encrypt command have the same propagation time as manually doing it?
Thanks!
Thanks @sintaxi! I'd recommend writing #3 and #4 into the surge.sh docs. They make it sound like it should be instant. :)
@mster81 The encrypt command propagates the cert instantly.
That's awesome, thanks!
@sintaxi I was doing more testing on my account this AM and it looks like the same thing is happening, using latest RC, uploads fine but getting the same cert error.
Other question, what is the purpose of the 'preview-url' when doing a deploy? Just curios.
Thanks!
Discussed in https://github.com/sintaxi/surge/discussions/489
Now I'm running into the same thing with rehearsal.fun. Any help?