Wordpress Site Not Working For Mac Sierra
The excitement of installing a new version of macOS, especially if its a High Sierra 10.13, is only tempered by the possibility of it not working properly or not being compatible with the apps you use most. Sep 28, 2017 - This worked for me when I ran into the same problem.com/questions/39631351/apache-localhost-403-forbidden-with-macos-sierra.
Setting Stuff Up • • • • • • • Web serving is possible via the inbuilt Apache app, it is installed ready to be fired up. This needs to be done in the Terminal which is found at /Applications/Utilities/Terminal For those not familiar with the Terminal, it really isn’t as intimidating as you may think, once launched you are faced with a command prompt waiting for your commands – just type/paste in a command and hit enter, some commands give you no response – it just means the command is done, other commands give you feedback. Using the prefix of sudo is required for commands that have their applications protected in certain folders – when using sudo you will need to confirm with your admin password or iCloud password if set up that way.
Lets get to it. To start Apache web sharing sudo apachectl start to stop it sudo apachectl stop to restart it sudo apachectl restart To find the Apache version httpd -v The Apache version that comes in macOS Sierra is Apache/2.4.23.
After starting Apache – test to see if the webserver is working in the browser – – you should see the “It Works!” text. If you don’t get the localhost test, you can try troubleshooting Apache to see if there is anything wrong in its config file by running apachectl configtest This will give you an indication of what might be wrong. Document root is the location where the files are shared from the file system and is similar to the traditional names of ‘ public_html‘ and ‘ htdocs‘, OSX has historically had 2 web roots one at a system level and one at a user level – you can set both up or just run with one, the user level one allows multiple accounts to have their own web root whilst the system one is global for all users. Control command for bullet point. It seems there is less effort from Apple in continuing with the user level one but it still can be set up with a couple of extra tweaks in configuration files.
It is easier to use the user level one as you don’t have to keep on authenticating as an admin user. System Level Web Root – the default system document root is still found at – The files are shared in the filing system at – /Library/WebServer/Documents/ User Level Root The other web root directory which is missing by default is the ‘ ~/Sites’ folder in the User account. This takes a bit longer to set up but some users are very accustomed to using it. You need to make a “ Sites” folder at the root level of your account and then it will work. Once you make the Sites folder you will notice that it has a unique icon which is a throwback from a few versions older. Make that folder before you set up the user configuration file described next.
You have to make a few additional tweaks to get the ~/Sites folder back up and running. Sites Folder Add a “username.conf” filed under: /etc/apache2/users/ If you don’t already have one (very likely), then create one named by the short username of the account with the suffix.conf, its location and permissions/ownership is best tackled by using the Terminal, the text editor ‘ nano‘ would be the best tool to deal with this. Osx-htaccess-override Also whilst here allow URL rewrites so your permalinks look clean not ugly. Uncomment in httpd.conf – should be uncommented on a clean install. LoadModule rewrite_module libexec/apache2/mod_rewrite.so PHP 5.6.24 is loaded in the build of macOS Sierra and needs to be turned on by uncommenting a line in the httpd.conf file.
Sudo nano /etc/apache2/httpd.conf Use “control” + “w” to search within nano and search for ‘php’ this will land you on the right line then uncomment the line (remove the #): LoadModule php5_module libexec/apache2/libphp5.so Write out and Save using the nano short cut keys at the bottom ‘control o’ and ‘control x’ Reload apache to kick in sudo apachectl restart To see and test PHP, create a file name it “phpinfo.php” and file it in your document root with the contents below, then view it in a browser. The macOS Sierra Public Beta’s didn’t play well with MySQL 5.7.x, but these issues are now resolved by using MySQL 5.7.16 MySQL doesn’t come pre-loaded with macOS Sierra and needs to be. The latest version of MySQL 5.7.16 does work with the public release of macOS. If you already have MySQL 5.7 and you have upgraded OS from El Capitan to Sierra I expect that to be ok, but will be interested if anyone comments on that.
Use the Mac OS X 10.11 (x86, 64-bit), DMG Archive version (works on macOS Sierra). If you are upgrading from a previous OSX and have an older MySQL version you do not have to update it. One thing with MySQL upgrades always take a in case things go south and before you upgrade to macOS Sierra make sure your MySQL Server is not running. When downloading you don’t have to sign up, look for » No thanks, just take me to the downloads!