Strapi stuck in deployment - No open HTTP ports detected

1

My web service was working usually when I upgraded to Strapi 4.19.1, and it’s sticking here:

==> Deploying...
==> Requesting node version ~18.17.1
==> Using Node version 18.17.1 via environment variable NODE_VERSION
==> Docs on specifying a Node version: https://render.com/docs/node-version
==> Running 'yarn start'
[2024-02-04 10:34:51.815] info: Using Local Image Sharp plugin
[2024-02-04 10:34:51.818] info: - Source directory: /opt/render/project/src/public
[2024-02-04 10:34:51.819] info: - Cache directory: /opt/render/project/src/.image-cache
==> No open HTTP ports detected
==> https://render.com/docs/web-services#host-and-port-configuration

Before it’s working.

Feb 4 05:54:31 AM[2024-02-04 10:54:31.215] info: - Source directory: /opt/render/project/src/public
Feb 4 05:54:31 AM[2024-02-04 10:54:31.215] info: - Cache directory: /opt/render/project/src/.image-cache
Feb 4 05:54:33 AM[2024-02-04 10:54:33.063] warn: Users-permissions registration has defaulted to accepting the following additional user fields during registration: sitemap_exclude
Feb 4 05:54:33 AM[2024-02-04 10:54:33.156] info: REST Cache provider "redis": connection established
Feb 4 05:54:33 AM[2024-02-04 10:54:33.164] info: Using REST Cache plugin with provider "redis"
Feb 4 05:54:34 AM
Feb 4 05:54:34 AM Project information
Feb 4 05:54:34 AM
Feb 4 05:54:34 AM┌────────────────────┬──────────────────────────────────────────────────┐
Feb 4 05:54:34 AM│ Time               │ Sun Feb 04 2024 10:54:34 GMT+0000 (Coordinated … │
Feb 4 05:54:34 AM│ Launched in        │ 5512 ms                                          │
Feb 4 05:54:34 AM│ Environment        │ production                                       │
Feb 4 05:54:34 AM│ Process PID        │ 84                                               │
Feb 4 05:54:34 AM│ Version            │ 4.19.0 (node v18.17.1)                           │
Feb 4 05:54:34 AM│ Edition            │ Community                                        │
Feb 4 05:54:34 AM│ Database           │ postgres                                         │
Feb 4 05:54:34 AM└────────────────────┴──────────────────────────────────────────────────┘
Feb 4 05:54:34 AM
Feb 4 05:54:34 AM Actions available
Feb 4 05:54:34 AM
Feb 4 05:54:34 AMWelcome back!

Locally, it is working usually with the same environment.

Is there any change in how to build the images in Render, which is causing this issue in the Node environment?

2

Hi all,

In this case, the issue was connecting to the 3rd party Redis service. Anything that happens on booting of the service that delays the web server binding to its ports can see this type of issue.

Regards,

Keith
Render Support, UTC+10 :australia:

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.