These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
12Next page
 

New Launcher and Proxies

First post
Author
Previous Topic Next Topic
Penitent Ezekiel
Golden Ratio SciTech
#1 - 2012-03-13 12:13:29 UTC
The machine that I play eve on cannot access the EVE servers directly due to filtering on the ports that it uses. I run EVE through a, SSH proxy using /server:127.0.0.1 which is all well and good, however it also means that whenever I have wanted to patch the game I have to download the patches over plain HTTP (for some reason patching doesn't work through my proxy, does it use another port?) and apply them manually.

This means I am now currently in an interesting situation - my install of EVE cannot patch itself over the proxy and the manual patches which would allow me to get up to date (and see the launcher and whatnot) have been discontinued! http://community.eveonline.com/patches/patches.asp now shows the utterly unhelpful "Updates to the EVE Client will be done through the launcher from now on."

Would it not make sense to run manual patches side by side until you get the launcher properly working with the general majority? Do I now need to rely on a third party to upload their own exported patch before I can update my own install and yet, how can I even do that without having a version of the client with a launcher? Will I have to do a complete reinstall of EVE?

Inquiring minds are filled with inquiries!
Aethlyn
Brutor Tribe
Minmatar Republic
#2 - 2012-03-13 12:21:48 UTC
I'm not sure, but I'd expect them to use Internet Explorer's proxy settings (correct me if I'm wrong). Can you access web pages using Internet Explorer? If you're using some other browser the proxy settings might not be set.

Looking for more thoughts? Follow me on Twitter.
Penitent Ezekiel
Golden Ratio SciTech
#3 - 2012-03-13 12:48:46 UTC
Yep, I can access everything on the Internet perfectly fine through IE. IE tunnels over my proxy just fine and the EVE client connects to Tranquility just fine however the EVE client won't patch through it automatically and there is no manual patch available at this time.
Penitent Ezekiel
Golden Ratio SciTech
#4 - 2012-03-13 13:22:34 UTC
The saga continues! I ran the Repair tool, this patched my EVE client to the latest version it will now start fine however it will no longer connect through my proxy Straight Running my previous EVE shortcut with the /server option fails with an exception as does running the launcher.exe with a /server option.

Running "Launcher" on it's own works fine and EVE starts but of course, cannot connect to the EVE server (port blockage, see first post)

Here's the stack trace for the failures when applying the /server command line argument. Finally - seriously? No angle brackets or indentation in this forum? Brill...

Quote:
Traceback (most recent call last):
File "launcher.py", line 36, in module
File "lib\initialization.pyc", line 125, in StartLauncher
File "lib\initialization.pyc", line 58, in InitInfo
File "lib\update.pyc", line 721, in GetUpdateServer
File "lib\update.pyc", line 748, in GetServerBuildNumber
File "lib\getServerStatusHack.pyc", line 53, in GetServerBuildnumber
File "lib\getServerStatusHack.pyc", line 11, in GetServerResp
File "socket.pyc", line 222, in meth
gaierror: [Errno 11004] getaddrinfo failed
Locals by frame, innermost last:
Frame module in launcher.py at line 47:
NoInternetError = class 'lib.exceptions.NoInternetError'
ServerUnreachableException = class 'lib.exceptions.ServerUnreachableException'
Shutdown = function Shutdown at 0x041738B0
StartLauncher = function StartLauncher at 0x044B22F0
__builtins__ = module '__builtin__' (built-in)
__doc__ = '\n This is the entry point into the launcher, it handles setting up the working\n directory, logging and finally importing and starting the laucher within a\n log-proof try/exeception clause so we can catch almost any exception and display\n an error message.\n'
__name__ = '__main__'
__package__ = None
exc_plus = function exc_plus at 0x0402D670
lib = module 'lib' from 'C:\Program Files (x86)\CCP\EVE\launcher\library.zip\lib\__init__.pyc'
localization = module 'localization' from 'C:\Program Files (x86)\CCP\EVE\launcher\library.zip\localization\__init__.pyc'
os = module 'os' from 'C:\Program Files (x86)\CCP\EVE\launcher\library.zip\os.pyc'
socket = module 'socket' from 'C:\Program Files (x86)\CCP\EVE\launcher\library.zip\socket.pyc'
sys = module 'sys' (built-in)
wx = module 'wx' from 'C:\Program Files (x86)\CCP\EVE\launcher\library.zip\wx\__init__.pyc'
zipextimporter = module 'zipextimporter' from 'C:\Program Files (x86)\CCP\EVE\launcher\library.zip\zipextimporter.pyc'
Frame StartLauncher in lib\initialization.pyc at line 128:
app = wx._core.App; proxy of Swig Object of type 'wxPyApp *' at 0x23c4f38
folder = 'C:\\Program Files (x86)\\CCP\\EVE'
Frame InitInfo in lib\initialization.pyc at line 58:
cacheDir = u'C:\\Program Files (x86)\\CCP\\EVE\\launcher\\cache'
folder = 'C:\\Program Files (x86)\\CCP\\EVE'
Frame GetUpdateServer in lib\update.pyc at line 721:
clientInfo = {'usescriptindexfiles': '1', 'appname': 'EVE', 'region': 'ccp', 'socketio': 'iocp', 'sync': '349998', 'server': '127.0.0.1:26000', 'edition': 'premium', 'version': '7.30', 'role': 'client', 'build': '349998', 'branch': '//depot/games/branches/release/EVE-TRANQUILITY/eve', 'aid': '0', 'codename': 'EVE-EVE-TRANQUILITY', 'port': '26000', 'cryptopack': 'CryptoAPI'}
folder = 'C:\\Program Files (x86)\\CCP\\EVE'
server = '127.0.0.1:26000'
Frame GetServerBuildNumber in lib\update.pyc at line 748:
address = '127.0.0.1:26000'
Frame GetServerBuildnumber in lib\getServerStatusHack.pyc at line 53:
ip = '127.0.0.1:26000'
Frame GetServerResp in lib\getServerStatusHack.pyc at line 16:
ip = '127.0.0.1:26000'
s = socket._socketobject object at 0x046169D0
Frame meth in socket.pyc at line 222:
args = (('127.0.0.1:26000', 26000),)
name = 'connect'
self = socket._socketobject object at 0x046169D0
jenny Yassavi
Doomheim
#5 - 2012-03-13 15:25:56 UTC
Same here,

Unable to connect through a proxy.
Aethlyn
Brutor Tribe
Minmatar Republic
#6 - 2012-03-13 15:32:04 UTC  |  Edited by: Aethlyn
(Forget what I wrote here before.)

From that stack trace it looks like the client tried to connect to 127.0.0.1 but it wasn't able to complete the connection. So the switch works, but it's somehow threated wrong or there's something else being expected.

Seems like the launcher wants to connect to your tunnel, too (which somehow fails). You're not having any firewall rules in place blocking that connection (127.0.0.1:26000)?

Looking for more thoughts? Follow me on Twitter.
CCP Sputnik
C C P
C C P Alliance
#7 - 2012-03-13 15:40:20 UTC  |  Edited by: CCP Sputnik
Dont tell anybody but we have a backup of the patches around:



We will keep these around for the next few more releases.

Edit: Unfortunately we don't have fallback patches for mac (the structure of the client changed which resulted in patches bigger than the installer) so the only fallback for Mac is the Installer (sorry guys Straight).

CCP Sputnik | Software Engineer | Team Undone Unit

My EVElopedia Talk My Broadcast Log
Mygalli
Doomheim
#8 - 2012-03-13 16:02:08 UTC
CCP Sputnik wrote:
Dont tell anybody but we have a backup of the patches around:



We will keep these around for the next few more releases.

Edit: Unfortunately we don't have fallback patches for mac (the structure of the client changed which resulted in patches bigger than the installer) so the only fallback for Mac is the Installer (sorry guys Straight).


Thank you Sputnik,

The manual patches have actually helped resolve an unrelated issue I've been having with the launcher throwing an exception at me during patching.
Accipitradea
Caldari Provisions
Caldari State
#9 - 2012-03-13 16:58:30 UTC  |  Edited by: Accipitradea
This stupid forum ate this post 4 times before it actually took.

Penitent Ezekiel wrote:

Frame meth in socket.pyc at line 222:
args = (('127.0.0.1:26000', 26000),)
name = 'connect'
self = socket._socketobject object at 0x046169D0


So basically this means you tried to specify the port in the /server flag. You can't do that, just put the localhost ip:

/server:127.0.0.1

The port is the default for you, so you shouldn't need to change it. Sadly, that's the problem I'm running into, the port is controlled by the start.ini file in the root directory, however it can't be modified without failing a checksum verification on launch, so despite it having the required port, the client won't even launch. If I put it back to default, the client launches, but won't use the custom port.

Whoever decided to checksum verify a .ini configuration file over at CCP needs to be taught what a .ini file is for. You don't checksum your settings file where people will be changing the settings. Ugh

Has anyone figured out where/how to change the port value properly for the launcher?

If I don't use the /server flag, the launcher uses http to verify the server status and then tries to connect the client to the server using the correct port, but the wrong ip.

If I use the /server flag, the launcher connects to the right ip, but on port 26000, ignoring the port change in the prefs.ini and using the unmodifiable value in start.ini. The launch fails immediately and never lets me launch the client correctly.
Penitent Ezekiel
Golden Ratio SciTech
#10 - 2012-03-13 17:32:02 UTC
Hurray! Thanks Accipitradea! Removing the port from my shortcut worked a charm and i'm up and running again through my tunnel - ready to log in at exactly one minute before an unscheduled reboot :)

Big thanks to Sputnik too - those static patch links got my client up and running.

Interesting side note: I had to start the launcher as an admin, fail a patch then start in normal mode to get the patch to take.
ACESsiggy
Deaths Consortium
#11 - 2012-03-13 18:12:03 UTC
Penitent Ezekiel wrote:
get the launcher properly working with the general majority?



No, at CCP they throw unfinished products on the shelf.Shocked

