The War-Z and Hamachi w/o M$ IIS!

[aLca]

1st of all; Credits goto all the PPL who works on the Z Source.


2nd of all; Credits goto hatsiepatsie, he makes the Original Tutorial for Abyss Webserver.
2,1nd of all; Theese steps that have i documented are the same who work's fine on my machine.


3nd of all; It's most likley the Critical Step; READ WHIT CARE! IF U NOT SURE ABOUT SOMETHING, GET YOUR TIME, THINK ABOUT I't!


4nd of all; If you can't handle it to to get This Build UP&RUNNING! or something similar Source! Stop Reading, be serious, Stop wasting your Time


5nd of all; At least but not last, this REQUIRES a working Instance of Microsoft SQL Server 2008 R2 (SP3), i will NOT Explain it here howto set that Up


6nd of all; IF YOU PLAN TO MAKE PROFIT WHIT THIS TUTORIAL GO AND **** UR SELF!

-------------------------------------------------------------------------------------------------------


AT LEAST MAKE SURE YOU'RE BEFORE U BUILD ANYTHING AT THE SOURCE CODE THAT YOU;


---> CLEAN UP <---


This means for Example: Build -> Clean Solution <- before hitting BUILD SOLUTION!




AND ALSO MAKE SURE, IF U'RE USING NO VPN TOOL'S LIKE HAMACHI AND OR TUNNGLE TO OPEN YOUR PORTS 34000,34001 and 34010 RIGHT ON YOUR FIREWALL FOR TCP and UDP! THX to FUZZY!


-------------------------------------------------------------------------------------------------------​

Step 1) [Seting up the Webserver for Port:80 w/o SSL]


Read This Post (by hatsiepatsie) Whit care(!) and Setup ur FIRST of TWO Abyss Webserver.!
After it's working on Port :80 (

To view the content, you need to sign in or register

) u should see from Now your Abyss Welcome Page.
Stop your Abyss Webserver.


Step 2) [Seting Up the new htdocs Folder]


Part 1;
Goto C:\
Create a Folder named htdocs
Go into that new Folder htdocs
Create a Folder named WarZ
Create a Folder named wz
Go into that new Folder WarZ
Create a Folder named api


Goto C:\Abyss Web Server
look for abyss.conf and open it up whit your Favorite Editor.
Hit CTRL+F search for the Line; <path> change it to ->

<path>
                C:\htdocs
</path>

Step 3) [Seting up the Webserver for Port:443 for SSL ONLY]


Part 1)
Navigate to your C:\Drive - you should see there a Folder named Abyss Web Server.
Copy and Paste that Folder it into C:\ and RENAME him to Abyss Web Server SSL.
Go into your fresh named Abyss Web Server SSL Folder, look for abyss.conf and open it up whit your Favorite Editor.
Hit CTRL+F search for the Line; "<port>" and change 9999 to 9998


It looks like; ---> DO NOT COPY PASTE THE CODE! IT WILL NOT WORK!!! <---

    <console>
       <port>
              9998
        </port>
        <bindip>
            *
        </bindip>
And so on...

After that, start abyssws.exe right in your Web Server SSL Folder.


Goto

To view the content, you need to sign in or register

Login whit your Login from Step 1


Search for SSL/TLS Certificates hit it
Private Keys: hit add


Name: MY_SSL_CERT
Action: hit Generate
Type: RSA 2048 bits
hit ok


Certificates hit add
Name: MY_SSL_CERT
PrivateKey (Dunno, most Likely MY_SSL_CERT shall popup there)
Type: Self-signed


Fill out the Lines (Just Fake bullsh*t)
hit ok


Certificate Signing Request: hit Generate
hit ok


Restart Abyss

Hit Configure
Hit General
[

To view the content, you need to sign in or register

]



Change Protocol to: HTTPS
Change HTTPS Port to: Default HTTPS Port (443)
Certificate: MY_SSL_CERT
Documents Path: C:\htdocs
hit ok
Stop Both Abyss Webserver




Goto C:\Abyss Web Server\
Hit abyssws.exe
Goto

