-
Notifications
You must be signed in to change notification settings - Fork 2
Troubleshooting
- Crash reports:
~/.aura/crash-reports/(Linux/macOS) or%AppData%\.aura\crash-reports(Windows) - Console output: click the wrench icon in the sidebar → Copy All
If you're reporting a bug, always attach the crash report or console output. See Bug reports.
Windows — crashes silently before the window appears
This is usually a JNA conflict. Make sure you're running the official installer or portable ZIP from the [releases page](https://github.com/Kitty-Hivens/Aura-Launcher/releases/latest) — not an older build.
Linux — AppImage won't run
Install FUSE:
sudo apt install libfuse2 # Ubuntu/Debian
sudo pacman -S fuse2 # ArchLinux — blank window or crash on Wayland
Try forcing XWayland:
_JAVA_AWT_WM_NONREPARENTING=1 ./AuraLauncher-*.AppImage"SSL certificate error" warning
The game server's SSL certificate may have expired. The launcher will show a warning — you can choose to connect anyway. Your credentials are not sent to any third party.
"Bad login" or "User not found"
Double-check your credentials on [smartycraft.ru](https://www.smartycraft.ru). The launcher uses the same login as the website.
Files keep re-downloading every time
This is normal on first launch or after a server update. The launcher verifies file integrity before each session.
Game crashes immediately
Check the console output (wrench icon → Copy All) for Java errors. Common causes:
- Not enough RAM allocated — go to server settings and increase memory
- Incompatible optional mod enabled — disable mods in server settings one by one
If you can't connect to the server, enable Offline mode in Settings → Behavior.
The launcher will skip authentication and file sync, using locally cached files.
Requires at least one prior online launch on the same server.