US EN
ES ES
  • support center
  • quick start guides
  • View Website
  • Support Center
  • Quick Start Guides
  • Store
  • Free Trials
EN
US EN
ES ES
  • Home
  • Error Message Repository

Error 125 - Communication error (Unknown error)

  • Error Message Repository
This article contains troubleshooting information

Error 125: Communication error (Unknown error)

Source-Connect | 3.8 | Windows

Description

Even after correctly configuring port forwarding and running a successful port test, users get this error during sessions:

For this error on Mac, please review https://support.source-elements.com/source-connect/error-124-communication-error instead.

Cause

  1. The most common cause is a firewall or network error. Getting this error generally means that you are on a strict network that is blocking certain types of TCP communications and is preventing Source-Connect from communicating with our servers. This is usually TCP port 5222 or 80 depending on your settings, contact us if you are not sure. Contact the support team if you need the full list of server IP addresses and ports that must be open.
  2. Certain errors occurred while creating the Jabber connection; Lack of network resources, port 5222 is closed.
  3. You have entered an incorrect username.
  4. This might be an issue with your account. In that case, contact support.

Actions

  • Make sure you check you are logging in with the correct username.
  • Try to log back in and send logs to tech support.
  • If you have IT support, ask them for assistance. Give them the Network Guide to understand the requirements for Source-Connect.
  • This command can be helpful to understand the issue as it is very low level. 
    1. First, send a message to our support@source-elements.com team for access to the Network Services document. You will get the SIGNALLING_IP_ADDRESS (communications server load balancer) from that document. 
    2. Download and install Wireshark, and ensure that dumpcap is in your system's path variable. 
    3. In a Command Line: dumpcap -i “INTERFACE NAME” -w signalserver.pcap -f “src host SIGNALLING_IP_ADDRESS” | Tee-Object -FilePath “$env:USERPROFILE\Desktop\signalserver.dm”. 
      1.  “INTERFACE NAME” should be the name of the network interface you want to capture traffic for (for e.g.: “Ethernet”, “WiFi”, etc).
    4. Start Source-Connect and reproduce the issue.
    5. Open a Command window and interrupt the command by pressing Ctrl+C.
    6. Send the signalserver.dm file created on Desktop to support@source-elements.com.
    7. Our engineering team will review this, if you need further assistance.

Otherwise, please Contact our Support team.

Was this article helpful?

Yes
No
Give feedback about this article

Table of Contents

Description Cause Actions

PRODUCTS

  • Source-Connect™ 4 Hub
  • Source-Connect™ 4 Talent
  • Source-Connect™ 4 Studio/Facility
  • Source-Connect™ Standard 3.9
  • Source-Connect™ Pro & Pro X 3.9
  • Source-Live™ Pro LL
  • Source-Nexus™ Suite
  • Source-Nexus™ Control Panel
  • Source-Nexus™ Gateway
  • Source-Nexus™ I/O
  • Source-Nexus™ Mute-On
  • Source-Nexus™ Review
  • Source-Nexus™ Router
  • Source-Stream™

ACADEMY

  • Source-Connect 4 Talent Course
  • Advanced Remote Recording for VO Artists
  • Source-Connect 4 Studio/Facility Course
  • Source-Nexus I/O 1.3 Free Introductory
    Course

ILOK AND LICENSES

  • iLok Documentation
  • Licensing Documentation

POLICIES

  • Network Access and Support Contract Policies
  • Technical Support Terms and Conditions
  • Technical Support Disclaimer
  • Source Elements Terms and Conditions
  • Source Elements Privacy Policy
  • Source Elements Purchase Policy
  • Source Elements Refunds Policy
  • Source Elements Cookies Policy

GET LIVE SUPPORT

  • Purchase Support
  • Book a session
  • Contact us for support

ABOUT US

  • Meet the team!

Copyright © 2025. Source Elements. All rights reserved.


Expand

  • Error Message Repository

Was this article helpful?

Yes
No
Give feedback about this article