Troubleshooter¶
This chapter details common issues that may arise when using XRebel.
XRebel with adblock software¶
Popular ad-blocking browser extensions (e.g. uBlock) can cause XRebel to not function properly. Consider disabling adblock software for web applications that you run with XRebel enabled.
XRebel with Spring Loaded¶
XRebel cannot be used alongside the Spring Loaded agent. When starting XRebel, Spring Loaded is disabled at startup. You will be notified of this in the console:
XRebel: Spring-loaded agent has been disabled.
Activating using a license file¶
When you buy an XRebel license, you will receive the license file xrebel.lic via email. You need to activate using this file. This can be done via the activation dialog. However, when you do not have access to the activation dialog (for example with web applications that do not allow toolbar injection), you can also copy the xrebel.lic license file into the .xrebel folder within your user files folder.
Linux and Mac OS¶
When using Linux or Mac OS, the XRebel data folder is located in: /Users\username/.xrebel/.
XRebel license persistence in Docker containers¶
When running Java applications inside Docker, XRebel may request license activation after each container restart. This occurs because the container filesystem is temporary and the license file is not preserved.
To ensure the license persists, mount both the license file and the XRebel agent directory from the host system, and reference them through environment variables or JVM startup options used by your server:
environment:
JAVA_OPTS: >
-javaagent:/container/xrebel/xrebel.jar
-Dxrebel.license.file=/container/license/xrebel.lic
volumes:
- /host/path/xrebel.lic:/container/license/xrebel.lic
- /host/path/xrebel:/container/xrebel
This setup ensures the XRebel files remain stored outside the container, preventing repeated license prompts after restarts. It works for any Java-based server or application running in a Docker container.