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.
 

Launcher problem AGAIN!!
Author
Previous Topic Next Topic
Pestily
State War Academy
Caldari State
#1 - 2015-08-13 13:40:50 UTC
as per usual the launcher will not update.. http://puu.sh/jA4n4.jpg

I have tried repair and that is doing nothing at all just closes everything..

I normally download a new launcher from the forums, after deleting my old launcher from the directory but today I am being told there is no updated launcher on the forums to download.. How do I get online then ???
Methiodine
Imperial Shipment
Amarr Empire
#2 - 2015-08-13 15:08:11 UTC
same problem here man... I'll be lurking on your post waiting for help as well.
Dream Weaver
Doped Player's Inc.
#3 - 2015-08-13 17:00:36 UTC  |  Edited by: Dream Weaver
Same here. Running windows 10.

here is the error log I get when running repair.exe

Traceback (most recent call last):
File "splunk.pyo", line 75, in emit
File "requests\sessions.pyo", line 504, in post
File "requests\sessions.pyo", line 461, in request
File "requests\sessions.pyo", line 573, in send
File "requests\adapters.pyo", line 431, in send
SSLErTraceback (most recent call last):
File "splunk.pyo", line 75, in emit
File "requests\sessions.pyo", line 504, in post
File "requests\sessions.pyo", line 461, in request
File "requests\sessions.pyo", line 573, in send
File "requests\adapters.pyo", line 431, in send
SSLError: [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Logged from file repair.py, line 204
Traceback (most recent call last):
File "splunk.pyo", line 75, in emit
File "requests\sessions.pyo", line 504, in post
File "requests\sessions.pyo", line 461, in request
File "requests\sessions.pyo", line 573, in send
File "requests\adapters.pyo", line 431, in send
SSLError: [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Logged from file repair.py, line 204
Traceback (most recent call last):
File "splunk.pyo", line 75, in emit
File "requests\sessions.pyo", line 504, in post
File "requests\sessions.pyo", line 461, in request
File "requests\sessions.pyo", line 573, in send
File "requests\adapters.pyo", line 431, in send
SSLError: [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Logged from file repair.py, line 204
Traceback (most recent call last):
Traceback (most recent call last):
File "splunk.pyo", line 75, in emit
File "requests\sessions.pyo", line 504, in post
File "requests\sessions.pyo", line 461, in request
File "requests\sessions.pyo", line 573, in send
File "requests\adapters.pyo", line 431, in send
SSLError: [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Logged from file repair.py, line 204
Traceback (most recent call last):
File "repair.py", line 254, in (the "module" keeps thinking it is html and won't post)
File "updateSelf.pyo", line 87, in UpdateSelf_nt
File "updateSelf.pyo", line 16, in ReadUpdateInfo
File "repairTool\repairTools.pyo", line 190, in GetRepairInfo
File "requests\api.pyo", line 65, in get
File "requests\api.pyo", line 49, in request
File "requests\sessions.pyo", line 461, in request
File "requests\sessions.pyo", line 573, in send
File "requests\adapters.pyo", line 431, in send
requests.exceptions.SSLError: [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Pestily
State War Academy
Caldari State
#4 - 2015-08-13 18:34:11 UTC  |  Edited by: Pestily
and still no reply from ticket so another day lost.... really not happy!!!!!!!!


WHY CANT CCP PUT THE NEW LAUNCHER VERSION ON THEIR POST https://ccpcommunity.zendesk.com/hc/en-us/articles/202664365-Reinstalling-the-Launcher INSTEAD OFF THE YESTERDAYS VERSION ..

THIS IS WHY WE CANNOT GET ONLINE .. IF THE LAUNCHER DOES NOT UPDATE OR WORK THEN GIVE US THE OPTION OF DOWNLOADING THE NEWER VERSION!!!!!!!!!
Tau Cabalander
Retirement Retreat
Working Stiffs
#5 - 2015-08-13 23:52:37 UTC  |  Edited by: Tau Cabalander
As per usual, have you checked for a malware proxy recently?

Check for, and disable any proxy.

Probably the #1 cause of EVE problems is stupid proxies installed by malware or "firewall" products.

http://goo.gl/3pbuHR

http://windows.microsoft.com/en-ca/windows/change-internet-explorer-proxy-server-settings
Pestily
State War Academy
Caldari State
#6 - 2015-08-14 06:56:12 UTC
Thanks Tau but it was not the problem... the problem is with the launcher because when finaly ccp responded 12 hours later and put the link for the new launcher on the forum I downloaded it and hey presto it works again.....



So today I recieve this..

GM Mechani GM Mechanic (EVE Online Customer Support)

Aug 13, 21:21

Hello, I am GM Mechanic.

Thank you for contacting customer support. My apologize for the delay in updating the link. I've now updated the link for you. Please see the following article.

https://ccpcommunity.zendesk.com/hc/en-us/articles/202664365

Best Regards,
GM Mechanic
CCP Customer Support | EVE Online | DUST 514 | EVE Valkyrie

Obviously it works, I have been getting my game to work by doing this for the last two years but why no explanation as to why we need to do this or wait 12 hours for a reply.. ??

What about the time lost AGAIN ! who pays for that .. oh wait it's me !!
Ransu Asanari
Perkone
Caldari State
#7 - 2015-08-14 09:21:18 UTC  |  Edited by: Ransu Asanari
Make sure to log a bugreport for this, and include the launcher log here:

C:\Program Files\CCP\EVE\launcher\cache (or whatever your install directory is).

Post the EBR number in this thread.

Reinstalling the Launcher is a workaround, but they should investigate the root cause.
Desmont McCallock
#8 - 2015-08-14 11:44:50 UTC  |  Edited by: Desmont McCallock
Another workaround is to delete the Cookies file in 'CCP/EVE/launcher/cache/BrowserCache'. This will reset your cookies (usernames you have entered) and clean up the login procedure.

Yet another workaround is to open the launcher settings, go to 'Advanced' and press 'Clear' on the 'Clear only cached usernames' option.