Hello, everyone! Today is an exciting day for the Mac community. OS X Yosemite is officially available for everyone to download and install! Because of that, I just wanted to take a few moments and write about the state of VirtualHostX on Apple's latest OS.
In short, the good news is VHX is updated and ready to go! We've got a brand new version 6.0 built just for Yosemite. You can download version 6.0 here.
VirtualHostX 6.0 is a FREE upgrade for all registered users of version 5.0. Your existing license will work with the new version. There's no need for a paid upgrade. If you're running version 4.0 or earlier, you can upgrade to the latest version here for 50% off.
After upgrading to Yosemite, if you're using Apple's built-in Apache server, open VirtualHostX and re-run the Setup Wizard. It's located under the "VirtualHostX" menu. Then click "Apply Changes" and restart Apache.
If you're getting 403 Forbidden errors when viewing your websites, you'll need to add the following line to your
Directory custom directives for each virtual host...
Require all granted
This will prevent Apache from giving you a 403 Forbidden error. More details here.
Make sure you click "Apply Changes" after adding that line to your virtual hosts.
In the future, you can instruct VirtualHostX to automatically add that line by following these instructions.
If you're using MAMP on Yosemite, none of the above steps will likely be necessary.
Some users are reporting that when they download and open VirtualHostX, they get an error saying the app is "Damaged and should be moved to the trash". This is because of some new "code signing" changes by Apple in the latest version of Mavericks and Yosemite. I'm looking into the problem and trying to solve it as quickly as possible.
Until then, you can work around the problem in one of two ways:
1) Right-click on VirtualHostX and choose "Open" to launch the app.
2) Or, you can go into System Preferences and click on "Security" and change "Allow Downloaded Apps From" to "Anywhere". But, PLEASE, only change that setting if you are sure of what you're doing. The first option is likely the best solution for most users.
In recent years, I've tried to release major updates to VirtualHostX on a 12-18 month schedule. Lately, those new releases have come during the first part of the year. The downside to this is that I spend June through October making sure the current version of VHX is ready for Apple's latest OS X release in the Fall, then rush to get new features built in time for a major VHX release early in the year. It also causes me grief because that leaves me with multiple version of VirtualHostX supporting multiple versions of OS X.
Beginning with VirtualHostX 6.0, I'm going to time new releases to coincide every Fall with Apple's new release of OS X. And each new version of VHX will only support that version of OS X. My goal is to drastically reduce the complexity of the app by only targeting one version of OS X. For you, that means VHX 6.0 will be required for Yosemite. And, next fall, VHX 7.0 will be required for whatever new version of OS X Apple comes out with.
This shouldn't speed up or slow down the development pace of VirtualHostX, I'm just shifting the release date to make things simpler for me and for you.
As always, thanks so much for being a VirtualHostX customer. If you have any questions at all, feel free to get in touch.