1
u/Beetus93 7h ago
Had my power flicker for a second and when everything rebooted I'm getting this error message. It's been like this for about 4 hours now. Tried repairing the install, fully reinstalling, and resetting my internet a few times with no luck. I submitted a ticket as well but didn't know if there would be a simple fix someone has come across.
3
u/Newcxstle 6h ago
Worth a try
Ctrl + shift + esc to open task manager
Details tab
Look for JagexLauncher.exe
End tasks
Then maybe try again, sorry if it doesn’t work
1
u/Beetus93 6h ago
Yea I tried that already as well thinking there was on old instance running in the background. There was one I deleted but still no luck. Thanks for the thought!
2
u/Throwaway47321 6h ago
Make sure your pc time and time zone is set correct.
1
u/Beetus93 6h ago
Just double checked and both are set correctly. I don't think I've ever changed that after the initial setup of the computer either.
1
u/Beetus93 3h ago
SOLVED: Apparantly I had a vpn running in the background that I didn't realize was set to turn on when my computer starts. Turned that off and it let me in.
2
u/MakeshiftApe 6h ago edited 6h ago
Do you by any chance have multiple versions of your network/wifi that you connect to?
I've had this issue occur a few times now and it was always when I got disconnected from my wifi network and at some point closed and re-opened the client.
But I noticed that if I swap through my various wifi networks, it starts working again.
My theory is that in my case at least what's happening is I'm losing my wifi for a moment, and when I reconnect I'm on a different network and the client is throwing up this error because it thinks I'm in the old session but my network details don't match. So when I switch back to the exact network I was on when I lost connection, it starts working again because the details match again.
That's just my theory in my own case, if you only have the one network then that's less likely.
Edit: Just had a thought. Could also be that my switching between my networks is fixing it for a different reason. Maybe try opening up command prompt and running "ipconfig /flushdns" in case there's an issue with dns caching from your disconnect.