|
Author |
Thread Statistics | Show CCP posts - 82 post(s) |
Seth Toralen
Generic Alt Corporation 421
0
|
Posted - 2013.05.26 16:56:00 -
[1] - Quote
I am still having issues with the launcher's login process. All of my attempts to communicate this to CCP have gone unanswered. Let me try to explain to explain the problem again.
I get 324 Errors whenever I try to access a number of EVE's login pages. I can't login to community.eveonline, secure.eveonline, or login.eveonline. When I try to access those pages, Chrome returns: "Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data." This problem persists across all computers on my local network. I suspect that a secure connection is failing to be established between the login pages and my computer.
This affects the launcher since the launcher directly tries to connect to login.eveonline for login purposes. I experience the error through the launcher and this page: https://client.eveonline.com/launcherv3.
I have filed two bug reports on this issue. One specific to the launcher issue (158877), and one specific to the websites (158874). I only realized later that they are in fact, the same issue. I also have been active on multiple forum posts. CCP has not responded to any of my posts. Here is the latest one: https://forums.eveonline.com/default.aspx?g=posts&m=3082892#post3082892 I also filed multiple petitions. The latest one is: #3234285
Please respond to something. I can't access account management, API's, petitions, the launcher.... Once the login is migrated out of the client, I will be completely unable to access EVE (except for the forums oddly enough). |
Seth Toralen
Generic Alt Corporation 421
4
|
Posted - 2013.06.08 18:48:00 -
[2] - Quote
Still can't use the launcher due to the 324 errors that a number of us are experiencing with EVE's browser login pages. We can't load the login pages at community.eveonline, secure.eveonline, and login.eveonline. The login pages don't load; they just eventually time out. Since the launcher tries to access the form from login.eveonline.... No login section.
Not a PC issue.. problem persists across our networks on every PC. Not a browser issue either. Not an antivirus issue. You just screwed the login pages for some of us when you updated them for this new unified login. Can't use the launcher, account management, API management, or petition management until you fix it for us. The 'workaround' is literally the only way we can login to the game now. |
Seth Toralen
Generic Alt Corporation 421
4
|
Posted - 2013.06.08 19:12:00 -
[3] - Quote
CCP Atropos wrote: We're looking into this on our end in an attempt to reproduce it. As you say it covers every device on your network, and so isn't isolated to a single computer or whatever, but rather is something about your network that stops it communicating properly.
Yes and it only occurs at the login pages on login.eveonline, community.eveonline, and secure.eveonline. The login page for forums.eveonline still works correctly. The forums, I believe, were the only thing not given the 'unified login' treatment too. Also, I think that my API fetching is being blocked, hopefully for the same root reason. Around the same time the login pages started having trouble, EFT and EVEMon stopped being able to fetch API info.
Thanks for working to fix this issue. It's getting really annoying. |
Seth Toralen
Generic Alt Corporation 421
4
|
Posted - 2013.06.14 15:56:00 -
[4] - Quote
I appreciate that CCP has acknowledged that there are some significant problems that need to be worked through. Among many, many people with current and last gen nVidia cards are having problems with EVE and drivers (some so severe it's crashing their games). Many people are unable to login through the launcher, because for varied reasons, it's broken for them. Some people (myself included) can't login into any of EVE's website services (API, Account Management, ect.) ever since you tried to create this 'unified login' system. Oh and on top of all the bugs, you've had people DDoS'ing your servers. CCP is having a bad month.
But at least we're all on the same page that these problems exist. I feel like CCP Atropos is getting some unfair heat for all this here. The launcher isn't a bad thing.... if they get it working. And I am sure usability tweaks will be made once they actually get this simplified version working. As long as ALL of our bugs are getting attention to get resolved, I am okay. Just try and get them all fixed as quickly as you can. EVE players are impatient people. |
Seth Toralen
Generic Alt Corporation 421
4
|
Posted - 2013.06.19 20:45:00 -
[5] - Quote
So uh... not to bug anyone, but the launcher still doesn't work for me either. I mean at least I can play with the .exe workaround (for now), but the launcher is still broken for me.
I'm one of those 'Error 324' guys who can't load/access the login screens on any of EVE's websites (and thus the login area of the launcher too). Been screaming about it for a month or so now.... anyone working on it or are we screwed? Also we're conveniently unable to cancel our account because we can't access Account Management so... yeah. |
Seth Toralen
Generic Alt Corporation 421
4
|
Posted - 2013.06.24 08:58:00 -
[6] - Quote
Assming CCP still follows this forum....
In followup to my Error 324 issues with all of EVE's websites, I have submitted a new bug report. As a quick reminder, this error prevents me from logging into account management, API management, and using the new launcher. This new bug report contains every bit of network diagnostics I could think to include. Since my problems connecting to the login pages are obviously somewhere in the interwebs, I have included tests that mostly focus on tracing communication from my PC to CCP's servers.
My tests include an ipconfig, a tracert to login.eveonline, a pathping to login.eveonline, and a netstat. All of this juicy data is in bug report 163663. It's probably enough data about my network to reveal vulnerable ports and certainly where I live too... whatever. Just use it to fix problems. I really hope it helps. |
Seth Toralen
Generic Alt Corporation 421
6
|
Posted - 2013.06.24 18:23:00 -
[7] - Quote
CCP Atropos wrote:Seth Toralen wrote:Assming CCP still follows this forum....
In followup to my Error 324 issues with all of EVE's websites, I have submitted a new bug report. As a quick reminder, this error prevents me from logging into account management, API management, and using the new launcher. This new bug report contains every bit of network diagnostics I could think to include. Since my problems connecting to the login pages are obviously somewhere in the interwebs, I have included tests that mostly focus on tracing communication from my PC to CCP's servers.
My tests include an ipconfig, a tracert to login.eveonline, a pathping to login.eveonline, and a netstat. All of this juicy data is in bug report 163663. It's probably enough data about my network to reveal vulnerable ports and certainly where I live too... whatever. Just use it to fix problems. I really hope it helps. This is excellent information. We've been completely stumped as to how or why this is happening, and detailed information such as this will undoubtedly help us. Thank you very much.
By all means, then please let me know if there is any other diagnostics I can run for you. I want this figured out and fixed as much as you guys do.
For example, running new tests this morning, I found that running a tracert to community.eveonline (or login or secure) follows a slightly different behavior than forums.eveonline (the only place I CAN still login). It is a minor, and likely unimportant difference with how CCP's front server (83.245.126.202) directs my request. Still how can I most effectively point it out to you guys? Just appending new information the the text file I included with the latest (and already processed) bug report? |
Seth Toralen
Generic Alt Corporation 421
6
|
Posted - 2013.06.24 23:09:00 -
[8] - Quote
CCP Atropos wrote:We've had some internal discussion and thrown a few theories around relating to corrupted winsocks drivers and MTU packet sizes. It would be great if you could undertake steps 1 and 2 in this article. Since we're not entirely sure what the cause it, I wouldn't recommend step 3 at this time. As for the winsocks theory, this Google thread details the same problem under Chrome, and how fixing the winsock drivers resolved the issue for some people. Again, since this is all just theory, I wouldn't recommend you do anything crazy at this time.
Here is what I found:
My MTU is set to the ethernet default of 1500 (1472 byte packets with 28 byte headers). Nothing strange there. I'll put the full netsh information at the end of this post.
Pinging google.com: It's a little weird. At first, packets won't go through with the default packet size of 1472 bytes. I had to lower the packet size to 548 for replies to begin flowing. However, after getting replies at 548, I could then send packets of 1472 bytes (MTU 1500) or higher. I tried packets as large as 10000 bytes and received replies. I tried new instances of cmd prompt, and the results were somewhat inconsistent. I could always send packets of 548 bytes or lower, but only sometimes was I able to send larger packets (and when larger, there was no practical limit). There seems to be nothing I can do to trigger the larger packets working. It never works the first time. I really can't make any sense of it. It almost seemed like short time windows were opening in which I could send larger packets (the ability would stop sometime later). Sometimes the 'packet needs to be fragmented' message would appear but packets would still send with replies. Very strange indeed....
Pinging login.eveonline.com: Normal ping (ping login.eveonline.com) worked fine. Packet size 1472 bytes would not go through (MTU 1500). Packets of size 548 or lower would always go through (just like google). I could never get packets larger than 548 packets to send. I even managed to catch a window where google.com was accepting packets of 1472 bytes and 10000 bytes, but login.eveonline.com was still not accepting packets above 548. The test in this windows were done in the same cmd instance. Google accepted large packets before and after the login.eveonline.com packets failed.
Pinging community.eveonline.com and secure.eveonline.com: exact same behavior as login.eveonline.com
Pinging forums.eveonline.com: same behavior. This may be important since this is the one site I can still login.
Summary: My network / ISP seems to be doing interesting things with packets larger than 548. CCP websites cannot reply to any packets larger than 548. Google (and I'd expect other sites) seems to sometimes accept larger packets, but it is very inconsistent. This is interesting since my MTU is set to the default 1500. I hope someone else can make more sense of all of this. I'm trying to be as thorough with you guys as possible since you've had trouble replicating the issue.
Here is my full netsh interface ipv4 show subinterfaces:
MTU MediaSenseState Bytes In Bytes Out Interface ------ --------------- --------- --------- ------------- 4294967295 1 0 2530624 Loopback Pseudo-Interface 1 1500 5 0 0 Wireless Network Connection 1500 1 19479868419 2149006945 Local Area Connection 1500 5 0 2571520 Wireless Network Connection 2 1500 1 0 3619091 VirtualBox Host-Only Network
|
Seth Toralen
Generic Alt Corporation 421
6
|
Posted - 2013.06.24 23:18:00 -
[9] - Quote
CCP Atropos wrote:Thank you so much for this information. I'll add it all to the defect and talk to our Ops guys. It is very strange that you're still able to access the forums, since it's all using the same load balancing and certificates, as far as I'm aware.
I will point out that I don't believe that the forums were incorporated into the unified login system. I am not sure what changes might have been made to the other login pages that weren't made to the forums (if any). |
Seth Toralen
Generic Alt Corporation 421
6
|
Posted - 2013.06.24 23:52:00 -
[10] - Quote
CCP Atropos wrote:Seth Toralen wrote:CCP Atropos wrote:Thank you so much for this information. I'll add it all to the defect and talk to our Ops guys. It is very strange that you're still able to access the forums, since it's all using the same load balancing and certificates, as far as I'm aware. I will point out that I don't believe that the forums were incorporated into the unified login system. I am not sure what changes might have been made to the other login pages that weren't made to the forums (if any). They were. If you open an incognito window (or whatever it might be called in your browser of choice) and navigate to the forums, and click the 'Log in' button it should redirect you to our login servers. Although, in your case, it probably wouldn't. It might be that you had a cookie that was logged in prior to the change, but I would still think that it would get sent to the servers for authentication.
Wow. You are quite right. When I use an incognito window, I am redirected to login.eveonline and cannot login to the forums. I guess this means that when you fix this apparent security problem (I guess it's not authenticating), I will lose access to the forums too. In the meantime, I better not empty my cookies.
Petitions and bug reports still don't direct to login.eveonline though. I have logged in to those areas fine. At the very least, please don't change that or I'll be stuck just emailing you guys. |
|
Seth Toralen
Generic Alt Corporation 421
6
|
Posted - 2013.06.25 01:45:00 -
[11] - Quote
I really do think CCP will add features to the launcher that will make it easier to multibox. I don't multibox myself, but it seems that a lot of the really 'hardcore' multiboxers had done some very intense work setting up a system that worked for them. A system with multiple installations that ran separately and were managed through a third-party central application. It sounds like a beautiful system for them. But with the launcher, that system has been largely broken.
Moving to a launcher-based system necessitated those things breaking. It would have been good of CCP to anticipate how this would affect some multiboxers, but to be fair, multiboxers with multiple installations and third party management software went far outside the design space that CCP laid out. However, I see real potential for this launcher to actually develop into something even better for the multiboxers; it just needs more features and development. It could allow for an equally capable multibox setup with one main installation and no third party software. I think we'll see some of these features, hopefully soon. Unfortunately, some of the people who were affected most by the new launcher were some of EVE's most avid fans who regularly play multiple accounts. On the other hand, I can see why CCP would want to start off with a very basic core launcher and incorporate new features from there.
Keep up the good work resolving the still existing issues and then getting to work on new features to make everyone's experience a little smoother. |
Seth Toralen
Generic Alt Corporation 421
6
|
Posted - 2013.07.02 18:05:00 -
[12] - Quote
Texty wrote:Excuse me, can we have the "Your CapsLock is on" notifing feature for the ID/password field?
That's a good idea. Work that in when you can.
Atrophos, is there any further testing that I can do for you guys to determine the cause of the 324 errors? As far as I know, you guys have still not been able to replicate it despite numerous players clearly having the issue. I would be happy to try more things for you guys if you have ideas.
The latest theory handed down from you guys came to me from GM Karidor and then a support petition response a couple days later. You guys wanted me to try resetting my IP/TCP stack. I did; it didn't work for me. No one else has responded to GM Karidor's forum post as to whether or not it worked for them (the thread he replied to had been quiet for 3 weeks prior to his post though). That it didn't work didn't particularly surprise me; that seems much more like a local machine fix. I'd love to try any other theories though. |
Seth Toralen
Generic Alt Corporation 421
6
|
Posted - 2013.07.04 16:00:00 -
[13] - Quote
Oh my gosh.... now you all understand the pain of our 324 Errors. This is exactly what happens to us. |
|
|
|