To view the content, you need to sign in or register

Change it Like my Picture.


Goto C:\Abyss Web Server\SSL
Hit abyssws.exe
Goto

To view the content, you need to sign in or register

Change it Like my Picture.





Restart BOTH Abyss Webserver.


-------------------------------------------------------------------------------------------------------


Step 3) [Setting Up the Z Source for the correct IP]


Part 1)
Goto C:\WarZ\src\Scripts\WZBackend-ASP.NET
Open up WZBackend-ASP.NET.sln
Build Solution as !DEBUG!
Publish Website to
C:\htdocs\WarZ




Part 2)
Goto C:\WarZ\bin\build\update\
Open up Launcher.cfg
Replace every LOCALHOST whit your Hamachi IP
also
Replace every 127.0.0.1 whit your HAMACHI IP
Save


Part 3)


Copy C:\WarZ\bin\build\update\WarZLauncher.exe and Launcher.cfg to C:\WarZ\bin\WarZLauncher.exe and Launcher.cfg




Part 4)
Open up C:\WarZ\bin\build\updater
hit CreateUpdater.bat
Copy api_getserverinfo.xml to


C:\htdocs\




Part 5)
Open up C:\WarZ\bin\build\updater
Copy woupd.xml and WarZlauncher.exe_0.9.*.exe to


C:\htdocs\wz\updater




Open up C:\htdocs\wz\updater\woupd.xml


Make sure that it's look like;

<p>
 <u url="https://HAMACHI.I.P.1-2-3/wz/updater/WarZlauncher.exe_0.9.3.exe" crc="459183624" ver="0.9.3" size="8166400"/>
</p>

Part 6) [Building *.bin Files]


Read this Post whit Care! by DNC


For a Clean Client (To Release for Friends and so on) u can use this RSBuild.xml ->

How should it look like!

