frontendschlampe commented 2 years ago

I want to make an update on my local installation. In the past there was no problems, but after updating to Manager 1.4.7 I got the following message, if I want to make an update:

Error handling the Composer Resolver Cloud. Please try again later.

There was only an update for Contao Manager but not for MAMP PRO.

V15 commented 2 years ago

Same here. Same setup.

Toflar commented 2 years ago

I think this is neither a Manager nor a Cloud issue. It seems like the intermediate CA information has changed.

Probably MAMP Pro does not have access to the CA installed on the local system, thus falling back to the bundled one (https://github.com/contao/contao-manager/blob/1.x/api/System/Request.php#L217). This has been updated lately and the X3 has been removed as it expired September 30. See https://github.com/composer/ca-bundle/pull/66. Related discussion: https://github.com/composer/composer/issues/10121

/cc @leofeyer

fritzmg commented 2 years ago

As far as I understand the issue, the PHP OpenSSL extensions needs to have a minimum version to work with the recent Composer version. This apparently also affects some Hosters and not just MAMP Pro: #662

basselin commented 2 years ago

Replace /Applications/MAMP/Library/OpenSSL/certs/cacert.pem with https://curl.se/ca/cacert.pem

And you can specify this cacert.pem to composer with the command : composer config --global cafile '/Applications/MAMP/Library/OpenSSL/certs/cacert.pem'

herrweiss77 commented 2 years ago

I have the same problem. MAMP Pro / macOS 11.6

speedweb commented 2 years ago

leider das selbe Problem auf mehreren Hosting mit Plesk. Was kann hier genau dagegen unternommen werden?

leofeyer commented 2 years ago

Das Paket ca-certificates muss auf dem Server aktualisiert werden (z.B. mit apt-get oder mit aptitude), damit das neue Root-Zertifikat installiert wird.

herrweiss77 commented 2 years ago

Das Paket ca-certificates muss auf dem Server aktualisiert werden (z.B. mit apt-get oder mit aptitude), damit das neue Root-Zertifikat installiert wird.

Auch wenn kein SSL genutzt wird (unter MAMP Pro)?

leofeyer commented 2 years ago

Du kannst ja nicht "kein SSL nutzen", weil die Verbindung zum Cloud-Resolver ausschließlich über https:// möglich ist.

aschempp commented 2 years ago

bitte schaut ob das Problem mit dem neuen Manager 1.4.8 behoben ist.

herrweiss77 commented 2 years ago

bitte schaut ob das Problem mit dem neuen Manager 1.4.8 behoben ist.

Leider nein (MAMP Pro / MacOS)

dazzle89 commented 2 years ago

Anfangs sah es gut aus, am Ende bekam ich dann aber diese Meldung (HostEurope/Plesk):

Package patchwork/utf8 is abandoned, you should avoid using it. Use symfony/polyfill-mbstring or symfony/string instead. Generating optimized autoload files composer/package-versions-deprecated: Generating version class... composer/package-versions-deprecated: ...done generating version class contao/manager-plugin: Generating plugin class... contao/manager-plugin: ...done generating plugin class 90 packages you are using are looking for funding. Use the composer fund command to find out more!

@php vendor/bin/contao-setup In AbstractMySQLDriver.php line 112:

An exception occurred in driver: SQLSTATE[HY000] [1045] Access denied for u
ser 'root'@'localhost' (using password: NO)

In Exception.php line 18:

SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using pas
sword: NO)

In PDOConnection.php line 40:

SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using pas
sword: NO)

Script @php vendor/bin/contao-setup handling the post-install-cmd event returned with error code 1

Process terminated with exit code 1

Result: General error

herrweiss77 commented 2 years ago

Bei mir erscheint immer noch die gleiche Fehlermeldung: Zuerst HTTP request to https://www.composer-resolver.cloud/jobs failed with status code 500 () Dann Error handling the Composer Resolver Cloud. Please try again later.

V15 commented 2 years ago

Bei mir leider auch keine Besserung:

$ /Applications/MAMP/bin/php/php7.4.12/bin/php -q -dmax_execution_time=0 -dmemory_limit=-1 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /Users/xxx/web/contao-manager.phar.php composer remove alpdesk/alpdesk-parallax --no-update --no-scripts --no-ansi --no-interaction

