Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

https://packager.dev/avo-hq/ is down #3656

Closed
glaucocustodio opened this issue Feb 11, 2025 · 5 comments
Closed

https://packager.dev/avo-hq/ is down #3656

glaucocustodio opened this issue Feb 11, 2025 · 5 comments

Comments

@glaucocustodio
Copy link
Contributor

https://packager.dev/avo-hq/ is down, we are unable to deploy to production

@adrianthedev
Copy link
Collaborator

Please use www.packager.dev/avo-hq version for now until we fix the issues.

@michaelbaudino
Copy link

Same thing here (a TLS internal error, apprently):

❯ curl -vkI https://packager.dev
*   Trying 54.174.66.4:443...
* Connected to packager.dev (54.174.66.4) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Unknown (21):
* TLSv1.3 (IN), TLS alert, internal error (592):
* error:0A000438:SSL routines::tlsv1 alert internal error
* Closing connection 0
curl: (35) error:0A000438:SSL routines::tlsv1 alert internal error

Using the www subdomain works like a charm @adrianthedev, thanks 👌

@adrianthedev
Copy link
Collaborator

Yup. We're still investigating. It seems to be related with the Caddy Hatchbox config not goint through.

Sorry about this everyone...

@adrianthedev
Copy link
Collaborator

We should be good now.
It was Caddy and Hatchbox related.

I'll be back with a better post mortem

@adrianthedev
Copy link
Collaborator

Post mortem

At about 4:55pm UTC (11 Feb. 2025) Caddy tried to update the SSL certificate on our naked domain (https://packager.dev) and failed because of a bug that was happening in version 2.8.
At 5:01pm we responded that the www version of the domain was working and users switched to that to be able to deploy their apps.

We started investigating and we found the issue we submitted a ticket to Hatchbox to get some help.
They swiftly came to our help, updated Caddy and restarted the server.

At 5:11pm the server was up and running on both the naked domain and the www subdomain.

Total downtime for the gem server naked domain (https://packager.dev) was 16 minutes.
Time until the initial solution to deploy (use www.packager.dev) was 5 minutes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants