Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

deicool's avatar

Error when running pingcrm

Hello

I am trying to run the example "https://github.com/inertiajs/pingcrm"

When I execute the command "composer install", I am getting the below errors

Error

Composer is operating significantly slower than normal because you do not have the PHP curl extension enabled. Loading composer repositories with package information Updating dependencies Your requirements could not be resolved to an installable set of packages.

Problem 1 - tijsverkoyen/css-to-inline-styles 2.2.2 requires php ^5.5 || ^7.0 -> your php version (8.0.24) does not satisfy that requirement. - tijsverkoyen/css-to-inline-styles[2.2.3, ..., 2.2.x-dev] require ext-dom * -> it is missing from your system. Install or enable PHP's dom extension. - inertiajs/inertia-laravel[v0.5.3, ..., v0.5.4] require laravel/framework ^6.0|^7.0|^8.74|^9.0 -> satisfiable by laravel/framework[v8.74.0, ..., 8.x-dev]. - laravel/framework[v8.74.0, ..., 8.x-dev] require tijsverkoyen/css-to-inline-styles ^2.2.2 -> satisfiable by tijsverkoyen/css-to-inline-styles[2.2.2, ..., 2.2.x-dev]. - Root composer.json requires inertiajs/inertia-laravel ^0.5.3 -> satisfiable by inertiajs/inertia-laravel[v0.5.3, v0.5.4].

To enable extensions, verify that they are enabled in your .ini files: - /etc/php/8.0/cli/php.ini - /etc/php/8.0/cli/conf.d/10-opcache.ini - /etc/php/8.0/cli/conf.d/10-pdo.ini - /etc/php/8.0/cli/conf.d/20-calendar.ini - /etc/php/8.0/cli/conf.d/20-ctype.ini - /etc/php/8.0/cli/conf.d/20-exif.ini - /etc/php/8.0/cli/conf.d/20-ffi.ini - /etc/php/8.0/cli/conf.d/20-fileinfo.ini - /etc/php/8.0/cli/conf.d/20-ftp.ini - /etc/php/8.0/cli/conf.d/20-gd.ini - /etc/php/8.0/cli/conf.d/20-gettext.ini - /etc/php/8.0/cli/conf.d/20-iconv.ini - /etc/php/8.0/cli/conf.d/20-phar.ini - /etc/php/8.0/cli/conf.d/20-posix.ini - /etc/php/8.0/cli/conf.d/20-readline.ini - /etc/php/8.0/cli/conf.d/20-shmop.ini - /etc/php/8.0/cli/conf.d/20-sockets.ini - /etc/php/8.0/cli/conf.d/20-sysvmsg.ini - /etc/php/8.0/cli/conf.d/20-sysvsem.ini - /etc/php/8.0/cli/conf.d/20-sysvshm.ini - /etc/php/8.0/cli/conf.d/20-tokenizer.ini You can also run php --ini in a terminal to see which files are used by PHP in CLI mode. Alternatively, you can run Composer with --ignore-platform-req=ext-dom to temporarily ignore these required extensions.

Error

Any ideas. Please advise.

Thanks.

0 likes
47 replies
vincent15000's avatar
Composer is operating significantly slower than normal because you do not have the PHP curl extension enabled.

Have you simply tried to enable the PHP curl extension ?

deicool's avatar

@vincent15000

Need help with the following problems:

Problem 1 - tijsverkoyen/css-to-inline-styles 2.2.2 requires php ^5.5 || ^7.0 -> your php version (8.0.24) does not satisfy that requirement. - tijsverkoyen/css-to-inline-styles[2.2.3, ..., 2.2.x-dev] require ext-dom * -> it is missing from your system. Install or enable PHP's dom extension. - inertiajs/inertia-laravel[v0.5.3, ..., v0.5.4] require laravel/framework ^6.0|^7.0|^8.74|^9.0 -> satisfiable by laravel/framework[v8.74.0, ..., 8.x-dev]. - laravel/framework[v8.74.0, ..., 8.x-dev] require tijsverkoyen/css-to-inline-styles ^2.2.2 -> satisfiable by tijsverkoyen/css-to-inline-styles[2.2.2, ..., 2.2.x-dev]. - Root composer.json requires inertiajs/inertia-laravel ^0.5.3 -> satisfiable by inertiajs/inertia-laravel[v0.5.3, v0.5.4].

1 like
vincent15000's avatar

@deicool I have never tested PingCRM, but you can try to force the version of tijsverkoyen/css-to-inline-styles 2.2.2 to 2.2.5 (in the composer.json file) which is compatible with PHP 8.x.

"tijsverkoyen/css-to-inline-styles": "^2.2.5",
vincent15000's avatar

