Stuck at connecting to Rockstar Services

23 Replies

optimistic-goldOP•3mo ago

test

optimistic-goldOP•3mo ago

2025-03-22T14_13_05-...

optimistic-goldOP•3mo ago

https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/wiki/Rockstar-Games-from-Epic-Games did do the #Rockstar Launcher opens showing the option to buy the game / Says the game is not owned part

GitHub

Rockstar Games from Epic Games

A games launcher for GOG, Amazon and Epic Games for Linux, Windows and macOS. - Heroic-Games-Launcher/HeroicGamesLauncher

optimistic-goldOP•3mo ago

didnt work

optimistic-goldOP•3mo ago

launcher.01.log

optimistic-goldOP•3mo ago

                   ##  **
                *####****.                    ┌──────────────────────Hardware──────────────────────┐
                  ###,                         PC: Apple MacBook Pro (16-inch, M2 Max, 2023)
               ...,/#,,,..                    │ ├: Apple M2 Max (8+4) @ 3.50 GHz
          /*,,,,,,,,*,........,,              │ ├󰍛: Apple M2 Max [Integrated]
        ,((((((//*,,,,,,,,,......             │ ├󰍛: 9.65 GiB / 30.85 GiB (31%)
       ((((((((((((((%............            └ └: 280.40 GiB / 459.36 GiB (61%) - btrfs
     ,(((((((((((((((@@(............          └ └: 91.96 GiB / 230.34 GiB (40%) - fuseblk
    (((((((((((((((((@@@@/............        └────────────────────────────────────────────────────┘
  ,((((((((((((((((((@@@@@&*...........
 ((((((((((((((((((((@@@@@@@&,...........     ┌──────────────────────Software──────────────────────┐
(((((((((((((((((((((@@@&%&@@@%,..........     OS: Fedora Linux Asahi Remix 41 (Workstation Edition)
 /(((((((((((((((((((@@@&%%&@@@@(........     │ ├: Linux 6.13.5-400.asahi.fc41.aarch64+16k
    ,((((((((((((((((@@@&&@@&/&@@@/..         │ ├󰏖: 2202 (rpm), 532 (nix-user), 57 (nix-default), 26 (
        /((((((((((((@@@@@@/.../&&            └ └: zsh 5.9
           .(((((((((@@@@(....
               /(((((@@#...                    DE: GNOME 47.4
                  .((&,                       │ ├: gdm-password 47.0 (Wayland)
                                              │ ├: Mutter (Wayland)
                                              │ ├󰉼: Adwaita
                                              └ └󰍛: asahi
                                              └────────────────────────────────────────────────────┘

                                              ┌────────────────────Uptime / Age────────────────────┐
                                                OS Age : 95 days
                                                Uptime : 2 days, 6 hours, 28 mins
                                                Battery: 60% (2 hours, 27 mins remaining) [Discharging
                                              └────────────────────────────────────────────────────┘

                   ##  **
                *####****.                    ┌──────────────────────Hardware──────────────────────┐
                  ###,                         PC: Apple MacBook Pro (16-inch, M2 Max, 2023)
               ...,/#,,,..                    │ ├: Apple M2 Max (8+4) @ 3.50 GHz
          /*,,,,,,,,*,........,,              │ ├󰍛: Apple M2 Max [Integrated]
        ,((((((//*,,,,,,,,,......             │ ├󰍛: 9.65 GiB / 30.85 GiB (31%)
       ((((((((((((((%............            └ └: 280.40 GiB / 459.36 GiB (61%) - btrfs
     ,(((((((((((((((@@(............          └ └: 91.96 GiB / 230.34 GiB (40%) - fuseblk
    (((((((((((((((((@@@@/............        └────────────────────────────────────────────────────┘
  ,((((((((((((((((((@@@@@&*...........
 ((((((((((((((((((((@@@@@@@&,...........     ┌──────────────────────Software──────────────────────┐
(((((((((((((((((((((@@@&%&@@@%,..........     OS: Fedora Linux Asahi Remix 41 (Workstation Edition)
 /(((((((((((((((((((@@@&%%&@@@@(........     │ ├: Linux 6.13.5-400.asahi.fc41.aarch64+16k
    ,((((((((((((((((@@@&&@@&/&@@@/..         │ ├󰏖: 2202 (rpm), 532 (nix-user), 57 (nix-default), 26 (
        /((((((((((((@@@@@@/.../&&            └ └: zsh 5.9
           .(((((((((@@@@(....
               /(((((@@#...                    DE: GNOME 47.4
                  .((&,                       │ ├: gdm-password 47.0 (Wayland)
                                              │ ├: Mutter (Wayland)
                                              │ ├󰉼: Adwaita
                                              └ └󰍛: asahi
                                              └────────────────────────────────────────────────────┘

                                              ┌────────────────────Uptime / Age────────────────────┐
                                                OS Age : 95 days
                                                Uptime : 2 days, 6 hours, 28 mins
                                                Battery: 60% (2 hours, 27 mins remaining) [Discharging
                                              └────────────────────────────────────────────────────┘

magic-amber•3mo ago

there seems to be some connectivity issues:

(15:21:38) ERROR:   [Backend]:          Failed to get epic service status with {
  "message": "timeout of 10000ms exceeded",
  "name": "AxiosError",
  "stack": "AxiosError: timeout of 10000ms exceeded\n    at RedirectableRequest.handleRequestTimeout (/tmp/.mount_HeroicLartL2/resources/app.asar/node_modules/axios/lib/adapters/http.js:657:16)\n    at RedirectableRequest.emit (node:events:519:28)\n    at Timeout.<anonymous> (/tmp/.mount_HeroicLartL2/resources/app.asar/node_modules/follow-redirects/index.js:210:12)\n    at listOnTimeout (node:internal/timers:573:17)\n    at processTimers (node:internal/timers:514:7)\n    at Axios.request (/tmp/.mount_HeroicLartL2/resources/app.asar/node_modules/axios/lib/core/Axios.js:45:41)\n    at runNextTicks (node:internal/process/task_queues:60:5)\n    at listOnTimeout (node:internal/timers:540:9)\n    at processTimers (node:internal/timers:514:7)\n    at mt (/tmp/.mount_HeroicLartL2/resources/app.asar/build/main/main.js:149:1419)\n    at kg (/tmp/.mount_HeroicLartL2/resources/app.asar/build/main/main.js:124:1500)\n    at Module._g (/tmp/.mount_HeroicLartL2/resources/app.asar/build/main/main.js:124:2231)\n    at /tmp/.mount_HeroicLartL2/resources/app.asar/build/main/main.js:199:6608\n    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:83537)",
  "config": {

(15:21:38) ERROR:   [Backend]:          Failed to get epic service status with {
  "message": "timeout of 10000ms exceeded",
  "name": "AxiosError",
  "stack": "AxiosError: timeout of 10000ms exceeded\n    at RedirectableRequest.handleRequestTimeout (/tmp/.mount_HeroicLartL2/resources/app.asar/node_modules/axios/lib/adapters/http.js:657:16)\n    at RedirectableRequest.emit (node:events:519:28)\n    at Timeout.<anonymous> (/tmp/.mount_HeroicLartL2/resources/app.asar/node_modules/follow-redirects/index.js:210:12)\n    at listOnTimeout (node:internal/timers:573:17)\n    at processTimers (node:internal/timers:514:7)\n    at Axios.request (/tmp/.mount_HeroicLartL2/resources/app.asar/node_modules/axios/lib/core/Axios.js:45:41)\n    at runNextTicks (node:internal/process/task_queues:60:5)\n    at listOnTimeout (node:internal/timers:540:9)\n    at processTimers (node:internal/timers:514:7)\n    at mt (/tmp/.mount_HeroicLartL2/resources/app.asar/build/main/main.js:149:1419)\n    at kg (/tmp/.mount_HeroicLartL2/resources/app.asar/build/main/main.js:124:1500)\n    at Module._g (/tmp/.mount_HeroicLartL2/resources/app.asar/build/main/main.js:124:2231)\n    at /tmp/.mount_HeroicLartL2/resources/app.asar/build/main/main.js:199:6608\n    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:83537)",
  "config": {

it looks like it's not just a rockstar issue but a more general thing with your connection (that error is from heroic's side) try changing you connection DNS servers (maybe google's 8.8.8.8 8.8.4.4) and also try disabling IPV6 (it's been causing issues for many users in other scenarios)

optimistic-goldOP•3mo ago

I also tried using a VPN which does change dns servers still no luck Some apps complain that im not connected to a wifi or ethernet when I am, or complain that they cannot get the system status etc also launchşg rdr2 from steam worked last time I checked which makes me believe this is a heroic issue

magic-amber•3mo ago

yeah, seems like something on your connection is blocking some epic endpoints can you open this URL in your browser? https://status.epicgames.com/api/v2/components.json that's what we check to see if the epic services are online

optimistic-goldOP•3mo ago

seems to open a json file do you want me to curl it and send the output?

magic-amber•3mo ago

nono, it's fine, I wanted to check if it was working or timing out so something is not letting heroic connect to that URL I think you are using the AppImage of heroic, right?

optimistic-goldOP•3mo ago

yes

magic-amber•3mo ago

can you try using a different package? just to check

optimistic-goldOP•3mo ago

not possible im using heroic under muvm it'ss either appimage or flatpack and flatpacks dont work under muvm,

magic-amber•3mo ago

for steam you are using appimage too?

optimistic-goldOP•3mo ago

steam comes with it's own wrapper on asahi let me check the script

magic-amber•3mo ago

hmmm I wonder if it's some issue with the combinatio nof asahi+muvm+appimage packages I don't have any way to test, but I wonder if other appimage applications have connection issues, to understand if it's a heroic issue or a combination of technologies

optimistic-goldOP•3mo ago

I believe steam is a native app

optimistic-goldOP•3mo ago

here's a screeenshot from steam also

optimistic-goldOP•3mo ago

 06c0:err:service:process_send_start_message service L"Rockstar Service" failed to start

 06c0:err:service:process_send_start_message service L"Rockstar Service" failed to start

I'm losing my mind It wasn't my fault Turns out r* messed something up because an old version of the launcher doesn't get stuck I'm still not resolving this as solved as I didn't find a fix I just found the cause I'm gonna apply for a job at r* just to fix this istg Ok this is really stupid so when RGL updates it updates 2 exe's Launcher.exe and RockstarService.exe and renames the old ones as Launcher.exe.old and same for RS.exe.old renaming RockstarService.exe.old to .exe again makes it so that the service manages to launch and then updates the service.exe so you need to do this before everytime you launch the game now I encounter this error https://canary.discord.com/channels/812703221789097985/1347680336901050469/1347680336901050469 Fixed by first launching r* launcher and then running the script trough wine explorer windows

optimistic-goldOP•3mo ago

now I'm waiting

optimistic-goldOP•3mo ago

I'm logged in on correct accounts in both launchers the launch button exists now ill update on how it goes goes back to "buy now" after trying to launch still stuck at this stage The root problem is the service not starting That needs a fix https://canary.discord.com/channels/812703221789097985/812710370551660554/1354053142383431760

Gaming

Programming

Stuck at connecting to Rockstar Services

Did you find this page helpful?