Uninstall the game like me and just wait a week or so till they fix their mistake(s)

Till then play ModernWarfare 3 or Battlefield 3 .......... or should i mention Elder Scrolls :)

“The open-minded see the truth in different things: the narrow-minded see only the differences.”
Beg Askiras
Deep Core Mining Inc.
Caldari State
#12 - 2012-03-13 18:20:23 UTC
CCP Sputnik wrote:
Dont tell anybody but we have a backup of the patches around:



We will keep these around for the next few more releases.

Edit: Unfortunately we don't have fallback patches for mac (the structure of the client changed which resulted in patches bigger than the installer) so the only fallback for Mac is the Installer (sorry guys Straight).


http://cdn1.eveonline.com/341054/EVE_Online_Installer_341054.exe Installer for first patch
Samantha Utama
Caldari Provisions
Caldari State
#13 - 2012-03-14 03:17:30 UTC
I'm a little stuck. So where should I put the /server:127.0.0.1 now? In the shortcut to the launcher? Tried that but it doesn't go beyond the Eve splash screen.
YariScur
Sebiestor Tribe
Minmatar Republic
#14 - 2012-03-14 08:47:19 UTC
Hello,

I used to play over SSH tunnell.

My settings were:

1) port 26000 from localhost redirect to 87.237.38.200:26000
1) port 26001 from localhost redirect to 87.237.38.200:26001
1) port 64519 from localhost redirect to 87.237.38.200:64519

Quote:
eve.exe /server:127.0.0.1
this worked before update.

But I suppose either new ports/addresses were added or syntaxis changed...

So has anyone succesfully logged in to eve after update over tunnell?
Finlara Deity
The Point
Prestige Mode
#15 - 2012-03-14 10:41:46 UTC
same problem here, cannot connect through ssh tunnel as I'm unable to use the server parameter
Femaref
Nocturnal Romance
Cynosural Field Theory.
#16 - 2012-03-14 11:16:21 UTC
Accipitradea: make your ssh tunnel listen on localhost:26000, pipe it forward on an open port, and the other side on your server pipes it back to eve-server:26000.
Aethlyn
Brutor Tribe
Minmatar Republic
#17 - 2012-03-14 11:49:46 UTC
Accipitradea wrote:
So basically this means you tried to specify the port in the /server flag.

Ahhh! Good catch. Didn't notice the port being specified twice.

Looking for more thoughts? Follow me on Twitter.
YariScur
Sebiestor Tribe
Minmatar Republic
#18 - 2012-03-14 12:36:15 UTC
Femaref wrote:
Accipitradea: make your ssh tunnel listen on localhost:26000, pipe it forward on an open port, and the other side on your server pipes it back to eve-server:26000.


Already done, problem is my default proxy is rejecting just everything without domain authentication. and eve.exe now wants not only 26000 but plain http connection which is not accessible.
Samantha Utama
Caldari Provisions
Caldari State
#19 - 2012-03-14 13:36:30 UTC  |  Edited by: Samantha Utama
ok, quick/temporary fix if you are unable to log in at all, so that you can tend to your empty skill queues:

I managed to get it working by creating the shortcut to the ExeFile.exe found in /bin folder with the /server:127.0.0.1 parameter.

Be warned tho, this resets all your settings to default, but I didn't mind that much. Also there's a console window like some sort of logServer.

This seems to bypass the Launcher™ completely so you'll have to update your client via the launcher first.

Hope CCP doesn't disable this now :V
Accipitradea
Caldari Provisions
Caldari State
#20 - 2012-03-14 14:30:11 UTC  |  Edited by: Accipitradea
Femaref wrote:
Accipitradea: make your ssh tunnel listen on localhost:26000, pipe it forward on an open port, and the other side on your server pipes it back to eve-server:26000.


I'm not using an ssh tunnel; just changing the local outbound port to circumvent the firewall and changing it back on my own firewall elsewhere. Thanks for the advice, but my set up simpler because I'm not tunneling, just PATing.

Samantha Utama wrote:
ok, quick/temporary fix if you are unable to log in at all, so that you can tend to your empty skill queues:

I managed to get it working by creating the shortcut to the ExeFile.exe found in /bin folder with the /server:127.0.0.1 parameter.

Be warned tho, this resets all your settings to default, but I didn't mind that much. Also there's a console window like some sort of logServer.

This seems to bypass the Launcher™ completely so you'll have to update your client via the launcher first.

Hope CCP doesn't disable this now :V


Ah ha! This is what I needed, because this allows me to bypass the launcher entirely. You make a good point that your settings will get reset, but if this matters, you can copy the /user/AppData/Local/CCP/EVE/c_programfiles_(x86)_ccp_eve_Tranquility files into the new user/AppData/Local/CCP/EVE/c_programfiles_(x86)_ccp_eve_127.0.0.1 directory that will be created after your first attempt to log on. That's where I had to go back and set the prefs.ini file port value.

Now I can connect without using the god-forsaken Launcher at all, just like I could last week. Though I'll probably have to use it to patch, then quit, then use my direct launch.
12Next page