Troubleshooting

Where are the logs?

	Path
Crash reports	`<data dir>/crash-reports/`
Session logs	`<data dir>/logs/launcher.log`
Console output	Wrench icon in sidebar → Copy All

<data dir> is %LOCALAPPDATA%\Nexira (Windows), ~/Library/Application Support/Nexira (macOS), or $XDG_DATA_HOME/nexira (Linux). See Installation for the full table.

Launcher won’t start

Windows – crashes silently before the window appears

Make sure you’re running the official installer or portable ZIP from the releases page, not an older third-party build. Check %LOCALAPPDATA%\Nexira\logs\launcher.log for the actual crash stack.

Linux – AppImage won’t run

Install FUSE:

# Ubuntu/Debian
sudo apt install libfuse2

# Arch
sudo pacman -S fuse2

Linux – blank window or crash on Wayland

Nexira ships a Liberica JDK runtime that handles Wayland through XWayland natively; no extra env vars should be needed. If the window still doesn’t appear, check that the Skiko native dependencies are present:

# Arch
sudo pacman -S fontconfig freetype2 libglvnd

# Debian/Ubuntu
sudo apt install libfontconfig1 libfreetype6 libgl1

“SSL certificate error” warning

The SMARTYcraft API certificate sometimes expires before the operator renews it. Nexira shows an SSL bypass prompt with three grant durations:

1 hour – short outage, expect the cert to be fixed today
30 days – typical renewal cadence
Always (100 years) – if you’ve given up on upstream’s TLS hygiene

Granted bypasses appear in Settings → Network → SSL bypasses and can be revoked at any time. Credentials are still only sent to the SMARTYcraft API, just over a connection where the certificate isn’t validated.

“Bad login” or “User not found”

Check your credentials on smartycraft.ru. The launcher uses the same login as the website.

2FA accounts

Two-factor authentication works. Signing in on an account that has it asks for the code and completes the login.

What to know about it: SMARTYcraft ends the previous session every time an account signs in, and the launcher has to sign in again to hand the game a session it can vouch for. So a launch on a two-factor account asks for a fresh code, and starting a second game ends the first one’s session. The launcher never signs such an account in on its own, for the same reason – neither on startup nor from a background sync – so opening it while you are in game leaves that game alone.

Game won’t launch

Files keep re-downloading every time

Normal on first launch or after a server update. The launcher verifies file integrity (MD5) before each session.

Game crashes immediately

Open the console (wrench icon → Copy All) and look for Java errors. Common causes:

Not enough RAM – raise the memory cap in Server Settings → RAM
Incompatible optional mod – disable mods one by one in Server Settings → Mods

Custom JVM flags break the launch

The JVM args builder (Settings → Advanced → Launch, then the builder button in a pack’s or a server’s settings) lets you set custom GC, JIT, CDS and JFR flags. If a configuration breaks the launch, reset to defaults from the same screen.

Network issues

News feed empty / can’t fetch server list

Neither the news nor the server list needs an account, so an empty rail on a launcher you have not signed into means the host was not reached. Nexira reaches SMARTYcraft over a direct HTTPS connection, and if that host is unreachable from your network both stay empty – there is no alternate route. A VPN or a system-level proxy is the workaround.

If the host answers but its certificate has expired, the launcher asks about it wherever the refusal happened rather than only inside the login form. Accepting once puts the news and the server list back.

Stale data dir warnings

If you moved the data directory through Settings → Advanced → Data directory, the relocation applies on the next launcher start. The bootstrap config at ~/.nexira.conf records the target; check that file if migration appears stuck.

Offline mode

Enable Offline mode in Settings → Appearance → Behavior to skip authentication and file sync.