New Customer: Build failed on an app running fine elsewhere - no error messages

[eltel]

Hi!

So, I’ve heard great things about Render, I thought I’d try you out - I deployed my app that’s running fine on Heroku to test things out and it’s failing every time with zero error messages.

Here are the logs:

Aug 10 11:01:35 AM  ==> Cloning from https://github.com/eltel/mern-social-tl5...
Aug 10 11:01:36 AM  ==> Checking out commit 1d5db1e45a8a5979cc7145b3806a340955147183 in branch main
Aug 10 11:01:38 AM  ==> Downloading cache...
Aug 10 11:01:45 AM  ==> Still downloading cache...
Aug 10 11:01:51 AM  ==> Running build command 'yarn'...
Aug 10 11:01:51 AM  yarn install v1.22.5
Aug 10 11:01:51 AM  [1/4] Resolving packages...
Aug 10 11:01:52 AM  [2/4] Fetching packages...
Aug 10 11:02:16 AM  info @next/swc-android-arm-eabi@12.2.3: The platform "linux" is incompatible with this module.
Aug 10 11:02:16 AM  info "@next/swc-android-arm-eabi@12.2.3" is an optional dependency and failed compatibility check. Excluding it from installation.
Aug 10 11:02:16 AM  info @next/swc-android-arm-eabi@12.2.3: The CPU architecture "x64" is incompatible with this module.
Aug 10 11:02:16 AM  info @next/swc-android-arm64@12.2.3: The platform "linux" is incompatible with this module.
Aug 10 11:02:16 AM  info "@next/swc-android-arm64@12.2.3" is an optional dependency and failed compatibility check. Excluding it from installation.
Aug 10 11:02:16 AM  info @next/swc-android-arm64@12.2.3: The CPU architecture "x64" is incompatible with this module.
Aug 10 11:02:16 AM  info @next/swc-darwin-arm64@12.2.3: The platform "linux" is incompatible with this module.
Aug 10 11:02:16 AM  info "@next/swc-darwin-arm64@12.2.3" is an optional dependency and failed compatibility check. Excluding it from installation.
Aug 10 11:02:16 AM  info @next/swc-darwin-arm64@12.2.3: The CPU architecture "x64" is incompatible with this module.
Aug 10 11:02:16 AM  info @next/swc-darwin-x64@12.2.3: The platform "linux" is incompatible with this module.
Aug 10 11:02:16 AM  info "@next/swc-darwin-x64@12.2.3" is an optional dependency and failed compatibility check. Excluding it from installation.
Aug 10 11:02:16 AM  info @next/swc-freebsd-x64@12.2.3: The platform "linux" is incompatible with this module.
Aug 10 11:02:16 AM  info "@next/swc-freebsd-x64@12.2.3" is an optional dependency and failed compatibility check. Excluding it from installation.
Aug 10 11:02:16 AM  info @next/swc-linux-arm-gnueabihf@12.2.3: The CPU architecture "x64" is incompatible with this module.
Aug 10 11:02:16 AM  info "@next/swc-linux-arm-gnueabihf@12.2.3" is an optional dependency and failed compatibility check. Excluding it from installation.
Aug 10 11:02:16 AM  info @next/swc-linux-arm64-gnu@12.2.3: The CPU architecture "x64" is incompatible with this module.
Aug 10 11:02:16 AM  info "@next/swc-linux-arm64-gnu@12.2.3" is an optional dependency and failed compatibility check. Excluding it from installation.
Aug 10 11:02:16 AM  info @next/swc-linux-arm64-musl@12.2.3: The CPU architecture "x64" is incompatible with this module.
Aug 10 11:02:16 AM  info "@next/swc-linux-arm64-musl@12.2.3" is an optional dependency and failed compatibility check. Excluding it from installation.
Aug 10 11:02:16 AM  info @next/swc-win32-arm64-msvc@12.2.3: The platform "linux" is incompatible with this module.
Aug 10 11:02:16 AM  info "@next/swc-win32-arm64-msvc@12.2.3" is an optional dependency and failed compatibility check. Excluding it from installation.
Aug 10 11:02:16 AM  info @next/swc-win32-arm64-msvc@12.2.3: The CPU architecture "x64" is incompatible with this module.
Aug 10 11:02:16 AM  info @next/swc-win32-ia32-msvc@12.2.3: The platform "linux" is incompatible with this module.
Aug 10 11:02:16 AM  info "@next/swc-win32-ia32-msvc@12.2.3" is an optional dependency and failed compatibility check. Excluding it from installation.
Aug 10 11:02:16 AM  info @next/swc-win32-ia32-msvc@12.2.3: The CPU architecture "x64" is incompatible with this module.
Aug 10 11:02:16 AM  info @next/swc-win32-x64-msvc@12.2.3: The platform "linux" is incompatible with this module.
Aug 10 11:02:16 AM  info "@next/swc-win32-x64-msvc@12.2.3" is an optional dependency and failed compatibility check. Excluding it from installation.
Aug 10 11:02:16 AM  [3/4] Linking dependencies...
Aug 10 11:02:22 AM  [4/4] Building fresh packages...
Aug 10 11:02:23 AM  Done in 31.50s.
Aug 10 11:02:23 AM  ==> Generating container image from build. This may take a few minutes...
Aug 10 11:04:20 AM  ==> Uploading build...
Aug 10 11:04:58 AM  ==> Build uploaded in 26s
Aug 10 11:04:58 AM  ==> Build successful 🎉
Aug 10 11:04:58 AM  ==> Deploying...
Aug 10 11:05:16 AM  ==> Starting service with 'yarn start'
Aug 10 11:05:18 AM  yarn run v1.22.5
Aug 10 11:05:19 AM  $ NODE_ENV=production node server.js
Aug 10 11:05:29 AM  Mongodb connected

There’s no point attaching the URL because it appears to trigger Spam filters on here but I think this is the deploy code:
dep-cbprkf02i3mhlklhgkvg

Any tips greatly appreciated.

Thanks in advance

Terry

[al_ps]

Hi Terry,

Thanks for reaching out.

Could you double-check that the webserver is using host 0.0.0.0 and binding to the PORT env var (which defaults to 10000).

Thanks

Alan

[eltel]

Hi Alan!

Thanks so much for the quick reply. I can confirm that the server’s using the PORT var - the host is consoling out at address: ‘::’ - which, according to what you’ve said, is clearly wrong - I’ve never in my life had to configure the host (and I’m not exactly a noob and have hosted dozens of sites/apps on Heroku/Vercel), how would I go about doing that?

Thanks again

Terry

[eltel]

Anyone? I, apparently, really need some tips on how to configure the host for the webserver, or at least where to look.

Thanks

Terry

[anurag]

Hello! Your server was indeed listening on the right interfaces. The issue was with the build command – It wasn’t building the artifacts needed to launch the server. We could’ve detected it automatically; our suggested command was ‘yarn’. We updated your service to change the build command from yarn to yarn; yarn build, and the service is now live. You can edit the build command yourself under Service Settings.

[eltel]

Thanks so much! That did the trick