The Vivox SDK error VxErrorInternalError (1004) occurs when sign-in fails due to inability to establish server connections, often caused by no internet or firewall restrictions blocking required ports, protocols, or IPs. Network administrators should ensure all Vivox-required IPs, ports, and protocols are allowed, especially in controlled office environments.
Symptoms:
The Vivox SDK status code VxErrorInternalError (1004) can occur when failing to successfully sign in a local user.
Note: In older SDKs, this error may be reported as status code 5007.
Cause:
There are a several possible causes for a VxErrorInternalError (1004) error during the sign in process, but each share in common a failure to establish server connections, open sockets, or other similar symptoms of not having an internet connection.
Resolution:
Outside of not having an active, stable internet connection at all, the most common cause for this issue is a firewall configuration which does not allow certain ports or protocols to be used, or which restricts certain types of connections to IP addresses that aren't explicitly permitted in an allowlist. This is especially a consideration for office settings which tend to have more tightly controlled network environments compared to home internet. Firewall issues are far less common for end users.
Please refer your network administrator to the following support article, which lists all the current IPs, ports, and protocols which must be open and available in order to use the Vivox service correctly:
Please review and apply exceptions for this list carefully. Even if one type of machine on the network works normally (consoles or PC), it does not necessary mean that firewall restrictions aren't in play to prevent connections from the other machines.