Steam offline bug #159
Comments
|
Just chiming in to say that I have this issue as well. |
|
Same here. |
|
I have it too. It seems to have started in the last GOG update (2.0.60, I think). |
|
+1 |
|
Same here |
|
Hi, I have the same problem. I had steam integration running. But in the last days y need reinstall GOG because when try update I have a error. The updater recommended reinstall Galaxy, and I did it. All integrations are running, except steam. I try download, and I try use old plugin (I had backup) always have de same error. I'm login correctly sure. I closed old GOG configuration in steam security tool. Steam wants you use QR code. Capture with your phone and continue. It is possible this is the problem? |
|
I also have this issue as of the last GOG update. |
|
I was having some problems updating GOG, due to having the standalone and also the Epic Games version both installed. |
|
I have the same issue. |
|
+1 |
|
I hope someone still working on this cuz I got the same issue, why it happened all of sudden. I shouldn't update GOG Galaxy. |
|
+1 |
1 similar comment
|
+1 |
|
same issue |
|
+1 |
|
Same for me - uninstalled and reinstalled several times, manually gone through and deleted all references to GOG in my system files. Tried installing an older version also, but that didn't work. Still just get 'Steam offline'. |
|
Same case here. |
|
+1 |
|
Same here, took a few hours to check what was happening. I looked at updating the protobuf model, and while there are some suspicious changes and deprecation, it is hard to tell whether there has been major protocol changes just by looking at data definitions. Note that this is not an isolated issue, looking at this one on SteamKit. |
|
is it possible to manually switch for public_profiles for now? I deleted my old plugin folder (and my saved profile, I'm guessing), so I'm not sure how the public_profiles Edit: public_profiles prompts for SteamID64, so that's at least figured out. It also fails with the "Offline" and bad retry link |
public_profiles doesn't work too |
|
This repo features pretty outdated documentation. Been trying to follow the Getting this set up on a windows env has been a nightmare, and I'm not even sure I have the right |
|
@FriendsOfGalaxy I do not think this is can be fixed by outside coders due to the lack of a |
|
+1 Is this integration abandoned? |
I desperately hope not - 90% of my library is steam. Is there a workaround? |
|
Yep, same issue. Started after latest GoG Galaxy update for me. It's really frustrating that out of 13 integrations (not including the "official" ones), 7 of them don't work now. |
|
It sure looks abandoned, the last update was on November 4, 2021. It's a pitty GoG doesn't invest some ressources in maintaining the integrations. Without Steam integration, GoG Galaxy is pretty much pointless. :( Of course, anybody with the proper background could fix it. I don't have the proper background, though :( |
|
Just tried to replicate this and at first it seemed like it did happen, but on deleting my cache it no longer presents itself so idk |
|
The "Importing Steam games..." not going away is usually a sign that the plugin is stuck in games import and did not present a list of games to galaxy. Most probably, there was an uncaught exception which caused the game import thread of the plugin to crash. This leaves Galaxy in the 'importing' state while the plugin won't ever send the list of games. Check your log file for Python exceptions prior to the passage where only ping-pong message are present. |
|
Thank you @ABaumher Your Fix worked for me :) |
Thx for tips ;-) |
also worked for me thanks |
|
|
|
|
|
lonewolf0708@766dd51 works |
|
It still not working for me. I downloaded all files from https://github.com/lonewolf0708/galaxy-integration-steam/tree/master/src and pasted them into the Steam plugin folder. Can anyone point out what I am doing wrong? PS. |
|
Don't mess with source code and just use https://github.com/GOG-Nebula/galaxy-integration-steam/releases/tag/v1.0.7 |
|
Using the above-mentioned repo for the plugin indefinitely stays on "Importing Steam" with nothing happening in GOG.
|
Have you also tried ABaumher's 1.2.0 beta he suggested? https://github.com/ABaumher/galaxy-integration-steam/releases/tag/v1.2.0beta |
It worked perfectly! Thanks! Question: Is there any chance these corrections made by lonewolf0708 will be downloadable through the launcher? Example: Amazon Games never got downloadable through the launcher. I had to install it manually just like this one. I'm certenaly this is hurting GOG Galaxy as a whole because most people do not do what we're doing and, without the plugins, they don't use GOG at all. |
I followed this today and worked perfectly. thank you @lonewolf0708 and @musterknabe !!! Just will add the file location for windows is: %localappdata%\GOG.com\Galaxy\plugins\installed\steam_ca27391f-2675-49b1-92c0-896d43afa4f8 |
|
It's 1 or 2 weeks, the steam plugin doesn't work anymore, (I have https://github.com/GOG-Nebula/galaxy-integration-steam/releases/tag/v1.0.7 version). Reinstalled it, but nothing. It stays "not connected" and I cannot launch anymore steam games. 2023-12-24 12:00:41,598 - galaxy.api.jsonrpc - INFO - Handling request: id=4, method=init_authentication, params={'stored_credentials': '****'}
2023-12-24 12:00:41,598 - steam_network.user_info_cache - INFO - Loaded account_username from stored credentials
2023-12-24 12:00:41,598 - steam_network.user_info_cache - INFO - Loaded persona_name from stored credentials
2023-12-24 12:00:41,598 - steam_network.user_info_cache - INFO - Loaded refresh_token from stored credentials
2023-12-24 12:00:41,598 - steam_network.user_info_cache - INFO - Loaded steam_id from stored credentials
2023-12-24 12:00:41,813 - steam_network.websocket_list - DEBUG - Got servers from backend: ['ext2-par1.steamserver.net:27025', 'ext2-par1.steamserver.net:27035', 'ext2-par1.steamserver.net:27033', 'ext2-par1.steamserver.net:27030', 'ext2-par1.steamserver.net:27023', 'ext2-par1.steamserver.net:27037', 'ext2-par1.steamserver.net:27022', 'ext2-par1.steamserver.net:27029', 'ext2-par1.steamserver.net:27031', 'ext2-par1.steamserver.net:27034', 'ext2-par1.steamserver.net:27038', 'ext2-par1.steamserver.net:27019', 'ext2-par1.steamserver.net:27024', 'ext2-par1.steamserver.net:27028', 'ext2-par1.steamserver.net:27032', 'ext2-par1.steamserver.net:27021', 'ext2-par1.steamserver.net:27020', 'ext1-par1.steamserver.net:27023', 'ext1-par1.steamserver.net:27019', 'ext1-par1.steamserver.net:27021', 'ext1-par1.steamserver.net:27035', 'ext1-par1.steamserver.net:27032', 'ext1-par1.steamserver.net:27022', 'ext1-par1.steamserver.net:27034', 'ext1-par1.steamserver.net:27036', 'ext1-par1.steamserver.net:27024', 'ext1-par1.steamserver.net:27030', 'ext1-par1.steamserver.net:443', 'ext1-par1.steamserver.net:27031', 'ext1-par1.steamserver.net:27029', 'ext1-par1.steamserver.net:27020', 'ext1-par1.steamserver.net:27033', 'ext1-par1.steamserver.net:27038', 'ext1-par1.steamserver.net:27037', 'ext1-par1.steamserver.net:27028', 'ext1-par1.steamserver.net:27025', 'ext2-par1.steamserver.net:27036', 'ext2-par1.steamserver.net:443', 'ext2-ams1.steamserver.net:27031', 'ext2-ams1.steamserver.net:27032', 'ext2-ams1.steamserver.net:27021', 'ext2-ams1.steamserver.net:27019', 'ext2-ams1.steamserver.net:27028', 'ext2-ams1.steamserver.net:27037', 'ext2-ams1.steamserver.net:27036', 'ext2-ams1.steamserver.net:27025', 'ext2-ams1.steamserver.net:27035', 'ext2-ams1.steamserver.net:27030', 'ext2-ams1.steamserver.net:27038', 'ext2-ams1.steamserver.net:27034', 'ext2-ams1.steamserver.net:27029', 'ext2-ams1.steamserver.net:27020', 'ext2-ams1.steamserver.net:27024', 'ext2-ams1.steamserver.net:27033', 'ext2-ams1.steamserver.net:27023', 'ext2-ams1.steamserver.net:27022', 'ext1-ams1.steamserver.net:27037', 'ext1-ams1.steamserver.net:27033', 'ext1-ams1.steamserver.net:27028', 'ext1-ams1.steamserver.net:27030', 'ext1-ams1.steamserver.net:27020', 'ext1-ams1.steamserver.net:27024', 'ext1-ams1.steamserver.net:27034', 'ext1-ams1.steamserver.net:27025', 'ext1-ams1.steamserver.net:27022', 'ext1-ams1.steamserver.net:27031', 'ext1-ams1.steamserver.net:27019', 'ext1-ams1.steamserver.net:27023', 'ext1-ams1.steamserver.net:27029', 'ext1-ams1.steamserver.net:443', 'ext1-ams1.steamserver.net:27035', 'ext1-ams1.steamserver.net:27032', 'ext1-ams1.steamserver.net:27036', 'ext1-ams1.steamserver.net:27021', 'ext1-ams1.steamserver.net:27038', 'ext2-ams1.steamserver.net:443', 'ext1-fra1.steamserver.net:27035', 'ext1-fra1.steamserver.net:27034', 'ext1-fra1.steamserver.net:27019', 'ext1-fra1.steamserver.net:27037', 'ext1-fra1.steamserver.net:27030', 'ext1-fra1.steamserver.net:27020', 'ext1-fra1.steamserver.net:27023', 'ext1-fra1.steamserver.net:27033', 'ext1-fra1.steamserver.net:27021', 'ext1-fra1.steamserver.net:27025', 'ext1-fra1.steamserver.net:27032', 'ext1-fra1.steamserver.net:27022', 'ext1-fra1.steamserver.net:27031', 'ext1-fra1.steamserver.net:27029', 'ext1-fra1.steamserver.net:27028', 'ext1-fra1.steamserver.net:27024', 'ext1-fra1.steamserver.net:27038', 'ext1-fra1.steamserver.net:27036', 'ext2-fra2.steamserver.net:27032', 'ext2-fra2.steamserver.net:27025', 'ext2-fra2.steamserver.net:27037', 'ext2-fra2.steamserver.net:27030', 'ext2-fra2.steamserver.net:27021', 'ext2-fra2.steamserver.net:27024']
2023-12-24 12:00:41,880 - steam_network.websocket_client - INFO - Connected to Steam on CM wss://ext2-par1.steamserver.net:27025/cmsocket/ on cell_id 0. Sending Hello
2023-12-24 12:00:41,880 - steam_network.protocol.protobuf_client - INFO - [Out] <EMsg.ClientHello: 9805> (21B)
2023-12-24 12:00:41,881 - steam_network.websocket_client - INFO - Got dict_keys(['mode']) from queue
2023-12-24 12:00:41,881 - steam_network.websocket_client - INFO - Finalizing Log in using the new auth refresh token and the classic login call
2023-12-24 12:00:41,881 - steam_network.protocol.protobuf_client - INFO - Websocket state is: OPEN
2023-12-24 12:00:41,881 - steam_network.protocol.protobuf_client - INFO - Sending log on message using access token
2023-12-24 12:00:41,881 - steam_network.protocol.protobuf_client - INFO - [Out] <EMsg.ClientLogon: 5514> (630B)
2023-12-24 12:00:42,336 - steam_network.protocol.protobuf_client - INFO - [In] 1 -> EMsg.Multi
2023-12-24 12:00:42,336 - steam_network.protocol.protobuf_client - INFO - New session id: -1249346362
2023-12-24 12:00:42,337 - steam_network.protocol.protobuf_client - INFO - [In] 751 -> EMsg.ClientLogOnResponse
2023-12-24 12:00:42,337 - steam_network.protocol.protobuf_client - INFO - Failed to log on, reason : eresult: 27
eresult_extended: 27
count_loginfailures_to_migrate: 0
count_disconnects_to_migrate: 0
2023-12-24 12:00:42,337 - steam_network.protocol.protobuf_client - INFO - Extended info : 27
2023-12-24 12:00:42,337 - steam_network.protocol_client - WARNING - authenticate_token failed with code: 27
2023-12-24 12:00:42,337 - steam_network.utils - ERROR - Error Received: Expired
2023-12-24 12:00:42,337 - steam_network.websocket_client - ERROR - Failed to establish authenticated WebSocket connection UnknownError()
2023-12-24 12:00:42,338 - steam_network.websocket_client - ERROR - Traceback (most recent call last):
File "C:\Users\<me>\AppData\Local\GOG.com\Galaxy\plugins\installed\steam_ca27391f-2675-49b1-92c0-896d43afa4f8\steam_network\websocket_client.py", line 98, in run
await auth_task
File "C:\Users\<me>\AppData\Local\GOG.com\Galaxy\plugins\installed\steam_ca27391f-2675-49b1-92c0-896d43afa4f8\steam_network\websocket_client.py", line 297, in _all_auth_calls
ret_code = await self._protocol_client.finalize_login(self._user_info_cache.account_username, self._user_info_cache.steam_id, self._user_info_cache.refresh_token, auth_lost_handler)
File "C:\Users\<me>\AppData\Local\GOG.com\Galaxy\plugins\installed\steam_ca27391f-2675-49b1-92c0-896d43afa4f8\steam_network\protocol_client.py", line 290, in finalize_login
raise translate_error(result)
galaxy.api.jsonrpc.UnknownError |
|
Eresult for Expired is a new one. I've never seen that before, but it might be a legitimate edge case. In the meantime, try deleting gog's steam cache; the expired credentials will be deleted along with it. Gog stores the cache in the same group of files as the logs, though I'm not sure where atm. It should be up one directory from where the logs are, in a file called "cache" iirc. Deleting the cache can sometimes fix errors that result from something being invalid.i don't usually recommend it because it usually is masking a bug elsewhere but it can fix issues between versions or if you've applied manual tweaks. In your particular case, it's just masking a potential oversight in the code; it should treat that the same way it treats authentication failed. That said, I've never seen that before, usually an expired refresh token triggers a different error. |
|
I didn't want to reimport everything, but log-out completely the plugin then relog worked somehow 👍 |
|
🎉🎉 Release Update: 🎉🎉 1.0.8 and 1.2.1 Beta are now available! These are minor fixes but if you have been here since the first release, you may have need of these. Your credentials remain valid for roughly seven months using the web authentication refresh and access token scheme. For the astute among you, this happened mid-December... and you've had issues suddenly pop up. This was something we knew might happen and we tried to address it, but we couldn't confirm it as we couldn't force the tokens to expire early. We could invalidate them, which we did, but this actually causes a different error. So, now that we know what error really happens, we've released a new patch that will handle this edge case and recover back to the login page. V 2.0 should have a nicer page to explain that they expired, but for now you'll just be hit with a login prompt every 7 months or so. Please see the latest at #178 |
|
So... I'm dumb. I forgot a colon in my releases but it was there in my testing. Not sure how, but i'm glad for y'all finding it so fast. if you grabbed 1.0.8 or 1.2.1 yesterday, please go back to the releases and grab the updated zips. I apologize for the mistake. Plus side, this is why Nebula has review requirements, so most of you won't get this |
No need for apologies mate! What you're doing for the community is beyond us. I just wished it was downloadable through the launcher because most people do not do what we do here and, without the plugins, most don't use GOG at all. |
|
1.0.8 is not sync well, some games i bought today are not appearing (The Metronomicom, Fort Triumph, Joe Danger, Joe Danger 2, etc)
|
|
This is still an issue. |
|
Hello all, with new version I am able to connect but it doesn't import nothing from library, achievements or play time |
|
I will need your logs to help diagnose your issue. You can find their location on the main page of either my or nebula's repos. i don't recall it off the top of my head. If you have a large collection of games there may be multiple files. I recommend deleting all your logs and trying to use galaxy again so I'm starting with a fresh group of logs. |
This the right log? |
Hello. I will attach mine. I am using the 1.2.1 beta version. It doesn't import nothing from a while ago... Tried everything so far, nothing seems to fix the issue |
Hello, those are updated Steam logs, still with the issue |
|
@Queue3612 the steam logs, not the galaxy client. Client can be useful but not in this case. @Danyelalejandro I'm seeing a lot of games appear in your log. This leads me to believe it's getting your credentials correctly and logging you in (as you mentioned) but it's taking too long to gather all that information and gog thinks our plugin is unresponsive and shuts us down. Unfortunately there isn't a good solution at this time for massive libraries, and from what i saw on initial look that appears to be what you're dealing with. |
I understand. I will wait for versión 2.0 then. Thank you |
|
and others
Describe the bug
While trying to log in to steam with plugin in the GOG app tries to load but it always ends with a message "Offline. Try again."
To Reproduce
Expected behavior
An expcted behaviour should be the abillity to log in and synchronise my games within the GOG Galaxy launcher
The text was updated successfully, but these errors were encountered: