HGL
xenial-black
Unable to stay logged into Epic
I am running into an issue where I am unable to log into Epic. It keeps disconnecting and telling me that it is offline. I have tried to clear cache, reset heroic, and the software is updated to the latest version. Cloud saves are disabled. It seemed to happen actually after the update. I know someone else posted this but they are using steam deck so some of the solutions don't work for me since the folder layout is different. As of right now I only have one game installed for Epic, most of the others are GOG which is working fine. Would appreciate advice.
7 Replies
xenial-blackOP•3y ago
Log reads as following:
Legendary (Epic Games)
Error:
An error has occurred! Try to Logout and Login on your Epic account.
[cli] INFO: Logging in...[Core] INFO: Trying to re-use existing login session...[cli] INFO: Checking for updates...Traceback (most recent call last):
File "urllib3\connectionpool.py", line 449, in _make_requestFile "<string>", line 3, in raise_from
File "urllib3\connectionpool.py", line 444, in _make_request
File "http\client.py", line 1377, in getresponse
File "http\client.py", line 320, in begin
File "http\client.py", line 281, in _read_status
File "socket.py", line 704, in readinto
File "ssl.py", line 1241, in recv_into
File "ssl.py", line 1099, in readsocket.timeout: The read operation timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "requests\adapters.py", line 489, in send
File "urllib3\connectionpool.py", line 785, in urlopen
File "urllib3\util\retry.py", line 550, in increment
File "urllib3\packages\six.py", line 770, in reraise
File "urllib3\connectionpool.py", line 703, in urlopenFile "urllib3\connectionpool.py", line 451, in _make_request
File "urllib3\connectionpool.py", line 340, in _raise_timeout
urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='launcher-public-service-prod06.ol.epicgames.com', port=443): Read timed out. (read timeout=10)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "legendary\cli.py", line 3069, in <module>
File "legendary\cli.py", line 2984, in mainFile "legendary\cli.py", line 607, in launch_game
File "legendary\core.py", line 361, in get_asset
File "legendary\core.py", line 349, in get_assets
File "legendary\api\egs.py", line 169, in get_game_assets
File "requests\sessions.py", line 600, in getFile "requests\sessions.py", line 587, in request
File "requests\sessions.py", line 701, in send
File "requests\adapters.py", line 578, in send
requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='launcher-public-service-prod06.ol.epicgames.com', port=443): Read timed out. (read timeout=10)
[6228] Failed to execute script 'cli' due to unhandled exception!
Update: downgraded back to 2.6.2 and everything works both GOG and Epic. Something is definitely up with the latest update that needs to be looked at. Will wait till patch or next version. Leaving here for devs to see.
inland-turquoise•3y ago
Probably reset heroic. I think we can't fix this.
xenial-blackOP•3y ago
I already reset heroic as noted above
Only thing that worked was downgrading back to previous version 2.6.2 via Github
exotic-emerald•3y ago
maybe you can try to keep Heroic 2.7.0 but downgrade Legendary using the legendary version from Heroic 2.6.2 using the Alternative binary advanced option if you want the new heroic features
if that work I feel it's an issue to report to the Legendary discord/github
xenial-blackOP•3y ago
What the heck is legendary? Huh?
I downloaded heroic. I've no idea what you're talking about. I don't use anything called legendary
Maybe heroic should test their stuff and get it working. Idk why upgrading my version of heroic would break whatever the heck that is
inland-turquoise•3y ago
Probably you should read about the programs you use!
Else your best choice is the official epic launcher then
exotic-emerald•3y ago
Heroic uses a project called Legendary in the background
we do test the releases, but there are edge cases that are only detected after a release, we can't test thousands of different setups