Skip to content
This repository has been archived by the owner on Apr 8, 2023. It is now read-only.

Troubleshooting problems with the client

Jump to bottom
Gamer1120 edited this page Oct 9, 2019 · 3 revisions

If your client or launcher is not launching or is misbehaving, try one of the steps below to try to resolve the issue. Also make sure to check logs for presence of any Exception or ERROR:.

To find logs, do one of the following things:

  • Open the screenshot directory (if you have access to client by right-clicking "Camera" button) and navigate 1 directory up and then open logs folder
  • Navigate to %userprofile%\.runelite\logs on Windows or $HOME/.runelite/logs on Linux and macOS.

Table Of Contents

Client not launching

If you see error fetching bootstrap in launcher.log you are unable to connect to RL servers to get the bootstrap for startup. The error will be accompanied by an exception

  • ConnectException: Connection timed out - this is caused by either a firewall blocking the connection or a routing issue, try adding an exception in your firewall for OpenOSRS, reseting/changing your current network, or use a VPN.
  • IOException: Server returned HTTP response code: 403 - this means the server has seen your request but is denying you, in our case that would be cloudflare intentionally blocking your connection for whatever reason. Try changing networks, using a VPN, or contacting cloudflare to ask why you are getting blocked.
  • SSLHandshakeException: Received fatal alert: handshake_failure - this is caused by java certs not matching refer to Problems with accessing API or downgrade your java version to 8
  • SignatureException: Signature length not correct: got 0 but was expecting 512 - this is caused by your router or some other software middle manning the connection to the RL server, try logging into your router to disable that "feature" or contact your isp to ask what they are doing.

If you see Error loading RS! in the client.log you are unable to get the osrs client from jagex. The error will be accompanied by an exception

  • SocketTimeoutException: timeout - this means the connection took too long to either connect or receive any data, most of the time caused by a slow or inconsistent internet connection, you can try resetting your network or maybe using a VPN.

Problems with accessing API

If you see SSLException in client.log this probably means that you do not have your Java certificates properly set-up. Workaround is here. TLDR:

printf '\xfe\xed\xfe\xed\x00\x00\x00\x02\x00\x00\x00\x00\xe2\x68\x6e\x45\xfb\x43\xdf\xa4\xd9\x92\xdd\x41\xce\xb6\xb2\x1c\x63\x30\xd7\x92' | sudo tee /etc/ssl/certs/java/cacerts
sudo /var/lib/dpkg/info/ca-certificates-java.postinst configure

Launcher immediately closing

If you see ConnectionException in launcher.log this most likely means that launcher is trying to use Ipv6 instead of Ipv4 when connecting to OpenOSRS repository. If you downloaded launcher before July 7th 2018, redownload it from https://openosrs.com.

Settings being reset

If you see something like IllegalArgumentException: Malformed \uxxxx in client.log and your client is not launching (launcher closing immediately but nothing opens) open %userprofile%\.runelite\settings.properties on Windows or $HOME/.runelite/settings.properties on macOS and Linux and check if it contains weird \u0000 symbols at bottom. If yes, delete them and save the file.

Client freezing

A Java bug can result in freezes when users are using the All Platform version of RuneLite (.jar) with Java 10. Try using Java 8, or Java 11 and newer.

Ubuntu 18.04 users should install openjdk-8-jre. Arch Linux users should install jre8-openjdk or jre-openjdk.

Client closing when loading

This looks like corrupted jagex cache issue. Try to delete %userprofile%\jagexcache on Windows or $HOME/jagexcache on macOS and Linux.

FPS problems, screen flickering or artifacts

Be sure to check out this guide on how to disable Hardware Acceleration.

Client bouncing up and down in macOS tray

This is caused by missing software for OpenGL in your system. You can either disable hardware acceleration or install required software.

To install the software, open your terminal and install homebrew (https://brew.sh/) and then type:

brew install glfw3
brew install glew

Now client should launch properly.

Client stuck at "Loaded update list" on Linux

This is caused by PulseAudio not being supported for Java. A workaround for this is to use Alsa instead. This can be done by adding the following line to the sound.properties file which is located at $JAVA_HOME/conf/sound.properties:

javax.sound.sampled.Clip=com.sun.media.sound.DirectAudioDeviceProvider
javax.sound.sampled.Port=com.sun.media.sound.PortMixerProvider
javax.sound.sampled.SourceDataLine=com.sun.media.sound.DirectAudioDeviceProvider
javax.sound.sampled.TargetDataLine=com.sun.media.sound.DirectAudioDeviceProvider

Your JAVA_HOME is by default located at /usr/lib/jvm/.

Client not launching on Linux

This looks like bug with JDK 10+. The solution is either to downgrade to JDK 8 (or 9) or to delete /usr/lib/jvm/java-11-openjdk-amd64/conf/accessibility.properties (for JDK 11 on Ubuntu, for 10 the path should be similar).

PulseAudio forcibly taken over by client

If OpenOSRS is taking over your entire PulseAudio, then you're likely missing "pulseaudio-alsa". Getting that package should resolve any sound conflicts, you can now listen to sounds and play music on your browser again.

Client crashing on login

This is probably related to some versions of vanilla client, there are few possible solutions

  • Login to vanilla (OSRS) client and move (try teleporting to Lumbridge for example) and then login back to OpenOSRS
  • Try installing the 32-bit version instead of the 64-bit version
  • Try running the .jar (all platforms) version with latest Java version
  • See Client closing when loading

Please join our Discord if you notice anything wrong or would like to discuss an addition to the wiki.

Table of Contents

Clone this wiki locally