Fork me on GitHub

WordPress-kehittäjä, älä missaa ilmaista webinaariamme WordPressin hakutoiminnosta tammikuun 14. päivä!

WordPress-utvecklare, missa inte vår gratis webbinar om sökningen in WordPress den 14. januari!

WordPress developer, don't miss our free webinar about search in WordPress on January 14th!

Debugging steps

  1. Find the VirtualBox and Vagrant versions. Make sure they are up-to-date and fit the requirements.

  2. Make sure you have installed Vagrant from the source specified in installation guide. If you haven’t, remove all Vagrant related software and follow the guide.

  3. Examine the common issues to see if you can find a match. Check the Seravo/wp-vagrant and Seravo/wordpress GitHub repositories to see if the issue has been already reported.

  4. Complete a thorough Vagrant cleanup and test with an empty project.

Reporting an issue

After you’ve completed the debugging steps, you can either file a bug report or contact the Seravo customer service. If you need to include sensitive information with the report, the latter is recommended.

Include the following with your report to expedite the resolution of the problem:

Common issues


Running vagrant up for the first time fails with an error symlink(): protocol error on Windows.


Run Cygwin as an administrator when you are about to start a machine.

MacOS: /dev/vboxnetctl error during vagrant up


Running vagrant up fails with an error failed to open /dev/vboxnetctl on macOS.


Grant more permissions to VirtualBox via System Preferences > Security & Privacy > General. Finally, restart the VirtualBox service:

sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/ restart
sudo /Library/StartupItems/VirtualBox/VirtualBox restart
sudo launchctl load /Library/LaunchDaemons/org.virtualbox.startup.plist


Running vagrant up fails with an error related to creating host-only network adapters on Linux.


VirtualBox kernel modules might not be loaded. Run sudo vboxreload to reload the modules.

Linux: Networking issues or virtual interface errors


Running vagrant up fails with an interface-related error, or networking fails. Known to affect Ubuntu 17.04 and later.


Make sure ifconfig and route commands exist. On Ubuntu, install them with sudo apt-get install net-tools.

Linux: Ruby header files error during vagrant up


Running vagrant up fails with an error mkmf.rb can't find header files. Known to affect Ubuntu 16.04 and later.


Install the Ruby development files. On Ubuntu, run sudo apt-get install ruby-dev.