Using config.component-dir has been deprecated. Please use extra.contao-component-dir instead. /Users/xxx/composer.json has been updated

Process terminated with exit code 0 Result: OK

Error handling the Composer Resolver Cloud. Please try again later.

netzarbeiter commented 2 years ago

I can confirm this issue (Contao Manager 1.4.8). On one of my customer's servers, I have also recently been unable to update and the connection with another software also fails.

frontendschlampe commented 2 years ago

bitte schaut ob das Problem mit dem neuen Manager 1.4.8 behoben ist.

same problem with Manager 1.4.8 and Mamp Pro 6.6

dazzle89 commented 2 years ago

Ich weiß nicht warum, aber nun konnte ich es problemlos installieren. Habe nochmal den aktuellen Manager runtergeladen und als einzigen Unterschied die 4.9 statt 4.12 installiert

ghost commented 2 years ago

Bei mir auch unter Contao CMS 4.9, MAMP PRO 6.6 und PHP 8.0.8 (CM = 1.4.8) leider das selbe Problem.

herrweiss77 commented 2 years ago

Dieser Workaround löst das Problem unter MAMP Pro / MacOS (Danke an Corsin Simeon):

Diese Datei runterladen [(http://curl.haxx.se/ca/cacert.pem)]
Datei nach /Applications/MAMP/Library/OpenSSL/certs/ kopieren (Original-Datei vorher sichern)

php.ini der entsprechenden PHP Version folgendermassen anpassen:

[openssl]
openssl.cainfo=/Applications/MAMP/Library/OpenSSL/certs/cacert.pem
openssl.cafile=/Applications/MAMP/Library/OpenSSL/certs/cacert.pem

MAMP Pro neustarten

sdahlmann commented 2 years ago

Bei Dogado Webhosting bekomme auch ich eine Fehlermeldung bei Neuinstallation vom Contao CMS 4.12.2 bei der Nutzung vom Contao Manager in der aktuellen Version 1.4.8. Dogado nutzt Plesk. Vor kurzem ging es noch einwandfrei, auch mit Contao 4.12.x. Ich hoffe, dass das hier genannte Problem nicht bei weiteren Webhostern auftritt, was ich leider befürchte. Gibt es einen Workaround oder umgehend eine Fehlerbereinigte Contao Manager Version?

Fehlermeldung bei Contao Manager auf Dogado Webhostiung:

composer create-project contao/managed-edition:4.12 composer install $ /opt/plesk/php/7.4/bin/php -q -dmax_execution_time=0 -dmemory_limit=-1 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Berlin /var/www/vhosts/h15621.web113.dogado.net/httpdocs/sdw-shop1/web/contao-manager.phar.php composer install --prefer-dist --no-dev --no-progress --no-ansi --no-interaction --optimize-autoloader No composer.lock file present. Updating dependencies to latest instead of installing from lock file. See https://getcomposer.org/install for more information. Loading composer repositories with package information Updating dependencies Lock file operations: 175 installs, 0 updates, 0 removals

Locking ausi/slug-generator (v1.1.1)
Locking bacon/bacon-qr-code (2.0.4)
Locking beberlei/assert (v3.3.1) ...... Writing lock file Installing dependencies from lock file Package operations: 175 installs, 0 updates, 0 removals As there is no 'unzip' nor '7z' command installed zip files are being unpacked using the PHP zip extension. This may cause invalid reports of corrupted archives. Besides, any UNIX permissions (e.g. executable) defined in the archives will be lost. Installing 'unzip' or '7z' may remediate them.
Downloading contao-components/installer (1.4.1)
Downloading composer/package-versions-deprecated (1.11.99.4)
Downloading symfony/polyfill-ctype (v1.23.0) ......
Installing contao-components/installer (1.4.1): Extracting archive
Installing composer/package-versions-deprecated (1.11.99.4): Extracting archive
Installing symfony/polyfill-ctype (v1.23.0): Extracting archive ...... 54 package suggestions were added by new dependencies, use composer suggest to see details. Package patchwork/utf8 is abandoned, you should avoid using it. Use symfony/polyfill-mbstring or symfony/string instead. Generating optimized autoload files composer/package-versions-deprecated: Generating version class... composer/package-versions-deprecated: ...done generating version class 90 packages you are using are looking for funding. Use the composer fund command to find out more! contao/manager-plugin: Generating plugin class... contao/manager-plugin: ...done generating plugin class

@php vendor/bin/contao-setup In AbstractMySQLDriver.php line 112:

An exception occurred in driver: SQLSTATE[HY000] [1045] Access denied for u
ser 'root'@'localhost' (using password: NO)

In Exception.php line 18:

SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using pas
sword: NO)

In PDOConnection.php line 40:

SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using pas
sword: NO)