<build>
 <output dir="build\data"/>
 
 <cdn url="http://YOUR-HAMACHI-IP!1.2.3-1.2.3/wz/"/>

 <!--  set base archive for incremental update -->
 <base file="build\data\wz35040902"/> 


 <!-- include EULA file -->
 <include mask="eula-en.htm"/>
 <include mask="eula-en.rtf"/>
 <!-- excludes for this package files (just in case they was created in this dir -->
 <exclude mask="WZ_*.bin"/>


 <!-- excludes for debug files -->
 <exclude mask="r3dlog.txt"/>
 <exclude mask="MasterServer_ccu.txt"/>
 <exclude mask="*.pdb"/>
 <exclude mask="*.exp"/>
 <exclude mask="*.lib"/>
 <exclude mask="*.bat"/>
 <exclude mask="*.vmp"/>
 
 <!-- excludes for other binaries -->
 <exclude mask="Studio*.*"/>
 <exclude mask="MasterServer.*"/>
 <exclude mask="WZ_GameServer.*"/>
 <exclude mask="SupervisorServer.*"/>
 <exclude mask="RSBuild.*"/>
 <exclude mask="RSUpdate.*"/>
 <exclude mask="WZAdmin.*"/>
 <exclude mask="WarZ_unpack.exe"/>
 <exclude mask="*.log"/>
 <exclude mask="*.suo"/>
 <exclude mask="*.bat"/>
 <exclude mask="gameSettings.ini"/>
 <exclude mask="local.ini"/>
 <exclude mask="windows_error_report_mapping.xml"/>  
 <exclude mask="Launcher.cfg"/>
 <exclude mask="APEX_Common_Legacy_x86.dll"/>
 <exclude mask="APEX_Common_LegacyCHECKED_x86.dll"/>
 <exclude mask="APEX_Common_LegacyPROFILE_x86.dll"/>
 <exclude mask="APEX_Destructible_Legacy_x86.dll"/>
 <exclude mask="APEX_Destructible_LegacyCHECKED_x86.dll"/>
 <exclude mask="APEX_Destructible_LegacyPROFILE_x86.dll"/>
 <exclude mask="APEX_Destructible_x86.dll"/>
 <exclude mask="APEX_DestructibleCHECKED_x86.dll"/>
 <exclude mask="APEX_DestructiblePROFILE_x86.dll"/>
 <exclude mask="APEX_Framework_Legacy_x86.dll"/>
 <exclude mask="APEX_Framework_LegacyPROFILE_x86.dll"/>
 <exclude mask="APEX_Framework_LegacyCHECKED_x86.dll"/>
 <exclude mask="ApexFramework_x86.dll"/>
 <exclude mask="ApexFrameworkCHECKED_x86.dll"/>
 <exclude mask="ApexFrameworkPROFILE_x86.dll"/>
 <exclude mask="avutil-50.dll"/>
 <exclude mask="PhysX3CharacterKinematic_x86.dll"/>
 <exclude mask="PhysX3CharacterKinematicCHECKED_x86.dll"/>
 <exclude mask="PhysX3CharacterKinematicPROFILE_x86.dll"/>
 <exclude mask="PhysX3CHECKED_x86.dll"/>
 <exclude mask="PhysX3CommonCHECKED_x86.dll"/>
 <exclude mask="PhysX3CommonPROFILE_x86.dll"/>
 <exclude mask="PhysX3CookingCHECKED_x86.dll"/>
 <exclude mask="PhysX3CookingPROFILE_x86.dll"/>
 <exclude mask="PhysX3GpuCHECKED_x86.dll"/>
 <exclude mask="PhysX3GpuPROFILE_x86.dll"/>
 
 
  <!-- excludes for build directories -->
 <exclude mask="1"/>
 <exclude mask="build"/>
 <exclude mask="logs"/>
 <exclude mask="bin"/>
 <exclude mask="server"/>
 <exclude mask="tools"/>
 <exclude mask="logs"/>
 <exclude mask="logms"/>
 <exclude mask="logss"/>
 <exclude mask="logsv"/>
 
 
 <include mask="ApexFramework_x86.dll"/>
 <include mask="avcodec-52.dll"/>
 <include mask="avformat-52.dlll"/>
 <include mask="avutil-50.dll"/>
 <include mask="CrashRpt1301.dll"/>
 <include mask="cudart32_32_16.dll"/> 
 <include mask="dbghelp.dll"/>
 <include mask="fmod_event.dll"/>
 <include mask="fmod_event_net.dll"/>
 <include mask="fmod_event_netL.dll"/>
 <include mask="fmod_eventL.dll"/>
 <include mask="fmodex.dll"/>
 <include mask="fmoxedL.dll"/>
 <include mask="icudt46.dll"/>
 <include mask="PhysX3_x86.dll"/>
 <include mask="PhysX3_Common_x86.dll"/>
 <include mask="PhysX3Coooking_x86.dll"/>
 <include mask="PhysX3Gpu_x86.dll"/>
 <include mask="PhysX3PROFILE_x86.dll"/> 
 <include mask="steam_api.dll"/>
 <include mask="VMProtectSDK32.dll"/>


</build>

Goto C:\WarZ\bin
Hit up RSBuild.exe


After Building .*bin Files, copy it from
C:\WarZ\bin\build\data
to
C:\htdocs\wz\ (DONT RENAME THE FILES!)
Goto C:\WarZ\bin\build\updater
Hit up CreateUpdater.bat
Copy WarZlauncher.exe_0.9.*.exe AND woupd.xml to
C:\htdocs\wz\updater




Step 4) [Fire up Super&MasterServer]
Goto C:\WarZ\bin
Edit SupervisorServer.cfg
Look for;
externalIP =
masterIP =
webAPIDomainIP =

change it Like;

externalIp = 123.123.123.123*
masterIp = 123.123.123.123*
webAPIDomainIP = 123.123.123.123*

Now it's Time to fire Up your MasterServer.exe and SupervisorServer.exe




* = Your Hamachi IP
-------------------------------------------------------------------------------------------------------


Done. From now on it should be possible to Register Accounts/Play over Hamachi whit the Launcher.

 

[aLca]

Re: Z and Hamachi w/o M$ IIS [WIP]

