Yes, it's definitely possible to have the alive.cfg in thr root directory; I do it like that when using my home PC for hosting and have full WarRoom acccess that way; could even successfully server save&exit a unit-heavy mod-stuffed mission yesterday. But, well, for performance in that kind of mission the rented dedi would be better of course...

Will create new .rpt's on the rented server now and post them here.

Here they come; client .rpt and server .rpt:

https://www.dropbox.com/s/ttitwsuw5mj3oc3/tourist_rented_dedi_rpt_files_3.7z?dl=0

I noticed that the server time is two hours earlier than my system time on the client PC. Is that simply because it's located in another timezone or may this hint towards a possible problem linked to the failing connection with WarRoom?

Yep, that's the IP I have registered in War Room. So lez hope Tupolev can shed some more light on the issue.

Are you sure that the server uses that IP to connect to Warroom? Some have more IP addresses for incoming traffic but use another for outgoing. Your provider could have some answers. They can give you the hostname also.

And you have a VPN to your server? I saw you logged in with an internal IP address (192.168.x.x).

Well, the router firewall of my home PC works with port forwarding. I have set it up to forward ingoing and outgoing traffic for the ports that ARMA and steam are using. If I host a game using my home PC and give my external IP to my buddies, they can join my server e.g. via ARMA quick connect or steam invitation. I can myself also join other peoples servers. So I guess the data lane is open on the relevant ports. I have successfully played+saved+reloadec ALIVE missions with a buddy and myself as players. Only the performance was bad if using own PC for hosting dedi AND playing...

Now with the ALiVE update out of the way I'd be glad if one of the Devs could find the time to help me with my questions regarding the usage of ALiVE on a rented dedi server that has no machine name.

See you soon here in the thread; meanwhile I'm going to try if it still works on my home PC and, well, ORBAT around a bit...

@Tupolov: that 92.217.186.87 is the IP of my home PC - the client when using the rented dedi. Still, I'd like to know if I really need to have a machine name or not.

When hosting with my home PC as dedi, everything is ok BTW; had a succesful server-save-and-exited session again today - only, that I miss the performance leap that a rented dedi would give me ;-)

@Tupolov: you mean this is a machine name or machine adress? So I should register the rented server with

46.228.198.108 as IP

and

37.157.251.47 as machine name?

But still, do I NEED to type in a machine name at all or not? And if so, which of the numbers from the logs could be that machine name?

Sorry for being so thick... :-(

Ah, thx for making that clear. Now I can test with that IP you dug out of the logs. So I can simply type anything I want in the field hostname?

Well, I fired up the Quickstart mission, but no connection to WarRoom established even though I had changed the rented server to use the new-found "hidden" IP 37.157.251.47...

WOOHOOO!!!

It does work, fi-na-fucking-ly!

Only, it is still the original IP I have to type in, that one: 46.228.198.108 - LOL!

I guess the 1.2 version of ALiVE makes this finally possible or my rented server provider has changed something regarding internal and external IP after I sent them my error reports as well. I did exactly the same as in all that failed tests before, only now it works.

Another thing I noticed in general also while playing this today and even while playing ALiVE mod-heavy missions hosted on my own PC after the release of ALiVE 1.2 as substitute as long as this issue here was not solved, and hats off to that, is a slight performance increase across the bank. The saving process definitely is faster than in previous versions.

Thank you for your dedication in improving the code of that awesome mod, and thank you for your patience and helpful advice in this thread and others like it!