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.
Related
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 have problem viewing php files locally on my mac, it used to work just fine for the past year and suddly apache stopped working for some reason,
I didn't change any thing or any port.
I'm running El Capitan 10.11.5.
I have tried reinstalling MAMP on my computer and changing 'envvars' to '_envvars' and lots of different terminal commands ,but nothing works.
Can anyone help?
Thanks
Recently I decided to make some improvements on my sadly abandoned website I've developed using easyphp. I tried to installed the last version of easyphp to be sure being up-to-date. Unfortunately the last version is not quite what I hoped for and decided to uninstall it and switch to wampserver.
My website is not working anymore though and after few analyzing I am sure this is from the version of apache being different or from wamp dealing with the apache options differently from easyphp (2.4.7 -> 2.4.9).
The problem seems to come from the .htaccess file (which worked nicely on easyphp), is one here have faced the same problem when changed from easyphp to wampserver ? or any suggestions where the problem could come from ?
I finally realized the module rewriteEngine was not initialized...
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
Looking for some help with getting xdebug to behave with my setup. My goal is to be able to debug Joomla code.
First let me preface saying that about a year ago I was able to get a version xdebug to work with Eclipse PDT 2.1 with xampp under Vista 32bit. However, now I'm on a new machine, and I wanted to get everything working with the latest versions. I did so by following through this walk-through. Now, trying to do the same thing I can't get it to work.
First, as per the walk-through, I downloaded php_xdebug-2.0.0-5.2.2.dll. Quickly realized that I needed an xdebug for php 5.3. So, I found the xdebugs Tailored Installation Instructions and followed that. My php.ini section looks as thus:
[XDebug]
;; Only Zend OR (!) XDebug
zend_extension = "D:\xampp\php\ext\php_xdebug-2.1.0-5.3-vc6.dll"
xdebug.remote_enable=true
xdebug.remote_host=localhost
xdebug.remote_port=10000
xdebug.remote_handler=dbgp
xdebug.profiler_enable=1
xdebug.profiler_output_dir="D:\xampp\tmp"
So this got the xdebug to actually show up in the phpinfo(). But, in Eclipse when I Debug As Php Webpage, it at first appears to connect, however if I step to the next line of code the debugger just sits there saying it is stepping, indefinitely. Sometimes apache will crash. I tried ports 9000, and 10000 with no avail.
What I did find out is, if I use the the php_xdebug.dll that comes with XAMPP 1.7.3, I actually can connect and step without any issues, EXCEPT, that version of xdebug apparently has a major bug in it that causes all my variables to be listed as 'Uninitialized'. So it is basically useless, however, it does give some hope that I have some of this stuff set up correctly.
So, my current setup thus: Win7 32bit, XAMPP 1.7.3 (PHP 5.3.1, Apache 2.2.14), Eclipse PDT 2.2
I have very limited experience with basically all the tools here so I'm kinda at a loss of what to do. Any help would be greatly appreciated. I searched some of the other posts here with similar issue but most of them appear to be for older versions of these components.
your report is somewhat confusing. As far as I understand you, your setup works as soon as you replace the XDebug-dll. Then your (primary) problem cannot be related to your settings, as far as you also adjusted zend_extension, of course.
Though xdebug.remote_port=10000 seems odd. Std is 9000. If you use 9000, the you have to tell Eclipse in Window/Preferences/PHP/Debug/Debuggers to also listen to that port for XDebug.
Best
Raffael