Getting System.Net.WebException Error

Beladi

Active Member
I'm a new ISXEQ2 user; my ex raved about it so decided to try it out.

Since he's not around to install things for me anymore I printed out instructions from forum posts and I believe followed everything to the letter.

However when I log in with InnerSpace and attempt to load ISXEQ2 using. . .
EXT ISXEQ2 and <enter> I get the following text:

ISXEQ2 Subscription Active. Thank you!
. . . Please hold while the ISXEQ2 patcher checks for updates. . .
isxGamesPatcher: Starting (Ver. 20090703.0001 by CyberTech/Amadeus)
isxGamesPatcher: Checking isxGamesPatcher: 1 file in manifest. . .
isxGamesPatcher: Exception: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. --->

I checked my version of .Net framework like Amadeus mentions in this post: http://www.isxgames.com/forums/showthread.php?t=3488 and it is version 3.5 SP1.

Any suggestions as to what to do now? Did I miss something? Any help would be so welcome!
 

Beladi

Active Member
That Fixed It!

It WORKED!!

Thanks so very much for your quick assistance. I was feeling quite lost!

No errors and it loaded right up.

A million thanks
 

Uglyhat

Active Member
Same error

Unfortunately #'s 1 and 2 aren't solving the problem. Is the <@CyberTechWork> significant to the solution, the domain of Valerian's email, or something else? Looking at GoDaddy's repository page in the last URL Valerian provided leaves me with no idea what to do.

I understand a certificate of some sort needs to be validated. Please help me lose a bit of my Noobness and offer a clue about where to go next. Also, given that things were running fine then suddenly this error appears, what might casue it and how can I learn more about this?

Thanks !!
 

Amadeus

The Maestro
Staff member
Running Windows Update and installing all available updates should fix most every problem related to this.
 

Pygar

EQ2Bot Specialist
Specifically, runnign windows update and applying the optional root certificates update will fix this issue.
 
Top Bottom