Hi all sorry to bother you guys but I ran out of ideas. I use a rented dedicated server through Jestservers. Jest has experience with ALiVE and set up the server. When I run the mission it will not let me connect to war room.

[2016-11-12 18:10:50] [info] Reading 'alive.cfg'
[2016-11-12 18:10:50] [info] Configuration found: C:\Users\206.217.128.102302\AppData\Local\ALiVE\alive.cfg
[2016-11-12 18:10:50] [info] No URL in config. Using default.
[2016-11-12 18:10:50] [info] Configuration 'alive.cfg' read OK.
[2016-11-12 18:10:50] [debug] Alive Config:
[2016-11-12 18:10:50] [debug] Type: JSON
[2016-11-12 18:10:50] [debug] User: vonyvenafixyhafojuhatigajupevo5a
[2016-11-12 18:10:50] [debug] Pass: xxxxxxxxxxxxxxxx
[2016-11-12 18:10:50] [debug] Group: 913TFS
[2016-11-12 18:10:50] [debug] URL: http://db.alivemod.com:5984
[2016-11-12 18:10:50] [info] Checking WarRoom access...
[2016-11-12 18:10:50] [info] URL: http://alivemod.com/api/authorise?&group=913TFS
[2016-11-12 18:10:50] [error] ###### HandleMessage - StartALiVE ######
[2016-11-12 18:10:50] [error] Error: You are not authorized to access ALiVE War Room with this account. Check IP and Groupname.
[2016-11-12 18:10:50] [error] RAW: StartALiVE ['true']
[2016-11-12 18:10:50] [debug] Return value [['StartALiVE','ERROR','You are not authorized to access ALiVE War Room with this account. Check IP and Groupname.']]

I've checked the IP and Group name, I've deleted the group and created a new one, I've done the set up step by step. Both Jest and I tried a few fixes from the solved posts on the forum and nothing worked. I am wondering if there is a different IP that is trying to connect to War room not the one I use on my rented dedi. Could you check your logs?

The IP I have registered on war room is 206.217.128.10. Thanks guys

@Tupolov helped me with this issue. Maybe the helpful samaritan will do so again? He checked/changed to the correct IP for me. As you say, different IP tried to connect to war room.

I'm hoping so. I'm all out of ideas

Hey Aladeen, did you see my other post? RE:
###
Ok, I figured it out.

I found the #debug von output. (on gameservers.com the log filename is set in config and writes to the config folder in Arma3 Root). Check your config file for what the log file is set to.

In the debug output look for IP address listed as private like :
Private: 108.61.104.XX

There were two "Private" listings, one was my local machine address (192.168.x.x) and the other was close to my server IP. Updated War Room info with that IP and voila!
###

Hope that helps.

Yes thank you for the info. My server host was able to get me the connecting IP and it just started working. Thank you so much for the info that helped out a lot!