[Help] Warz online server in virtual machine

[lluk12]

SOLVED

Hi everyone,
so after trying quite a lot of times I can't still set up my server online. I followed this tutorial http://forum.ragezone.com/f791/tutor...erver-1010574/ and I did everything as said in here but in a Virtual machine (VMware player).
Since I want to make it public and I have a router I installed DUC (no-ip) in my virtual machine, I set a host in it and now when you put warzdns.ddns.net it gets redirected to my public ip. So in all the files where I had to replace 127.0.0.1 and Localhost I replaced them with this dns adress.
After that I opened my ports for the local ip of the virtual machine (which is bridged by the way), so let's say that the ip of my virtual machine is 192.168.1.40. I opened the ports: 80(tcp), 443(tcp), 1433(udp), 34000-34020(udp) for this internal ip.
So all should be done correctly then. When I open the MasterServer.exe I think I get what I should, the problem comes when I open the Supervisor.exe

Here there are some pictures

MasterServer:



Supervisor server:



I saw another post where someone had a similar problem and he posted the solution but it was in portuguese and I can't understand anything, here the post: http://forum.ragezone.com/f792/help-...g-vps-1026658/

Thanks, hope someone can help me

[MentaL]

[m70b1jr]

Make sure your supervisor.cfg is edited

[lluk12]

yes it is :/

I suppose you mean the supervisorserver.cfg right?

[GigaToni]

Maybe this helps you:
http://www.rocksclusters.org/roll-do...4.3/x1090.html

[lluk12]

Thanks for answering but I don't find any solution in there.
The virtual machine is already bridged by default (you can choose that on vmware player network config) and has the ip 192.168.1.47. This bridging makes as if the vm was physically connected to the network.
So knowing that the ip is 192.168.1.47 just opening the ports for that ip it should work. But it doesn't so I must be missing something

[GigaToni]

Your

masterIp = 127.0.0.1

can be localhost. Because it's only if you're running a cluster. Something like this:

MasterServer -> 88.88.88.88
---------------------------------------------
SuperVisor GER -> 85.115.128.83
SuperVisor US -> 89.115.12.15
SuperVisor RU -> 60.39.118.13

Then you'll need to change the master server ip to 88.88.88.88 but If you're running MS & SV on the same machine it can be localhost.

[lluk12]

What do you mean by masterIp = 127.0.0.1?

I'm running the ms and sv on the same machine as you say, but I don't understand what you are telling me to change. The masterserver.cfg? or the supervisorserver.cfg? or all the .cpp and .cfg files?

[GigaToni]

supervisorserver.cfg

change the line

masterIp = XXXX

to

masterIp = 127.0.0.1

[lluk12]

Okey I get what you are saying now :D thanks

Now after opening supervisorserver.exe it can connect to masterserver and it opens another window but I still have a problem

Supervisor:



GameServer:

[GigaToni]

Search in the source for "Getting shop data" and verify the ips etc.

[lluk12]

I checked all the ips and I think all are fine, also I found the error codes at WOBackendAPI.h
Error 8 is: http connection

Edit:

If i go to 127.0.0.1/api/api_GetShop1.aspx it actually enters the website so it's working

Edit2:

If i put myddns.ddns.net/api/api_GetShop1.aspx in my other computer (same network) it doesn't work, also 192.168.1.35/api/api_GetShop1.aspx doesn't work while if someone of another network (my friends in their home) enter to: myddns.ddns.net/api/api_GetShop1.aspx it works for them and see my webpage

And yeah, in the same computer 127.0.0.1/api/api_GetShop1.aspx works perfectly

[arczyx]

There's something pretty simple that you missed. You opened the ports right? Did you forwarded them for your vm too?

[lluk12]

I don't think there is an option like that in VMware player
although other people can connect to myddns.ddns.net/api/api_GetShop1.aspx and they get a sever answer, also if they connect to myddns.ddns.net they see the IIS welcome page. And I didn't forward any port to my virtual machine, I just opened them in the router

EDIT:
This problem has been solved, just had to delete the 2 ip lines in wz/bin/game.ini
I can't remember the lines but it was something like:
ip_masterserver 127.0.0.1
ip_api 127.0.0.1