Forestadmin server suddenly no longer works - SSL error

Help me!
1

Hi team,

We currently have an issue with your server: app.forestadmin.com

 curl -vI https://app.forestadmin.com
*   Trying 99.83.183.127:443...
* Connected to app.forestadmin.com (99.83.183.127) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /usr/ssl/certs/ca-bundle.crt
*  CApath: none
* TLSv1.3 (IN), TLS alert, unrecognized name (624):
* OpenSSL/3.1.4: error:0A000458:SSL routines::tlsv1 unrecognized name
* Closing connection
curl: (35) OpenSSL/3.1.4: error:0A000458:SSL routines::tlsv1 unrecognized name

It happened today around 17h55 Paris time.

Could you please confirm if this comes from your side or not?

Thanks in advance
Best regards
Louis-Marie

2

Hello Louis-Marie, sorry for the inconvenience!
Our tech team is on it. Our hosting provider is encountering an issue and we’re currently looking for a workaround. https://status.heroku.com/

We’ll let you know here any advances made by our team.

3

Come on Guys, this is not the first time we experience big problems due to your upstream provider Heroku.

You should take actions about this very soon.

Regards,
Matteo

4

We are being impacted by the same issue. Totally unable to access our space in Forest.

5

Do we have any idea of timing? as this is right during the middle of the day getting as much visibility as to whats happening and what the time is doing would be great.

6

Hi all,

We should be back up and running after re-deploying our frontend app.
You can find the latest update on our status page: https://status.forestadmin.com/

Please let us know if you encounter any further issues.

Apologies for the inconvenience :folded_hands:

7

No need for apologies for this inconvenience. But now you need to think carefully about how to prevent similar incidents in the future. This is not the first time Heroku creates long downtimes to Forest Admin and to the business on our side.

So please follow up with with the actions you are going to take.

Thank you.

8

This incident confirmed what we had already begun to notice: Heroku is no longer a reliable infrastructure provider for our needs.
As a result, we are currently migrating our infrastructure to AWS to ensure greater reliability, scalability, and long-term resilience.
We will be rolling out this migration progressively over the coming weeks and will share more details as we go. In the meantime, please rest assured that maintaining the stability of our platform remains our top priority.

2 Likes