Health Endpoint (`-i`) Not Working on macOS with Wireproxy Configuration

[pritam12426]

Problem:

The -i option for exposing the health status endpoint does not seem to work on macOS. When running wireproxy with the following command:

wireproxy -c ~/.config/wireproxy/wireproxy.conf -i "127.0.0.1:9080"

The server starts successfully, and the SOCKS5 and HTTP proxies bind to their respective ports (127.0.0.1:1080 and 127.0.0.1:8080). However, the health status endpoint (127.0.0.1:9080) does not respond to curl requests, and the check_wireproxy.sh script reports that the server is not running.

Configuration:

Here is the wireproxy.conf file used:

WGConfig = /Users/pritam/Downloads/wg.conf
LogLevel = info

[Socks5]
	BindAddress = 127.0.0.1:1080
	UDPForwarding = true  # Enables UDP for DNS resolution over SOCKS5

[http]
	BindAddress = 127.0.0.1:8080
	EnableMetrics = true

Step, which I have used:

1. Use the above wireproxy.conf file.
2. Run the following command:

   wireproxy -c ~/.config/wireproxy/wireproxy.conf -i "127.0.0.1:9080"

3. Check the health status endpoint:

   # Define the health status endpoint
   HEALTH_ENDPOINT="127.0.0.1:9080"
   
   # Check if the server is running
   if curl --silent --fail "$HEALTH_ENDPOINT" >/dev/null; then
       echo "Wireproxy server is running successfully."
   else
       echo "Wireproxy server is NOT running."
       exit 1
   fi

4. Observe that the health status endpoint does not respond.

Observed Behavior:

• The SOCKS5 proxy (127.0.0.1:1080) and HTTP proxy (127.0.0.1:8080) work as expected.
• The health status endpoint (127.0.0.1:9080) does not respond to curl requests.

Expected Behavior:

The health status endpoint should respond to curl requests and provide information about the server's health.

---

System Information:

• Operating System: Macbook air m2 with [OS: macOS 26.1 25B78 arm64]
• Wireproxy Version: wireproxy, version 1.0.9