Error: CERT_HAS_EXPIRED, after deploying to Heroku.

[zivkovicj]

I forked this project, as described in the project instructions, then deployed. When trying to view the project, my logs show this:

2022-06-21T22:14:07.800542+00:00 app[web.1]:     at TLSSocket.emit (node:events:527:28)
2022-06-21T22:14:07.800542+00:00 app[web.1]:     at emitErrorNT (node:internal/streams/destroy:157:8)
2022-06-21T22:14:07.800543+00:00 app[web.1]:     at emitErrorCloseNT (node:internal/streams/destroy:122:3)
2022-06-21T22:14:07.800543+00:00 app[web.1]:     at processTicksAndRejections (node:internal/process/task_queues:83:21) {
2022-06-21T22:14:07.800544+00:00 app[web.1]:   type: 'system',
2022-06-21T22:14:07.800544+00:00 app[web.1]:   errno: 'CERT_HAS_EXPIRED',
2022-06-21T22:14:07.800544+00:00 app[web.1]:   code: 'CERT_HAS_EXPIRED'
2022-06-21T22:14:07.800545+00:00 app[web.1]: }
2022-06-21T22:14:37.707715+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/" host=deploying-backend-project.herokuapp.com request_id=4029c381-4c5b-42ec-8553-87ee2d576359 fwd="97.117.72.47" dyno=web.1 connect=0ms service=30001ms status=503 bytes=0 protocol=https
2022-06-21T22:14:38.107888+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=deploying-backend-project.herokuapp.com request_id=c19c3355-83f6-4416-9cb7-e238232578e2 fwd="97.117.72.47" dyno=web.1 connect=0ms service=3ms status=404 bytes=394 protocol=https

[aliktb]

I had the same issue. Appears to be an expired SSL certificate with the bored API. This can be 'fixed' by reverting back to http in the fetch request in app.js