Skip to main content

“SlipStream GUI is damaged” error

This is the most common macOS issue, caused by Gatekeeper security settings blocking unsigned applications.
Let macOS know you trust the application.
  1. Try to open SlipStream GUI (it will be blocked)
  2. Go to System SettingsPrivacy & Security
  3. Scroll down to the Security section
  4. You should see a message: “SlipStream GUI” was blocked from use because it is not from an identified developer
  5. Click “Open Anyway”
  6. Confirm by clicking “Open” in the dialog
You only need to do this once. macOS will remember your choice.
Bypass Gatekeeper for the first launch.
  1. Locate SlipStream GUI in Applications
  2. Right-click (or Control-click) on the app
  3. Select “Open” from the context menu
  4. Click “Open” in the confirmation dialog
After the first successful launch, you can open the app normally.
If all three options fail, the DMG file may be corrupted. Download a fresh copy from the releases page.

Binary execution permissions

The SlipStream client binary must be executable. The app handles this automatically, but you may need to verify manually if issues persist.
For Apple Silicon (M1/M2/M3):
ls -l /Applications/SlipStream\ GUI.app/Contents/Resources/binaries/slipstream-client-mac-arm64
For Intel Macs:
ls -l /Applications/SlipStream\ GUI.app/Contents/Resources/binaries/slipstream-client-mac-intel
The output should show -rwxr-xr-x (executable permissions).
If permissions are missing:Apple Silicon:
chmod +x /Applications/SlipStream\ GUI.app/Contents/Resources/binaries/slipstream-client-mac-arm64
Intel:
chmod +x /Applications/SlipStream\ GUI.app/Contents/Resources/binaries/slipstream-client-mac-intel
The app automatically sets these permissions on startup, but manual intervention may be needed if the app bundle was extracted incorrectly.
If you’re running the wrong binary for your Mac:Check your Mac’s architecture:
uname -m
  • arm64 = Apple Silicon (M1/M2/M3)
  • x86_64 = Intel
Download the correct version:
Apple Silicon Macs can run Intel binaries through Rosetta 2, but native ARM64 binaries perform better.

System proxy configuration

On macOS, system proxy configuration uses networksetup and may require administrator privileges.
When you enable “Configure System Proxy”, macOS will prompt for your administrator password.Why this happens:
  • networksetup requires admin privileges to modify network settings
  • This is a macOS security feature
  • The app does not store or have access to your password
If the prompt doesn’t appear:
  • The app will log an error
  • Configure proxy manually in System Settings
If automatic configuration fails:
  1. Open System SettingsNetwork
  2. Select your active network (Wi-Fi or Ethernet)
  3. Click Details
  4. Go to the Proxies tab
  5. Enable Web Proxy (HTTP) and Secure Web Proxy (HTTPS)
  6. Set Web Proxy Server: 127.0.0.1:8080
  7. Set Secure Web Proxy Server: 127.0.0.1:8080
  8. Click OK
The app automatically detects and configures the active network interface.Preferred interfaces (in order):
  1. Wi-Fi
  2. Ethernet
  3. USB 10/100/1000 LAN
  4. Thunderbolt Bridge
Check configured interface:
networksetup -listallnetworkservices
Manually configure a specific interface:
# Replace "Wi-Fi" with your interface name
networksetup -setwebproxy "Wi-Fi" 127.0.0.1 8080
networksetup -setsecurewebproxy "Wi-Fi" 127.0.0.1 8080
networksetup -setwebproxystate "Wi-Fi" on
networksetup -setsecurewebproxystate "Wi-Fi" on
If the system proxy remains configured after stopping the VPN:Disable proxy manually:
# Replace "Wi-Fi" with your interface name
networksetup -setwebproxystate "Wi-Fi" off
networksetup -setsecurewebproxystate "Wi-Fi" off
Check current proxy status:
networksetup -getwebproxy "Wi-Fi"
networksetup -getsecurewebproxy "Wi-Fi"
The app only disables proxy configurations it created (pointing to 127.0.0.1:8080).

macOS-specific logs

Access detailed logs for debugging:
View console logs:
  1. Open Console.app (Applications → Utilities → Console)
  2. Select your Mac in the sidebar
  3. Filter for “SlipStream GUI”
Common log locations:
  • Electron logs: ~/Library/Logs/SlipStream GUI/
  • Settings file: ~/Library/Application Support/SlipStream GUI/settings.json
Check networksetup output:
# View all network services
networksetup -listallnetworkservices

# Check proxy configuration
networksetup -getwebproxy "Wi-Fi"
networksetup -getsecurewebproxy "Wi-Fi"

# Check proxy bypass domains
networksetup -getproxybypassdomains "Wi-Fi"
Check if ports are in use:
sudo lsof -i :8080
sudo lsof -i :5201
Kill processes using ports:
sudo lsof -ti:8080 | xargs kill -9
sudo lsof -ti:5201 | xargs kill -9

Sharing VPN over Wi-Fi

Share your VPN connection with iOS devices on the same network.
Option 1: Terminal
ifconfig | grep "inet " | grep -v 127.0.0.1
Option 2: System Settings
  1. Open System SettingsNetwork
  2. Select your Wi-Fi connection
  3. Your IP address is shown (e.g., 192.168.1.100)
  1. On iPhone/iPad: SettingsWi-Fi
  2. Tap (i) next to your network
  3. Scroll to HTTP ProxyManual
  4. Server: Your Mac’s IP (e.g., 192.168.1.100)
  5. Port: 8080
  6. Tap Save
If iOS can’t connect, check your Mac’s firewall:
  1. System SettingsNetworkFirewall
  2. Ensure firewall allows incoming connections on port 8080
  3. Or temporarily disable firewall to test
Allow port 8080 via Terminal:
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --add /Applications/SlipStream\ GUI.app
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --unblockapp /Applications/SlipStream\ GUI.app

Other macOS issues

The app should appear in the Dock when running. If it doesn’t:
  1. Check Activity Monitor for “SlipStream GUI” process
  2. Try force-quitting and reopening
  3. Reinstall the application
If the DMG file won’t open:
  1. Download the DMG again (may be corrupted)
  2. Try mounting manually:
    hdiutil attach ~/Downloads/SlipStream-GUI-macOS-*.dmg
    
  3. Check disk permissions:
    diskutil verifyVolume /
    
If the app crashes immediately:
  1. Check Console.app for crash logs
  2. Reset settings:
    rm ~/Library/Application\ Support/SlipStream\ GUI/settings.json
    
  3. Reinstall from a fresh download
For issues not covered here, see Common issues or open an issue on GitHub.

Build docs developers (and LLMs) love