@deicool If you have solved your problem, can you please assign a best answer to close the post ?

deicool's avatar

Hello

When I run the command "npm run dev", I am getting the below mentioned error:

Error

ubuntu@ip-172-31-12-225:/var/www/html/pingcrm$ npm run dev

@ dev /var/www/html/pingcrm npm run development

@ development /var/www/html/pingcrm mix && npm run ssr:build

● Mix █████████████████████████ done (99%) plugins CustomTasksPlugin

Killed npm ERR! code ELIFECYCLE npm ERR! errno 137 npm ERR! @ development: mix && npm run ssr:build npm ERR! Exit status 137 npm ERR! npm ERR! Failed at the @ development script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/ubuntu/.npm/_logs/2022-10-11T07_12_12_403Z-debug.log npm ERR! code ELIFECYCLE npm ERR! errno 137 npm ERR! @ dev: npm run development npm ERR! Exit status 137 npm ERR! npm ERR! Failed at the @ dev script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/ubuntu/.npm/_logs/2022-10-11T07_12_13_048Z-debug.log ubuntu@ip-172-31-12-225:/var/www/html/pingcrm$ more /home/ubuntu/.npm/_logs/2022-10-11T07_12_13_048Z-debug.log 0 info it worked if it ends with ok 1 verbose cli [ 1 verbose cli '/home/ubuntu/.nvm/versions/node/v14.10.0/bin/node', 1 verbose cli '/home/ubuntu/.nvm/versions/node/v14.10.0/bin/npm', 1 verbose cli 'run', 1 verbose cli 'dev' 1 verbose cli ] 2 info using [email protected] 3 info using [email protected] 4 verbose run-script [ 'predev', 'dev', 'postdev' ] 5 info lifecycle @~predev: @ 6 info lifecycle @~dev: @ 7 verbose lifecycle @~dev: unsafe-perm in lifecycle true 8 verbose lifecycle @~dev: PATH: /home/ubuntu/.nvm/versions/node/v14.10.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/html/pingcrm/node_modules/.bin:/home/ubuntu/. nvm/versions/node/v14.10.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin 9 verbose lifecycle @~dev: CWD: /var/www/html/pingcrm 10 silly lifecycle @~dev: Args: [ '-c', 'npm run development' ] 11 silly lifecycle @~dev: Returned: code: 137 signal: null 12 info lifecycle @~dev: Failed to exec dev script 13 verbose stack Error: @ dev: npm run development 13 verbose stack Exit status 137 13 verbose stack at EventEmitter. (/home/ubuntu/.nvm/versions/node/v14.10.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16) 13 verbose stack at EventEmitter.emit (events.js:314:20) 13 verbose stack at ChildProcess. (/home/ubuntu/.nvm/versions/node/v14.10.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack at ChildProcess.emit (events.js:314:20) 13 verbose stack at maybeClose (internal/child_process.js:1047:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5) 14 verbose pkgid @ 15 verbose cwd /var/www/html/pingcrm 16 verbose Linux 5.15.0-1020-aws 17 verbose argv "/home/ubuntu/.nvm/versions/node/v14.10.0/bin/node" "/home/ubuntu/.nvm/versions/node/v14.10.0/bin/npm" "run" "dev" 18 verbose node v14.10.0 19 verbose npm v6.14.8 20 error code ELIFECYCLE 21 error errno 137 22 error @ dev: npm run development 22 error Exit status 137 23 error Failed at the @ dev script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 137, true ]

1 like
Sinnbeck's avatar

@deicool Vite requires Node.js version 14.18+, 16+. You are running node 14.10. I recommend installing node 16.x

1 like
deicool's avatar

Somehow the command "npm run dev" is taking forever...

1 like
Sinnbeck's avatar

@deicool Yes until you close it. Its a server :)

So just open the website (Are you using php artisan serve?) and it should show the page.

You can also run npm run build to just compile once

1 like
deicool's avatar

@sinnbeck If "npm run dev" runs a server, why would it say 13% complete? And it just waits at 13%.

1 like
Sinnbeck's avatar

@deicool Ah sorry. I forgot that pingcrm still havent been updated to use vite. Sorry about that. It still uses mix.

Try npm run watch instead :)

1 like
Sinnbeck's avatar

@deicool Then point apache2 to the public folder in the pingcrm project (in a virtual hosts file)

1 like
deicool's avatar

@Sinnbeck

I did, still not working. It is listing the directories under pingcrm

DocumentRoot /var/www/html/pingcrm/public/ <Directory /var/www/html/pingcrm/public/>

I am trying a few things, will update.

1 like
Sinnbeck's avatar

