Burrows cert issue?
Visiting my burrow URL in Safari gives "This connection is not private". Chrome is fine. Did something change with the certificates?
Solved
Solved by rhea
We rotated the wildcard certificate this morning and one edge in ams kept the old chain for a few hours. It is fixed now — a hard refresh should clear it. Sorry about that.
Jump to post128 views · 1 like · 2 users
Related topics
- How is burrow RAM billed? Does it include the page cache?1 reply
- Rails 8 solid_queue on Larkhost: one pod or two?1 reply
- Agent connector for Burrows4 replies
- Burrow failed to start: storage not ready0 replies
- HTTP POST to a burrow URL does not wake a paused burrow (GET does)3 replies
- Node.js app memory climbs until OOM — only on Larkhost2 replies