Fix it yourself in a few minutes.

Check if the server is actually running

tasklist | findstr JadexVault

If nothing shows up, the service isn't running — double-click the desktop shortcut or find it in the Start Menu.

Check what's listening on port 7777

netstat -ano | findstr :7777

If another process is already using port 7777, Jadex Vault won't start. Note the PID in the last column, then find and close that process, or set a different port (see below).

Run on a different port

If port 7777 is already taken by something else, set the PORT environment variable before starting:

set PORT=8080
"C:\Program Files\JadexVault\JadexVaultServer.exe"

Find your machine's IP address (for LAN access)

ipconfig

Look for "IPv4 Address" under your active network adapter — teammates connect to https://<that-ip>:7777.

Restart the service cleanly

taskkill /IM JadexVaultServer.exe /F
"C:\Program Files\JadexVault\JadexVault.vbs"

Check service status

sudo systemctl status jadexvault

Look for "active (running)". If it says "failed" or "inactive", check the logs (below) for why.

View logs

sudo journalctl -u jadexvault -n 50 --no-pager

Restart the service

sudo systemctl restart jadexvault

Check what's listening on port 7777

sudo ss -tulpn | grep 7777

Or if ss isn't available:

sudo netstat -tulpn | grep 7777

Find your machine's IP address (for LAN access)

ip addr show | grep "inet "

Run on a different port

Edit the systemd service to add the PORT environment variable:

sudo systemctl edit jadexvault

Add these lines in the editor that opens, then save:

[Service]
Environment=PORT=8080

sudo systemctl daemon-reload
sudo systemctl restart jadexvault

Why this matters

Jadex Vault runs fine on localhost without any firewall changes. But if you want teammates on other devices to reach it, your OS firewall blocks incoming connections to port 7777 by default — this is the most common reason "it works on my computer but not my teammate's."

Windows Defender Firewall (GUI)

1. Open Windows Security → Firewall & network protection → Advanced settings.
2. Click Inbound Rules → New Rule...
3. Select Port → Next → TCP, Specific local ports: 7777 → Next
4. Allow the connection → Next → check all three profiles (or just Private if you're only on a trusted network) → Next
5. Name it "Jadex Vault" → Finish

The installer offers to create this rule automatically during setup — if you skipped that step, do it manually here.

Windows Firewall (Command Line)

Run as Administrator:

netsh advfirewall firewall add rule name="Jadex Vault" dir=in action=allow protocol=TCP localport=7777

Linux — ufw (Ubuntu/Debian default)

sudo ufw allow 7777/tcp
sudo ufw reload

Linux — firewalld (RHEL/CentOS/Fedora)

sudo firewall-cmd --permanent --add-port=7777/tcp
sudo firewall-cmd --reload

Verify it's actually open

From another device on the same network, try:

# Windows (PowerShell)
Test-NetConnection -ComputerName <server-ip> -Port 7777

# Linux/Mac
nc -zv <server-ip> 7777

If this fails but the firewall rule looks correct, double-check your router isn't running its own client-isolation feature (common on guest Wi-Fi networks) — devices on "Guest" networks often can't see each other regardless of firewall settings.