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.
 

Socket Closed

First post First post First post
Author
Previous Topic Next Topic
Irene Kennedy
#361 - 2014-03-02 23:17:40 UTC
Same exact problem here, since Friday (2 days now).
Kylejen Janau
Imperial Shipment
Amarr Empire
#362 - 2014-03-02 23:24:35 UTC
I really do hope CCP fixes it someday soon Cry
DerpimusPrime Aihaken
Free Tank Test
#363 - 2014-03-02 23:39:59 UTC  |  Edited by: DerpimusPrime Aihaken
Same for me, socket closed every 5-10 min.
But the weird thing is when im not doing anything docked I pretty much never get "socket closed"

And on another note this started happening for me after the ddos attack.
DerpimusPrime Aihaken
Free Tank Test
#364 - 2014-03-02 23:52:03 UTC  |  Edited by: DerpimusPrime Aihaken
ops double post.
Piraal
Viziam
Amarr Empire
#365 - 2014-03-02 23:55:47 UTC  |  Edited by: Piraal
Looks like I have the same problem as many others.

Launcher won't launch client, tried repair, tried clearing cache problem persists. When I try to run client from bin/exefile my socket closes the moment I get on.
Piraal
Viziam
Amarr Empire
#366 - 2014-03-02 23:56:53 UTC  |  Edited by: Piraal
blah double post, sorry.
hungrymanbreakfast
Federal Navy Academy
Gallente Federation
#367 - 2014-03-03 00:08:43 UTC
Yup. Know a number of people that cannot log in some of their characters. I have one of mine on and can occasionally get my alt on, but at the moment am doing the repetitive log ins hoping it connects.
Comon CCP get this fixed.
Neville Smit
The Scope
Gallente Federation
#368 - 2014-03-03 01:29:42 UTC
Started having this issue this week - I can't log in to any of my characters. Keep getting "Connection Lost - Socket is closed" error messages.

Submitted a support ticket. Looking for ideas here.

I am an unapologetic fan of EVE Online. My blog: http://nevillesmit.com/ - My Twitter: https://twitter.com/NevilleSmit
Elvis Jones
Deep Core Mining Inc.
Caldari State
#369 - 2014-03-03 02:47:29 UTC
I've been getting "connection lost, socket closed" errors all weekend.
Irene Kennedy
#370 - 2014-03-03 03:13:17 UTC  |  Edited by: Irene Kennedy
ANGER. well sorta.

we'd love to help but it is the weekend.

i always seem to get called in when things go wrong at my job.

just saying.

and to anyone that loves to flame people about this, hush.

not one response since this began (for alot of us) is sad.
Jester Cap
A better day
#371 - 2014-03-03 08:19:03 UTC
I can confirm, restarting my computer and router fixed the problem for me.
Zappity
New Eden Tank Testing Services
#372 - 2014-03-03 08:37:15 UTC
Jester Cap wrote:
I can confirm, restarting my computer and router fixed the problem for me.

Didn't for me. Nor did switching to a different router. Only a problem for the last couple of days.

Zappity's Adventures for a taste of lowsec and nullsec.
Mihnea Tepes
Federal Navy Academy
Gallente Federation
#373 - 2014-03-03 10:10:03 UTC
Zappity wrote:
Jester Cap wrote:
I can confirm, restarting my computer and router fixed the problem for me.

Didn't for me. Nor did switching to a different router. Only a problem for the last couple of days.


the same here, last two days to be precise
Robert BlueLion
Immortalis Inc.
Shadow Cartel
#374 - 2014-03-03 11:07:15 UTC  |  Edited by: Robert BlueLion
The "The Socket Was Closed" message on login has become very common over the last few days, since the end of the last week. The Login Launcher launches fine, as well as the initial login/load screen, but as and when you login via selecting a character on the 'character select' login screen, it has a common habit of closing socket on login to said character every now and again. Normally after a few re-attempts it'll log you in in-game successfully, maybe one or two times, maybe more for some. The tell-tale sign that it won't log you in is when the chat channel box does not appear within a few seconds of login, and you instead receive a permanent black screen until disconnect. The best way to do it is either retry until you get a successful login, or do a fresh restart of the game launcher and retry login, because myself and a few other people are finding restarting your router/computer isn't making a difference in terms of this issue occurring less, or being a suitable fix. Pirate
Rotineque Severasse
Center for Advanced Studies
Gallente Federation
#375 - 2014-03-03 11:55:10 UTC
Seems after DT it is now fixed for me. Wasn't working before DT.
Narkrud Morganian
The Forgotten Veterans
#376 - 2014-03-03 14:24:21 UTC
Is this today's downtime we are talking about or yesterdays maintenance?, as i would Love to be able to play tonight
York Saissore
Center for Advanced Studies
Gallente Federation
#377 - 2014-03-03 14:26:10 UTC
Ok, seems to work now with todays patch.

But am i getting back those three days (weekend days so more free to play) I did pay for the game-time afterall.
Johnnyan
Johnnyan Inc.
#378 - 2014-03-03 14:31:12 UTC
Well, I reactivated my account 4 days ago, I couldn't play for 3, so yea :) I could not even post inhere until now....
Samir Saab
Deep Core Mining Inc.
Caldari State
#379 - 2014-03-03 14:33:33 UTC
CCP Developers are Amar elites and us steam users are Minmatar slaves (ROLE PLAY) hence the second class citizen treatment....
Moostang
Center for Advanced Studies
Gallente Federation
#380 - 2014-03-03 23:29:23 UTC
LunarGlow wrote:
Moostang wrote:
LunarGlow wrote:
Moostang wrote:


I see that the eve subnet is not longer being advertised by CCP BGP AS anymore. It is now advertised by verisign. :(


What does that mean for a user like me?


Nothing really. Simply that it is a change and before that change I was able to log in without any problems. If it is CCP's intent to reroute through Verisign then the decision to change paths is not in itself a problem, but it is obviously broken in some form since some of us are unable to log in.


Way to screw up before leaving for the weekend.



Looks back to normal. Eve's IP subnet is now being advertised from the CCP network again instead of from Verisign and trace-routes confirm.