Please apologize to the 24,167 players who are having no issues logging in and playing…shut down servers…roll stuff back to where it worked 2 days ago…so the most important person in the world…“ME”…can get his eve fix 
Just Kidding
…sort of 
2 Likes
its about to be 5 days with no replay by ccp:/
In desperation, I went a-Googling this morning and found this post on a similar thread in the old forums, which has worked for me. I am now connected.
It appears to be a problem with the game certification, which needs to be fixed but here’s the workaround:
Credit goes to Kattara Aliastra
Ok, so it seems that the new launcher has some nice diagnostics built-in. So the issue appears to be here:
K:\Program Files (x86)\CCP\EVE\Shared\tq\code.ccp\requests\packages\urllib3\util\ssl_.pyj:318: SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#snimissingwarning.
.
.
.
K:\Program Files (x86)\CCP\EVE\Shared\tq\code.ccp\requests\packages\urllib3\util\ssl_.pyj:122: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
Ok So I have figured out a workaround for my issue.
- Run the “evelauncher.exe”
- Goto your taskbar at the bottom right and locate the small EVE symbol and Right click on it and go to Settings
- Place a check in the box “Ignore certification errors” and select OK.
- Login to eve
If it still doesn’t work, reboot your PC and try again - this worked for me.
2 Likes
Thx a lot, this seemed to work for me hopefully it last lol, no thx to ccp 
This time, cant even reach char selection.
edit: server restarted again and it is solved.
I tried this solution under wine, (using wineboot instead of rebooting, which is supposed to simulate a windows reboot), and it did not help. I did not see that error anywhere in the logs, either. I may be experiencing a different issue, though.
This worked for me with the caveat that I lost my overview, chat, really all my interface setups. Took a little over an hour to set everything back to rights, but I am able to log into game.
and this somehow didnt work for me great:/
Thanks for the information, but this did not work for me. I’m still able to access the Character Selection screen, but just get a black screen upon choosing a character. I just verified with a friend that when I’m looking at a black screen, he shows that character as online and music is playing in the background. So the character appears to connect, but I can’t see anything.
Again, everything works just fine on Singularity.
That workaround didn’t work for me either 
This didn’t work for me either on linux or windows. I am going to try completely reinstalling eve on my linux system now and see if that has any effect on anything.
how did reinstall go?.
So i uaing the network dignostic tool and running a trace route and well i had multiple requet timed out on the traceroute mabey that could be the problem?
Starting traceroute diagnostics - this may take several minutes
Starting tracert for launcher.eveonline.com
Tracing route to d1hoqe10mv32pv.cloudfront.net [13.32.202.57]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.0.1
2 587 ms 559 ms 590 ms 10.73.13.20
3 564 ms 588 ms 737 ms 10.73.10.18
4 594 ms 604 ms 595 ms 10.95.240.161
5 616 ms 611 ms 584 ms six01-sea4.amazon.com [206.81.80.147]
6 614 ms 594 ms 593 ms 52.95.53.0
7 586 ms 605 ms 564 ms 52.95.53.7
8 611 ms 672 ms 579 ms 205.251.226.83
9 570 ms 571 ms 673 ms 52.95.55.123
10 610 ms 608 ms 1097 ms 52.95.55.253
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 612 ms 581 ms 606 ms 13.32.202.57
Trace complete.
Starting tracert for binaries.eveonline.com
Tracing route to d17ueqc3zm9j8o.cloudfront.net [13.32.202.169]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.0.1
2 902 ms 558 ms 579 ms 10.73.13.20
3 596 ms 1119 ms 559 ms 10.73.10.18
4 588 ms 588 ms 578 ms 10.95.240.161
5 596 ms 610 ms 599 ms six01-sea4.amazon.com [206.81.80.147]
6 592 ms 606 ms 592 ms 52.95.52.18
7 604 ms 586 ms 619 ms 52.95.52.23
8 592 ms 598 ms 578 ms 205.251.225.73
9 649 ms 639 ms 636 ms 52.95.55.121
10 600 ms 596 ms 596 ms 52.95.55.253
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 612 ms 644 ms 638 ms 13.32.202.169
Trace complete.
Starting tracert for resources.eveonline.com
Tracing route to dm794883twbxj.cloudfront.net [13.32.202.79]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.0.1
2 555 ms 598 ms 558 ms 10.73.13.20
3 618 ms 597 ms 598 ms 10.73.10.18
4 * 629 ms 640 ms 10.95.240.161
5 629 ms 637 ms 640 ms six01-sea4.amazon.com [206.81.80.147]
6 645 ms 959 ms 639 ms 52.95.53.0
7 648 ms 646 ms 639 ms 52.95.53.9
8 645 ms 635 ms 641 ms 205.251.225.109
9 643 ms 638 ms 627 ms 52.95.55.125
10 1022 ms 689 ms 626 ms 52.95.55.253
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 642 ms 638 ms 640 ms 13.32.202.79
Trace complete.
Traceroute diagnostics finished
Here is my trace route you can see there are quite a few request timed out how could i fix request timed out?
1 Like
reinstalling it had no effect
Bump!
Time to get home from vacation Ccp!
I also have a few timeout’s on my trace route, but i also have the same number of timeouts on the trace route to the Singulaity test server which i can connect to without a problem so I don’t think they have a bearing on this problem.
1 Like
This morning I am able to connect again, I am not sure if they fixed it or i just got lucky, time will tell I guess. Time to make some isk 
1 Like
I was also able to get back in this morning. Stayed logged in throughout the day. Haven’t tried to log out and back in yet.
Last gaming session everything worked well, no black windows, no getting thrown out of the game with socket errors.
l guess a Jovian helped Ccp to fix this problem, well done - probably one of the few that has survived the havoc going on in the Jove system!
1 Like