Persistent Login Error in Linux Heroic Launcher/Legendary

[PadTrick]

Describe the bug

This issue was already posted, but closed by author https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/issues/4245.

I log into my Epic Account, after some seconds this popup appears. This error is also present in legendary.
I tried 4 different ISPs in 2 different cities on 3 different PCs with 3 different distros (Arch, Debian, Nobara) all produce this error.

• Logout and Login does not fix the issue.
• Rebooting the PC/Turning PC off and on does not fix the issue.
• Uninstalling and reinstalling Heroic Games Launcher does not fix the issue.
• Switching to another Linux Distro does not fix the issue.
• Heroic Games Library doesnt show any Epic Games.
• GoG Login works & GoG Games in Library are shown.

Add logs

Legendary (Epic Games)
Fehler:
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: Getting game list... (this may take a while)Traceback (most recent call last):
File "urllib3/connectionpool.py", line 536, in _make_request
File "urllib3/connection.py", line 507, in getresponseFile "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 1275, in recv_into
File "ssl.py", line 1133, in read
socket.timeout: The read operation timed out
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "requests/adapters.py", line 667, in send
File "urllib3/connectionpool.py", line 843, in urlopen
File "urllib3/util/retry.py", line 474, in increment
File "urllib3/util/util.py", line 39, in reraiseFile "urllib3/connectionpool.py", line 789, in urlopen
File "urllib3/connectionpool.py", line 538, in _make_request
File "urllib3/connectionpool.py", line 369, 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 3224, in <module>
File "legendary/cli.py", line 3133, in main
File "legendary/cli.py", line 201, in list_gamesFile "legendary/core.py", line 415, in get_game_and_dlc_list
File "legendary/core.py", line 361, in get_assetsFile "legendary/api/egs.py", line 170, in get_game_assets
File "requests/sessions.py", line 602, in get
File "requests/sessions.py", line 589, in requestFile "requests/sessions.py", line 703, in send
File "requests/adapters.py", line 713, in sendrequests.exceptions.ReadTimeout: HTTPSConnectionPool(host='launcher-public-service-prod06.ol.epicgames.com', port=443): Read timed out. (read timeout=10)
[PYI-5080:ERROR] Failed to execute script 'cli' due to unhandled exception!

Steps to reproduce

1. Start Heroic Launcher
2. Login to Epic Games
3. See error after logging in.

Expected behavior

1. Start Heroic Launcher
2. Login to Epic Games
3. Go to Library
4. All Epic Games should be listed

Screenshots

Heroic Version

Latest Stable

System Information

OS: Arch Linux x86_64
Kernel: Linux 6.12.9-zen1-1-zen
DE: KDE Plasma 6.2.5
WM: KWin (Wayland)
CPU: AMD Ryzen 7 5800X (16) @ 4.85 GHz
GPU: Intel Arc A770 @ 2.40 GHz [Discrete]
Memory: 32 GB

Additional information

No response

[arielj]

Have you tried using a VPN to connect from another country?

Since you say it happens with legendary I imagine it also happen with other tools that use legendary in the background, like Rare, but have you tried it?

I don't think this is a Heroic issue, you mentioned it happens even with legendary alone so it doesn't belong to this issues tracker, there's nothing we can do from heroic's side if legendary can't connect, it's not that Heroic is doing something wrong here.

I'd recommend asking in the legendary discord about this or maybe in our discord too for more visibility

[PadTrick]

Yes i have tried a VPN. Issue is the same.
Why is it closed if the problem isnt fixed ?
Heroic depends on Legendary (which causes this issue).
I only use Heroic, where i face this problem. So its a Heroic issue (for choosing to rely on software which has issues).
Seems like Epic has changed something about the API.

[arielj]

It's closed because the issue is not caused by Heroic, you said that: it's caused by legendary

I understand it affects any app using legendary then, so it should be reported in the legendary tracker, not here