CowboyPilotUSA

Tried that as well. Both with BindAddress having 0.0.0.0 (which happens if you don't apply it at all based on the console logs), and setting it to the same as publicAddress. I've also had the IP for public address set, no difference. The server still appears in either scenario and the errors clients get on connection are the same. a2s is not what should be 0.0.0.0 based on the BI instructions/wiki. However, I tried it with the a2s address as 0.0.0.0 and had the exact same result. Is that what you have in your server config settings?

Our server shows up and its successfully started. We have all the proper port handling and configuration in place, but all clients get "Kick cause code: group=1 'REPLICATION', reason=3 'CONNECTION_FAILURE'. Bind address is not set and is 0.0.0.0. Using standard port 2001 and 17777 respectively. All UDP port forwarding is set, and server appears in the listing. xxx in IP address for privacy. Any help here would be appreciated. This is being run on a bare metal server with Windows 2019. Confirmed fully updated with SteamCMD. { "publicPort": 2001, "a2s": { "address": "135.148.150.xxx", "port": 17777 }, "game": { "name": "EDITED FOR PRIVACY", "password": "", "passwordAdmin": "EDITED FOR PRIVACY", "scenarioId": "{C700DB41F0C546E1}Missions/23_Campaign_NorthCentral.conf", "maxPlayers": 64, "visible": true, "supportedPlatforms": ["PLATFORM_PC","PLATFORM_XBL"], "gameProperties": { "serverMaxViewDistance": 1600, "serverMinGrassDistance": 50, "networkViewDistance": 1500, "fastValidation": true, "battlEye": true, "disableThirdPerson": false, "VONDisableUI": false, "VONDisableDirectSpeechUI": false, "missionHeader": {} } }, "operating": { "lobbyPlayerSynchronise": true, "playerSaveTime": 120, "aiLimit": 100, "slotReservationTimeout": 60 } }