Worship Connection & Troubleshooting

Overview

WeConnect Studio runs an in-app WebSocket server (default port: 8765) that broadcasts lyrics, chord sheets, and current slides to musician tablets and devices running the WeConnect Worship mobile app on the stage.

However, because the connection happens over your local Wi-Fi network, security policies or network settings can sometimes prevent the mobile app from connecting. Follow the troubleshooting steps below to resolve connection issues.

1. Configure Windows Defender Firewall

By default, Windows Defender Firewall blocks incoming network requests on unrecognized ports to protect your computer. You must allow incoming traffic on port 8765.

1. Open the Windows Start Menu, search for "Windows Defender Firewall with Advanced Security", and open it.
2. Click on Inbound Rules in the left sidebar.
3. Click New Rule... in the right-hand Actions panel.
4. Choose Port and click Next.
5. Select TCP, choose Specific local ports, enter 8765, and click Next.
6. Select Allow the connection and click Next.
7. Ensure all network profiles (Domain, Private, and Public) are checked to ensure connection capability at your church's Wi-Fi network. Click Next.
8. Give the rule a name (e.g., WeConnect Studio Worship Server) and click Finish.

2. Check Wi-Fi Router Client/AP Isolation

Many modern dual-band routers, especially public or church Wi-Fi systems, have a security feature enabled called AP Isolation, Client Isolation, or Guest Mode.

• The Problem: When enabled, this feature prevents Wi-Fi devices from communicating with other local devices directly, even if they are on the same network subnet. It allows devices to access only the gateway and the internet.
• The Test: Open a command prompt on your laptop, look up your tablet/phone's local IP address (in the mobile app settings or Wi-Fi settings), and try to ping it (e.g. ping 192.168.100.15). If the ping request times out or is unreachable, your router is isolating the devices.
• The Solution: You will need to access your router's administration portal (or contact your church's IT department) and **disable client/AP isolation** or set up a dedicated media network where local device communication is allowed.

3. Handle Multiple Network Adapters (IP Mismatch)

If your computer uses virtual adapters (VMware, VirtualBox), a local VPN (like Tailscale/ZeroTier), or is connected to both Ethernet and Wi-Fi simultaneously:

• The Problem: The automatic IP detection inside Studio might pick up one of these virtual interfaces and show an incorrect connection address on the screen (e.g. a VPN address starting with 10.x.x.x or VirtualBox address 192.168.56.x).
• The Solution: Find your active Wi-Fi IP address manually:
  1. Open a Command Prompt (cmd) on the Studio computer.
  2. Type ipconfig and press Enter.
  3. Find your active **Wireless LAN adapter Wi-Fi** section.
  4. Copy the **IPv4 Address** (typically 192.168.100.x or 192.168.1.x) and enter it directly in your mobile app connection prompt.

4. Dual-Band Networks

Make sure both your presentation laptop and the worship team's mobile devices are connected to the exact same Wi-Fi SSID. Connecting one device to a 5 GHz network and another to a separate 2.4 GHz Guest SSID can place them in different subnets that cannot route traffic to each other.