1. Home
  2. Knowledge Base
  3. Ghostlab: Troubleshooting
  4. I have trouble setting up WordPress…

I have trouble setting up WordPress…

This article describes a sample set up of WordPress via Ghostlab, and emphasizes some of the most common pitfalls.We have our local computer (192.168.0.13) running both WordPress and Ghostlab. Wordpress runs at the URL http://192.168.0.13:8888/wordpress. Ghostlab runs locally on port 8001, so its URL is http://192.168.0.13:8001.

In order to set up WordPress via Ghostlab, we did the following:

  1. Used our browser to navigate to the WordPress instance: http://192.168.0.13:8888/wordpress
  2. Once the site has loaded, we dragged the URL from the browser and dropped it on the Ghostlab site list, thereby creating a new entry. (Note: we could also have used the Add dialog, but the drag-and-drop is more convenient and less error-prone, as you don’t have to type in a long URL)
  3. Once the site entry has been created in Ghostlab, we started the Ghostlab server for this site by clicking the Play button
  4. We then opened a new browser tab by clicking the green launch button
  5. Done – WordPress is now running through Ghostlab.

Important notes:

  • Make sure that the WordPress address matches the Ghostlab site root. In the example above, they are both “http://192.168.0.13:8888/wordpress”. If we were to use “localhost:8888/wordpress” as the Ghostlab site root, the setup would not work because Ghostlab could not properly rewrite the link URLs
  • If you are using hostnames for your local test setup (e.g. by using MAMP Pro, or directly editing the /etc/hosts file, such that you could enter the url “http://mydev.site”, and this would point you to your local machine), please note that this can cause problems for devices connecting to Ghostlab via the network (e.g. a phone or tablet). It is safer to only use IP addresses to denote sites in Ghostlab that are known to all devices within the network. In the case of our example, this would mean that we should not use ‘localhost’ or any alias, but always ‘192.168.0.13’ as the host.

Was this article helpful?

Related Articles