Script @php vendor/bin/contao-setup handling the post-update-cmd event returned with error code 1

Process terminated with exit code 1

Result: General error

fritzmg commented 2 years ago

@sdahlmann that is a different issue: https://github.com/contao/contao/issues/3557

MaCo7 commented 2 years ago

Habe das gleiche Problem immer noch, trotz des Workarounds von Patrick Weiss. Ich bekomme kein Contao Upgrade oder UPdate mehr zum Laufen. MampPro 6.6, CM 1.48 .

contaoacademy commented 2 years ago

Ich konnte das Problem mit dem Workaround lösen. Hast du die richtige php.ini bearbeitet?

MaCo7 commented 2 years ago

@contaoacademy ICh hoffe ja ;). Wie genau bekomme ich das raus? Habe auch mehrere versucht. /Programme/MAMP/bin/php/php7.3.29/conf/php.ini .Ok?

fritzmg commented 2 years ago

/Programme/MAMP/bin/php/php7.3.29/conf/php.ini .Ok?

Wenn der Contao Manager bei dir das PHP CLI unter /Programme/MAMP/bin/php/php7.3.29 nutzt, dann ja. Wenn nicht, dann nicht.

contaoacademy commented 2 years ago

In folgendem Beitrag habe ich es auch noch mal dokumentiert: https://contao-academy.de/contao-faq/mamp-6-6-fehler-error-handling-the-composer-resolver-cloud-please-try-again-later

MaCo7 commented 2 years ago

HEy, es klappt. Dankkkeeeee Chris! ICh bin nochmal den Beitrag von Christian durchgegangen. HAbe dabei unter Parallels ein komplett neues macOS Monterey installiert, sowie MAmp Pro, etc. Die Resolver Cloud läuft!! Es funktioniert aber nur, wenn ich die Template php Dateien Bearbeite, nicht die, die Contao im Manager anzeigt. Seltsam!! Nun versuche ich es mal ob es so auch ohne VM hinbekomme.

aschempp commented 2 years ago

Closing this since it has to be solved locally on MacOS (see https://github.com/contao/contao-manager/issues/661#issuecomment-966169812)

fritzmg commented 2 years ago

It still can be solved on the server as well by removing the expired root certificate from the chain.

aschempp commented 2 years ago

thanks @fritzmg for the heads-up! We finally fixed this on the cloud directly, so this should be solved for anyone using MacOS/MAMP now 🎉

rustykowski commented 2 years ago

Leider habe ich unter MAMP 6.6 weiterhin das Problem. Sowohl mit Cloud-Resolver als auch ohne. Ich bin dem Workaround von @herrweiss77 gefolgt. Habe natürlich auf das richtige Template (sprich: die richtige php.ini) geachtet, Mamp neu gestartet etc.

Die Fehlermeldung lautet:

In CurlDownloader.php line 354:

  curl error 60 while downloading https://repo.packagist.org/packages.json: S  
  SL certificate problem: unable to get local issuer certificate

fritzmg commented 2 years ago

@rustykowski that seems to be a different problem. In your case your local CA file is not available or not accessible.

rustykowski commented 2 years ago

@fritzmg Can you please explain this a bit more? What would be the local CA file in the case of Mamp? Among other things, I find these files in the OpenSSL directory: MAMP_PRO_Root_CA.crt MAMP_PRO_Root_CA.key MAMP_PRO_Root_CA.srl

contao / contao-manager

no update possible since Contao Manager 1.4.7 with MAMP PRO 6.5 #661

Process terminated with exit code 1

Result: General error

Process terminated with exit code 1

Result: General error