• Unfortunately, we have experienced significant hard drive damage that requires urgent maintenance and rebuilding. The forum will be a state of read only until we install our new drives and rebuild all the configurations needed. Please follow our Facebook page for updates, we will be back up shortly! (The forum could go offline at any given time due to the nature of the failed drives whilst awaiting the upgrades.) When you see an Incapsula error, you know we are in the process of migration.

Help please "Failed to connect"

Newbie Spellweaver
Joined
May 12, 2014
Messages
17
Reaction score
0
Hello, the launcher says please try again

r3dlog

000000.000| Input Devices enabled: Mouse, Keyboard
000000.043| VMEM As seen through DDRaw: 978
000000.044| VMEM As seen through WMI: 0
000000.065| We have 2317 MB texture memory
000000.065| r3dFont: Creating Verdana 10pt
000000.067| r3dFont: Finished creating Verdana 10pt
000000.067| r3dFont: Creating Tahoma 12pt
000000.071| r3dFont: Finished creating Tahoma 12pt
000000.071| r3dFont: Creating Tahoma 10pt
000000.074| r3dFont: Finished creating Tahoma 10pt
000000.074| r3dFont: Creating Tahoma 9pt
000000.077| r3dFont: Finished creating Tahoma 9pt
000000.565| Starting updater, v:2.9.6, cmd:
000000.565| Checking for new updater
000030.574| !resp ChilkatLog:

SynchronousRequest:

DllDate: Jun 14 2011

UnlockPrefix: ARKTOSHttp

Username: KOKO-PC:KoKo

Architecture: Little Endian; 32-bit

Language: Visual C++ 9.0

domain: localhost

port: 80

ssl: 0

OriginallySetFromUrl:

RequestData:

HttpVersion: 1.1

Verb: GET

Path: /wz/updater/woupd.xml

Charset: utf-8

SendCharset: 0

MimeHeader:

ReadTimeout: 60

ConnectTimeout: 30

httpConnect:

hostname: localhost

port: 80

ssl: 0

ConnectTimeoutMs: 30000

calling ConnectSocket2

This is an IPV4 numeric address...

AddrInfoList:

AddrInfo:

ai_flags: 4

ai_family: 2

ai_socktype: 1

ai_protocol: 0

ai_addrlen: 16

ai_canonname: (NULL)

Connect using IPV4.

ipAddress1: 127.0.0.1

timeout waiting for connect to complete

Connect function failed.

SocketError: WSAEWOULDBLOCK The socket would block.

For more information see this Chilkat Blog post:

connectTimeoutSec: 30

idleTimeoutMs: 60000

Failed to connect.

Failed.


000049.748| Requested to stop, 0 files in queue
000049.748| CUpdater::Stop()


Could you help me please :/:
 
Junior Spellweaver
Joined
Apr 14, 2013
Messages
185
Reaction score
66
You didn't give much information, so I am going to assume you're hosting on a server and not your pc.
You need to change the IP's in the source and the "launcher.cfg" to your server's IP.
Just open up "RSUpdate.sln" and look for "127.0.0.1" and "localhost" on the entire solution, and replace them.
 
Upvote 0
Newbie Spellweaver
Joined
May 12, 2014
Messages
17
Reaction score
0
Hello, thank you very much : I managed to solve this problem but I have another error that appeared just after this one.

r3dlog:

000000.000| Input Devices enabled: Mouse, Keyboard
000000.045| VMEM As seen through DDRaw: 978
000000.045| VMEM As seen through WMI: 0
000000.085| We have 2317 MB texture memory
000000.086| r3dFont: Creating Verdana 10pt
000000.087| r3dFont: Finished creating Verdana 10pt
000000.087| r3dFont: Creating Tahoma 12pt
000000.088| r3dFont: Finished creating Tahoma 12pt
000000.089| r3dFont: Creating Tahoma 10pt
000000.089| r3dFont: Finished creating Tahoma 10pt
000000.089| r3dFont: Creating Tahoma 9pt
000000.090| r3dFont: Finished creating Tahoma 9pt
000000.727| Starting updater, v:2.9.6, cmd:
000000.727| Checking for new updater
000000.775| Checking for new updater - finished
000065.317| WO_API: http timeout
000065.317| Login FAILED, code: 8

Please, if you could help me one more time. Thank you to having answered so quickly :).
 
Upvote 0
Junior Spellweaver
Joined
Apr 14, 2013
Messages
185
Reaction score
66
This should be due to HTTPS. Follow this tutorial and it should work:

Make sure your 443 port is open in your firewall.
 
Upvote 0
Newbie Spellweaver
Joined
May 12, 2014
Messages
17
Reaction score
0
The https port of my firewall is open but i think the problem isn't caused by this. When I go for register using the launcher, i get this page thank you for your help
 
Upvote 0
Junior Spellweaver
Joined
Apr 14, 2013
Messages
185
Reaction score
66
Open "RSUpdate.sln" and edit the file "LauncherConfig.cpp", and scroll down to the comment section "Manual Config", and then edit the values of all the variables to match your server's IP and links to your api files.
Note: You don't need to provide the "launcher.cfg" file with your launcher after you've done the above.
 
Upvote 0
Newbie Spellweaver
Joined
May 12, 2014
Messages
17
Reaction score
0
Hello, thank you again for all the help you provided me.
I try to manage alone, but I'm stuck at this stage.


r3dlog:


000004.322| Loaded 12 of 12 grass settings locations from the glist file
000004.334| Loaded 12 grass settings files
000004.548| WEAPON ERROR: 100999_name trying to load non existent sound event Sounds/NewWeapons/SUP/SUP_Generic_Shot_single
000004.556| Trying to load food item with id '301321' that is already loaded!000037.974| WOApi: Connect to 127.0.0.1
000037.974| WOApi: api_LoginSessionPoller.aspx NETWORK time: 30.1066
000037.974| WO_API: http timeout
000037.975| LoginAuth: 8
000047.917| obj_Zombie::FreePhysSkeletonCache:000047.917| done in 0.00 seconds
000047.920| Deleting render targets
000048.318|
000048.320| WARNING: pd3ddev have 10 reference counts

pepitox - Help please "Failed to connect" - RaGEZONE Forums



I hope I can always count on your help :) plz
 
Last edited:
Upvote 0
Junior Spellweaver
Joined
Apr 14, 2013
Messages
185
Reaction score
66
Open "WarZ.sln", then search for "127.0.0.1" in the following files:
"Vars.h", "Main.cpp", "WOBackendAPI.cpp".
replace "127.0.0.1" with your server's IP, also make sure the paths to your api are valid.
If you have done the above and the problem still persists, check your port 443.
 
Upvote 0
Newbie Spellweaver
Joined
May 12, 2014
Messages
17
Reaction score
0
I have followed your instruction but my problem is not resolved :/:.
 
Upvote 0
Junior Spellweaver
Joined
Apr 14, 2013
Messages
185
Reaction score
66
I had the same issue and I resolved it by doing what I mentioned in my previous post. Try to clean your solution and rebuild everything.
Check your API. My issue was that https was not binded on my IIS website and I also had to open the port both on the firewall and on the router.
 
Upvote 0
Back
Top