Kirby doesn’t work on the server by my client

[coolcoolhomebody]

Hello, I created a website with Kirby.
When I make Kirby’s website, it generally works well,
but it doesn’t work on the server by my client.

So the server developer wants to talk to Kirby.
I’d like to ask you where to talk, not at the forum.

The client’s message to me is as follows.
Since I don’t understand the server well, I think it would be better to connect directly with Kirby’s developer.

---

Could not update the integration plugin

• Changed current directory to /var/www/vhosts/hzone.com/.composer* Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See Deprecating Packagist.org support for Composer 1.x

• [Composer\Downloader\TransportException]

• The “http://repo.packagist.org/p/provider-2013%24f3374f551eeda6ea5a872f28d100748b74b2f5ee2407d2b84e352907f745afe1.json” file could not be downloaded: failed to open stream: Network is unreachable

• require [–dev] [–prefer-source] [–prefer-dist] [–fixed] [–no-progress] [–no-suggest] [–no-update] [–no-scripts] [–update-no-dev] [–update-with-dependencies] [–update-with-all-dependencies] [–ignore-platform-reqs] [–prefer-stable] [–prefer-lowest] [–sort-packages] [-o|–optimize-autoloader] [-a|–classmap-authoritative] [–apcu-autoloader] [–] []…

[mauricehh]

Looks like they want to install or update something via composer and that doesn’t work on the server. Imho something that has to be fixed by the server admin.

But maybe it’s in general a better idea to build an update/deployment workflow. Deployment via git, run (and test!) updates locally before doing it direktly on production, for example.

[pixelijn]

@coolcoolhomebody

Could not update the integration plugin

And what is the integration plugin?