@deicool Sounds like it isnt picking up the index.php file. Is this on windows or linux or mac?

1 like
deicool's avatar

@Sinnbeck

That could be it. I think I might have to update the php which apache uses to 8.

On the Ubuntu terminal

PHP 8.1.11 (cli) (built: Sep 29 2022 22:28:49) (NTS) Copyright (c) The PHP Group Zend Engine v4.1.11, Copyright (c) Zend Technologies with Zend OPcache v8.1.11, Copyright (c), by Zend Technologies

On Apache

PHP Version 7.2.34-35+ubuntu20.04.1+deb.sury.org+2

Sinnbeck's avatar

@deicool Hmm yeah that seems a bit off. Can you try

sudo apt install php8.1-common
deicool's avatar

@Sinnbeck

sudo apt install php8.1-common Reading package lists... Done Building dependency tree Reading state information... Done php8.1-common is already the newest version (8.1.11-1+ubuntu20.04.1+deb.sury.org+2). php8.1-common set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

deicool's avatar

When i run "sudo npm install", it gets stuck at:

npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

npm WARN deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility

npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. [ ......] / extract:prettier: sill extract prettier@^2.5.1 extracted to /var/www/html/pingcrm/node_modules/.staging/prettier-3021c0dd (35459ms)

deicool's avatar

@Sinnbeck

What I mean is the terminal to the server is stuck when i run the command "sudo npm install". I have to reboot the server every time i run that command.

Sinnbeck's avatar

@deicool You should not need sudo to install npm dependencies. The user that is running the command should have write permissions to the folder

And you can always hit ctrl+c to quit a long running command.

deicool's avatar

@Sinnbeck

ctrl+c doesn't work anymore on the terminal. It just hangs and does not accept any input from me.

Sinnbeck's avatar

@deicool Ok I dont know why that would happen. I have not personally experienced that before :( But maybe you can compile the assets locally and upload them to the server instead?

deicool's avatar

@Sinnbeck

Mebbe it is bcos i am using a low-end-server (1 cpu,1gb RAM, 64gb disk size,). Probably should go for a high end server

Sinnbeck's avatar

@deicool No that should be fine. I have several servers I use privately for my blog and such, and each work fine :)

1 like
deicool's avatar

@Sinnbeck

The command "npm install" takes forever. I will have to find some other way.

Sinnbeck's avatar
Sinnbeck
Best Answer
Level 102

@deicool Maybe something is wrong with the vps. Perhaps just try making a new one and see if it works? :)

deicool's avatar

@sinnbeck

When I run the command "npm run dev" it is giving the below mentioned error:

dev npm run development

development mix && npm run ssr:build

sh: 1: mix: not found

Any ideas?

Sinnbeck's avatar

@deicool Try npm install. And is that on the new server? On the server you should not run dev. Run npm run prod

deicool's avatar

@Sinnbeck

Yup it's on a brand new server.

I am also using apache (so would i be needing to run " Run npm run prod"?)

deicool's avatar

@Sinnbeck

When I run the command "php artisan serve", it gives the following output:

Starting Laravel development server: http://127.0.0.1:8000 [Mon Oct 17 06:38:43 2022] PHP 8.1.2 Development Server (http://127.0.0.1:8000) started

When i try accessing the url "http://external-ip-address:8000" from the browser, it doesn't work. I get the error "This site can’t be reached". I think it can be only run locally (http://127.0.0.1:8000).

Any ideas?

deicool's avatar

@Sinnbeck

I tried the below commands, it still doesn't work:

sudo php artisan serve --host 3.101.212.39 --port 80

php artisan serve --host 0.0.0.0

Gives the error: Starting Laravel development server: http://3.101.212.39 80 [Mon Oct 17 07:05:13 2022] Failed to listen on 3.101.212.39 :80 (reason: Cannot assign requested address)

Sinnbeck's avatar

@deicool Let me try again. php artisan serve is for running on your local computer while developing. You cannot use it on a server. Use apache2 or nginx to set up a proper webserver.

deicool's avatar

@Sinnbeck

Hmm. I then wonder why do we have a command like this : "sudo php artisan serve --host 3.101.212.39 --port 80"

Sinnbeck's avatar

@deicool So you can expose it to different things locally while testing. But php artisan serve is single threaded so it can only every manage 1 request at a time.. So your site will be sloooooooow :)

Sinnbeck's avatar

@deicool Happy to help. You can close the thread by marking a best answer

1 like
deicool's avatar

I have got pingcrm working now. Was wondering how can I understand the nuts-n-bolts of pingcrm?

deicool's avatar

@Sinnbeck

Is there a simple application of Laravel without using inertiajs? Just application of pure Laravel code.

Please or to participate in this conversation.