![]() Out there you can find enough guides that helps you archive this because, frankly, there are plenty of methods to get this done. The idea behind changing the Command-line to start using the PHP coming with MAMP and its configuration is to be able to switch rapidly between PHP versions and to have the configuration for PHP in only one place. The same goes for libpq.dylib.Īt the end everything should look like the following:īy default, after installation, MAMP will make its PHP binaries "available on the browser" while the Terminal will keep on using the system's PHP with its own configuration. ![]() ln -s libpq.5.7.dylib libpq.5.dylib Īs you can see on the previous screenshot, the symlink libpq.5.dylib points to a broken path for libpq.5.7.dylib which is basically right there on the same folder. But it doesn't matter, let's just fix those symlinks by deleting them and creating them again. Go to /Applications/MAMP/Library/pg/lib and you'll notice something really weird which are broken paths for the symlinks libpq.5.dylib and libpq.dylib as seen below.Īgain, how that happened is another mystery. Now it doesn't matter what MAMP is looking for as it will find it either way. Go to that extensions subfolder mentioned in the error (for example, mine is /Applications/MAMP/bin/php/php7.3.21/lib/php/extensions/no-debug-non-zts-20180731/) and create a symlink for pdo_pgsql.so called pdo_pgsql.so.so by doing: ln -s pdo_pgsql.so pdo_pgsql.so.so What's interesting about the error above is that it mentions pgsql.so.so which is clearly wrong because of the double. That didn't work for me (and to be honest I can't see what's the relationship with Brew and MAMP) but you can give it a try anyway since it's easy to do. To get around this situation, many suggest to update Brew with brew update. ![]() Reason: image not found), /Applications/MAMP/bin/php/php7.3.21/lib/php/extensions/no-debug-non-zts-20180731/pgsql.so.so (dlopen(/Applications/MAMP/bin/php/php7.3.21/lib/php/extensions/no-debug-non-zts-20180731/pgsql.so.so, 9): image not found)) in Unknown on line 0 Referenced from: /Applications/MAMP/bin/php/php7.3.21/lib/php/extensions/no-debug-non-zts-20180731/pgsql.so PHP Warning: PHP Startup: Unable to load dynamic library 'pgsql.so' (tried: /Applications/MAMP/bin/php/php7.3.21/lib/php/extensions/no-debug-non-zts-20180731/pgsql.so (dlopen(/Applications/MAMP/bin/php/php7.3.21/lib/php/extensions/no-debug-non-zts-20180731/pgsql.so, 9): Library not loaded: /Applications/MAMP/Library/pg/lib/libpq.5.dylib ![]() I don't know exactly why this happened to me out of the sudden (I blame MAMP as it was the last thing that I updated) but I managed to fix it anyway. I had this weird issue that seems to be related to macOS Big Sur and MAMP, allegedly, either both combined or when upgrading any of those two (or both?). be overridden on a per-stream basis via the "cafile" SSL stream contextįinally, remember to restart Apache before trying again. not specify a value for this directive as PHP will attempt to use the to use when verifying the identity of SSL/TLS peers. The location of a Certificate Authority (CA) file on the local filesystem If still unsure about the location of the cacert.pem you need to replace, check your php.ini and look for the openssl.cafile= line. If you are using MAMP, chance are that the file you need to replace, locally, is on /Applications/MAMP/Library/OpenSSL/certs/, but if you are unsure you can open a Terminal and run locate cacert.pem to get a list of all the places where you can find the Certificate Authority file. So, fixing this is quite simple as it only involves replacing the cacert.pem file with the one you can download here: CA certificates extracted from Mozilla. cacert.pem is a bundle of CA certificates that you use to verify that the server is really the correct site you're talking to (when it presents its certificate in the SSL handshake).Ĭomment by Daniel Stenberg on Stack Overflow The full error is up there and it appears when you use Composer such as when running composer install, and it seems to be that your computer is using a wrong (or not up to date?) CA certificate when trying to communicate with a Composer repository. OpenSSL Error messages:Įrror:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed The file could not be downloaded: SSL operation failed with code 1. But it's there, and I have a potential solution, hoping you are in a hurry to get it fixed without asking too much questions. This is one of those errors that makes you say " this started to happen out of the sudden and I'm 100% sure I touched nothing". I'm going to be honest with you: I have no idea why this can happen.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |