Skip to content
👋 Jan

Server Settings

This page covers server-specific settings for Jan’s local API. For general Jan settings, see the main Settings Guide.

Accessing Server Settings

Section titled “Accessing Server Settings”

Navigate to Settings in Jan to configure server-related options.

Server Configuration

Section titled “Server Configuration”

API Server Settings

Section titled “API Server Settings”

Configure the local API server at Settings > Local API Server:

  • Host & Port - Network binding configuration
  • API Key - Authentication for API requests
  • CORS - Cross-origin resource sharing
  • Verbose Logging - Detailed request/response logs

See our API Configuration Guide for complete details.

Engine Configuration

Section titled “Engine Configuration”

Configure llama.cpp engine at Settings > Model Providers > Llama.cpp:

  • Backend Selection - Hardware-optimized versions
  • Performance Settings - Batching, threading, memory
  • Model Defaults - Context size, GPU layers

See our Engine Settings Guide for optimization tips.

Logging & Monitoring

Section titled “Logging & Monitoring”

Server Logs

Section titled “Server Logs”

Monitor API activity in real-time:

  1. Enable Verbose Server Logs in API settings
  2. View logs at System Monitor > App Log
  3. Filter by [SERVER] tags for API-specific events

Log Management

Section titled “Log Management”
  • Location: Stored in Jan Data Folder
  • Retention: Automatically cleared after 24 hours
  • Manual Clear: Settings > Advanced > Clear Logs

Performance Tuning

Section titled “Performance Tuning”

Memory Management

Section titled “Memory Management”

For optimal server performance:

  • High Traffic: Increase parallel slots in engine settings
  • Limited RAM: Reduce KV cache quality (q8_0 or q4_0)
  • Multiple Models: Enable model unloading after idle timeout

Network Configuration

Section titled “Network Configuration”

Advanced networking options:

  • Local Only: Use 127.0.0.1 (default, most secure)
  • LAN Access: Use 0.0.0.0 (allows network connections)
  • Custom Port: Change from default 1337 if conflicts exist

Security Considerations

Section titled “Security Considerations”

API Authentication

Section titled “API Authentication”
  • Always set a strong API key
  • Rotate keys regularly for production use
  • Never expose keys in client-side code

Network Security

Section titled “Network Security”
  • Keep server on localhost unless LAN access is required
  • Use firewall rules to restrict access
  • Consider VPN for remote access needs

Troubleshooting Server Issues

Section titled “Troubleshooting Server Issues”

Common Problems

Section titled “Common Problems”

Server won’t start:

  • Check port availability (netstat -an | grep 1337)
  • Verify no other instances running
  • Try different port number

Connection refused:

  • Ensure server is started
  • Check host/port configuration
  • Verify firewall settings

Authentication failures:

  • Confirm API key matches configuration
  • Check Authorization header format
  • Ensure no extra spaces in key

For more issues, see our Troubleshooting Guide.

Section titled “Related Resources”