Start by identifying the symptom. Use DNS only when the FiveM NUI is stuck at “Connecting…”; otherwise check channel state, logs and the integration.
Use DNS only for the documented NUI case
If the FiveM NUI is stuck at “Connecting…”, run nslookup lh.v10.network on the affected client. The SaltyChat FAQ says it must resolve to 127.0.0.1 when no proxy is used. If it does not, check the client resolver or add a router DNS-rebind exception only for the exact host lh.v10.network; never disable DNS-rebind protection globally, and remove the exception when the integration is no longer used.
Check the actual voice-channel state
For a player who can connect but cannot move, verify the configured TeamSpeak server identity, in-game channel ID and password, the player’s current TeamSpeak channel, and the server-side action that requests the move. Compare these values with the active SaltyChat configuration before changing commands or permissions.
Collect logs before guessing
Enable SaltyChat Expert Mode with Extensive log level in the TeamSpeak client, reproduce one switch attempt, and keep the corresponding server console output. The FAQ identifies the TeamSpeak live log and the client log directory. Remove passwords, tokens and personal identifiers before sharing logs.
Verify the FiveM integration
The documented integration starts saltychat; start saltyhud only if you installed and use the optional HUD. The saltychat resource uses config.json for values such as VoiceEnabled, ServerUniqueIdentifier, IngameChannelId and IngameChannelPassword. Confirm that the running resource and config belong to the same deployment, then test a single controlled move after every correction.
Primary sources: SaltyChat FAQ, commands documentation and FiveM integration repository.
Reference documentation
Source: SaltyHub-net/saltychat-docs · Source: SaltyHub-net/saltychat-fivem