Any ppl out here who got THIS HERE Up&Running and want to Help me out testing Hamachi and how Stable it is? Bin's are done, you need only to PM me for Link/Login's.

 

[iceydamo]

Re: Z and Hamachi w/o M$ IIS [WIP] --> Need test users!

wouldnt tunngle work better then hamachi?

 

[aLca]

Re: Z and Hamachi w/o M$ IIS [WIP] --> Need test users!

No1? Okay, it's also cool!

@iceydamo; Yes, Tunngle "can" be better, indeed! But, it's just 4 testing purpose and so on. When it's working as intended, maybe i'll will host some Community Masterserver for VPN-Servers.

 

[DNC]

Re: Z and Hamachi w/o M$ IIS [version 0.0.1]

Cleaned the thread up so you match the New Alpha Stable version that is about 20 minutes from posting bro


PS the RSBuild and WarZLauncher will work in this release, you wont have to use a shortcut and client will only work through the WarZLauncher like it is supposed to do now.

Undeleted the 1 to many

 

[aLca]

Re: Z and Hamachi w/o M$ IIS [version 0.0.2] Here it is!

I'll guess #1 should work 4 now. Feedback would be awesome!

 

[aLca]

Re: Z and Hamachi w/o M$ IIS [version 0.0.2] Here it is!

I'll guess #1 should work 4 now. Feedback would be awesome!

NVM! Added now the FINAL Screenshot of how it should look like for a Clean Client.

 

[SazanOFF94]

Re: The War-Z and Hamachi w/o M$ IIS! [Major rework soon! Windows is up&installing]

Please tell me where it says how to set up the game for hamachi. I govoryupo bad English on it I can not find. help

 

[aLca]

Re: The War-Z and Hamachi w/o M$ IIS! [Major rework soon! Windows is up&installing]

Be patient plx, it's done when it's done. Got already some trouble atm.

 

[aLca]

Re: The War-Z and Hamachi w/o M$ IIS! [Major rework soon! Windows is up&installing]

Sorry to all who had to wait.

 

[allmymind]

Great job! ^^

 

[thefuzzy]

Goto C:\Abyss Web Server\SSL
Hit abyssws.exe
Goto

To view the content, you need to sign in or register

Change it Like my Picture.

At this part its not aspnet, its under scripting parameters

Also unlike the your older guide do we compile all the .sln as normal without changing any ip's?

 

[051992]

can I just only install hamachi change ips and not use Abyss Webserver I use the iis(inetpub) ?

when I go to localhost works.

 

[aLca]

Ye, ofc you can.

Fuzzy; i lil optic rework comes now.

 

[thefuzzy]

Hey so, when you are under scripting parameters you switch the interface to FastCGI local pipes when I do this I cant connect the lootbox db (supervisor server) but at the bottom under Custom Environment Variables I added redirect_status 200 and it works.
But my problem now is I get login failed if I try to connect from another pc. Any ideas?

 

[allmymind]

Done with IIS. Many thanks for your configuration guide.

Can you help me about this?
I can't ping to any clients and any client can't ping to me too.
I try to allow connection in firewall Inbound and Outbound but not work.
I have to turn off firewall (Host , Clients) to get it work. I don't want to turn it off.
Any solution?

PS.Sorry for my english
(I try to ping to myself 127.0.0.1 and my Hamachi ip It's work.)

 

[momk100]

hey aLca my https server is giving me a listening error could u help me out

 

[aLca]

But my problem now is I get login failed if I try to connect from another pc. Any ideas?

Ingame? Make sure that the game.ini is setup properly whit ur Hamachi Ip.

Done with IIS. Many thanks for your configuration guide.

PS.Sorry for my english
(I try to ping to myself 127.0.0.1 and my Hamachi ip It's work.)

Ping answer activated for request's on your FW?

hey aLca my https server is giving me a listening error could u help me out

Need more Background infos. ^^ And also .log files are very important, take a look into it.

 

[thefuzzy]

I get this,

and this is what my log says.
000032.733| WO_API: http timeout
000032.733| LoginAuth: 8

 

[momk100]

here is a picture of my issue aLca