I am running Yosemite 10.10.1 however had the same problem on Lion prior to upgrading (thought it would fix it!). Apologies if this has already been answered but I have searched hi and low and cannot find anything...
I have tried updating to the latest version of MAMP and renamed the envvars file, both have not fixed the problem.
When I start MAMP (not MAMP pro), it opens, when I click to start the servers I get "Apache couldn't be started. Please check your MAMP installation and configuration".
Please someone help this has been driving me crazy, any help would certainly be appreciated!
Had the similar problem-
Do the following
Rename the file “envvars” located in /Applications/MAMP/Library/bin into “_envvars”
In the file "/Applications/MAMP/conf/apache/httpd.conf" remove the line
LoadModule example_module modules/mod_example.so(86th line)(Use sublime Text/vim).
Use default port numbers 8888 for Apache and 8889 for Mysql.
Exactly the same problem I have. Going back to an older 3.0.x solves the problem. Just replace the htdocs and db folder with the ones before the update an it will run again.
Peter
I've had this problem when upgrading from 6.6 to 6.7. Seems that sometimes the Apache and MySQL servers keep on running during the upgrade and there is a problem binding to the port. What worked for me was this:
Completely quit MAMP.
Kill all Apache and MySQL processes using the pkill command:
pkill -f httpd && pkill -f mysql
Run MAMP again and set ports to 80/3306
Related
I installed LAMPP on my Ubuntu 20.04 machine. I also installed PgAdmin4 to work with my Postgresql 14. The problem is, both LAMPP and PgAdmin4 installation came with their own Apache2. This cause error for me, as in the development process, I use 127.0.0.1/pgadmin4 and localhost/ at browser interchangeably.
For now, each time I need to edit psql database in PgAdmin4, I need to turn off LAMPP using sudo /opt/lampp/lampp stop command and to turn on pgAdmin4 with sudo /etc/init.d/apache2 start. And vice-versa if I need to test the website output in LAMPP localhost.
Is there any way around them? How to configure pgAdmin4 to use Apache2 from LAMPP? Or to Install pgAdmin4 without the packaged Apache2?
I already tried using PhpPgAdmin 7 instead, but it keeps getting error.
I've upgraded to the current version of macOS. I want to work with Apache. Well, my problem is, that when I try to access localhost with or without ~Username, I get an error message saying ERR_CONNECTION_REFUSED on Chrome or "Can't open Page" on Safari. Apache is running and apachectl configtest says "Syntax OK".
I placed the current version of phpMyAdmin into /Library/WebServer/Documents and tried to access it, same problem.
I followed the steps in this guide without a solution for me
Apache localhost/~username/ not working
So does anyone know what problem I'm facing? I'm clueless right now.
I had the same outcomes as above, using virtual hosts though, and after updating to macos 10.12.2 was receiving ERR_CONNECTION_REFUSED.
My original setup is based on the excellent posts here: https://getgrav.org/blog/macos-sierra-apache-mysql-vhost-apc
And as such, because I'm using Homebrew, all I needed to do was also run brew upgrade on CLI followed by sudo apachectl restart and I'm back up and running.
I updated my MAMP to the latest version 3.0 today, due to the fact of the Apache issue on the old version.
Still the Apache issue persist. This time the envvars in the latest MAMP is named envvars_
I tried to renamed it to _envvars or _envvars_ but the apache still doesn't run.
I also tried different ports.
***I decided to update my MAMP, because when I tried _envvars on the old version of MAMP and my Apache start running but mySQL didn't and I read that with the new version of MAMP this issue will be resolved.
Anybody experienced the same issue? Any solution or work around with this problem? Thanks.
Did you retain your original httpd.conf from before the upgrade? You may have to edit the modules in your httpd.conf.
I had to run /Applications/MAMP/Library/bin/apachectl configtest to display which modules to remove.
I commented out a example_module.
#LoadModule example_module modules/mod_example.so
I got just the new public beta 2 of OS X 10.10 and MAMP stopped to work. No way to start the apache server, port 80 or 8080, always error: httpd cannot be opened...
In the first public beta MAMP worked correctly. Found with Google some advice: Rename the file “envvars” located in /Applications/MAMP/Library/bin into “_envvars” and this is not working at all.
Any idea on how to fix that?
Renaming the envvars file in /Applications/MAMP/Library/bin worked for me.
I find it odd that the "_envvars" solution works for some folks, but not for others. As I mentioned in a previous post, the minute I made that small file name change, MAMP PRO's Apache server started running again.
I should note that the problem didn't start for me until after I installed Yosemite DP5 over top of Yosemite Public Beta 1. Or maybe it was when I installed Yosemite DP6 over top of DP5. Whatever the case may be, this fix did work for me.
Maybe it has something to do with your specific OS configuration, or the particular machine that you are using.
I have been trying to install IonCube for the past 2 days on my localhost, and it just won't show up. Today I tried changing the PHP versions to force some sort of hard refresh, and MAMP is not changing versions.
By the looks of this, in my opinion, Apache is not restarting at all, how can I force it to stop with a Terminal command or something?
Thanks in advance.
The short and sweet is to restart your machine entirely, fine for if you're just a local developer.