ServBay Frequently Asked Questions (FAQ)

When using the ServBay local web development environment, developers may encounter various issues. This document addresses two of the most common questions: upgrading ServBay Runtime and resolving problems with accessing local websites when using proxy tools like ClashX Pro.

How Do I Upgrade ServBay Runtime?

ServBay Runtime is the core component of ServBay and is crucial for ensuring the stable operation of ServBay and its hosted services. When a new version is released, ServBay will prompt users to upgrade upon launch. Keeping the Runtime updated helps improve ServBay’s overall performance, stability, and compatibility.

To upgrade ServBay Runtime, follow these steps:

1. Launch the ServBay application.
2. In the left navigation bar of the ServBay window, select Packages > General Services.
3. In the right panel, locate the ServBay Runtime entry.
4. If an update is available, ServBay Runtime will display a yellow upgrade prompt or an upgrade button. Click the yellow upgrade button.
5. ServBay will begin downloading and installing the latest version of the Runtime. Please wait patiently for the upgrade to complete.

After the upgrade, ServBay Runtime will be running the latest version, providing improved stability and performance.

Why Can't I Access Local ServBay Websites After Using ClashX Pro (or Other Proxy Tools)?

Many developers use ServBay for local development and testing, often configuring custom local domains (such as servbay.demo, myproject.servbay.demo, etc.) that typically resolve to the local loopback address 127.0.0.1.

When using ClashX Pro or other VPN/proxy tools (like Surge, Quantumult X, etc.), these tools may intercept or redirect DNS requests, forcing all domain name lookups through their proxy servers. This behavior can bypass the operating system’s native DNS resolution process and the local hosts file (which ServBay relies on for resolving local domains), causing local development domains configured in ServBay not to properly resolve to the local IP address. As a result, you won’t be able to access your local website.

To resolve this issue, you need to add rules in your proxy tool’s settings to tell it NOT to proxy or hijack DNS requests for your local development domains. This is usually accomplished by configuring a “bypass proxy”, “ignore proxy”, “whitelist”, or “exclusion list”.

Taking ClashX Pro as an example, configure it as follows:

1. Open the ClashX Pro application.
2. In the macOS menu bar, find the ClashX Pro icon, click it, then choose More Settings.
3. In the settings window, navigate to the General tab.
4. Locate the input box labeled Ignore proxy settings for these hosts and domains (or a similarly named option).
5. Add your local development domains to this list. To cover the most common ServBay local domains, it’s recommended to add localhost, 127.0.0.1, and the specific domains or wildcard domains you use in ServBay. For example, if your local domains end with .servbay.demo, you can add *.servbay.demo. Entries are usually separated by commas , or line breaks. A typical configuration might look like:

   localhost, 127.0.0.1, *.servbay.demo, yourproject.servbay.demo

6. Save your settings and, if prompted by ClashX Pro, reload or apply the configuration for changes to take effect.

(Illustration: Configuring ignored hosts and domains in ClashX Pro)

After completing the above configuration, ClashX Pro will no longer interfere with resolution of these specific local domains, and your ServBay local site should be accessible as expected. If you still encounter issues, make sure you have correctly configured the domain in ServBay’s Sites settings, and that relevant ServBay services (such as Caddy or Nginx) are running properly. You can also use terminal commands like ping yourproject.servbay.demo or dig yourproject.servbay.demo to further diagnose domain resolution.