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

Vercel Deployment fails due to error loading php shared libraries #679

Closed
madaley1 opened this issue May 10, 2024 · 2 comments
Closed

Vercel Deployment fails due to error loading php shared libraries #679

madaley1 opened this issue May 10, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@madaley1
Copy link

Describe the bug
When deploying to vercel, after creating the repository and adding the token the build exits with an error

Logs:

Running build in Washington, D.C., USA (East) – iad1
--
09:05:53.768 | Cloning github.com/madaley1/github-readme-streak-stats (Branch: main, Commit: e7a7629)
09:05:54.298 | Previous build cache not available
09:05:54.518 | Cloning completed: 746.5ms
09:05:54.571 | Found .vercelignore
09:05:54.578 | Removed 1 ignored files defined in .vercelignore
09:05:55.019 | Running "vercel build"
09:05:55.984 | Vercel CLI 34.1.10
09:05:56.386 | > Installing Builder: [email protected]
09:06:01.188 | 🐘 Downloading user files
09:06:01.188 | 🐘 Downloading PHP runtime files
09:06:01.192 | 🐘 Installing Composer dependencies [START]
09:06:01.455 | php: error while loading shared libraries: libssl.so.10: cannot open shared object file: No such file or directory
09:06:01.469 | Error: Exited with 127
09:06:01.470 | at ChildProcess.<anonymous> (/vercel/path0/.vercel/builders/node_modules/vercel-php/dist/utils.js:182:24)
09:06:01.470 | at ChildProcess.emit (node:events:518:28)
09:06:01.470 | at ChildProcess.emit (node:domain:488:12)
09:06:01.471 | at ChildProcess._handle.onexit (node:internal/child_process:294:12)
09:06:01.493 | Error: Command "vercel build" exited with 1
09:06:01.577 | Command "vercel build" exited with 1

To Reproduce
Steps to reproduce the behavior:
Follow the steps provided for Vercel in the Deploying it on your own section of the Readme

Expected behavior
It should deploy and be able to be accessed via the vercel deployment url

Screenshots
image

Desktop (please complete the following information):

  • OS: Windows 11
  • Browser: Arc (Based on Chromium version 124.0.6367.60 (Official Build) (64-bit))

Additional context
I'm not sure if there are any steps that I missed, but I believe I did the process as outlined in the tutorial a couple times and it was the same result both times.

@madaley1 madaley1 added the bug Something isn't working label May 10, 2024
@Machine-Maker
Copy link

In the vercel project settings, change the node version to 18.x from the default of 20.x

@madaley1
Copy link
Author

This worked, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants