Troubleshooting

How to Get Error Logs

Error logs are essential for troubleshooting issues and getting help from Jan team. To get error logs from Jan, follow the steps below:

Through Jan Interface

1. Open System Monitor in the footer
2. Choose App Log

Through Terminal

Application Logs

Server Logs

Broken Build

To resolve the issue where Jan is stuck in a broken build after installation:

Following these steps, you can cleanly uninstall and reinstall Jan, ensuring a smooth and error-free experience with the latest version.

Cannot Relocate Data Folder on Windows

If you are unable to change the data folder location through Jan's interface on Windows, you can manually update it by editing the settings file:

1. Fully quit Jan (right-click the system tray icon → Quit)

2. Open File Explorer and navigate to:

   
   

   C:\Users\[username]\AppData\Roaming\Jan\

   
   

3. Open settings.json with a text editor (e.g. Notepad)

4. Find the "data_folder" field and update its value to your desired path, for example:

   
   

   {

   "data_folder": "D:\\Jan"

   }

   
   

5. Optionally, copy your data from the old folder to the new folder to preserve your models, chat history, and settings

6. Save the file and restart Jan

Jan will now use the new data folder location.

Troubleshooting NVIDIA GPU

To resolve issues when Jan does not utilize the NVIDIA GPU on Windows and Linux systems.

Tested Configurations

These configurations have been verified to work with Jan's GPU acceleration. You can use them as reference points for your setup.

Bare Metal Installations

Windows 11 Pro (64-bit)

Ubuntu 22.04 LTS

Virtual Machine Setups

Ubuntu on Proxmox VM

Performance Notes

• Bare metal installations provide better performance
• VM setups require proper GPU passthrough configuration
• Some laptop GPUs may have reduced performance
• Hybrid graphics (Optimus) may need additional configuration

Permission Denied

When running Jan, you might encounter the following error message:

Permission problems mainly cause this error during installation. To resolve this issue, follow these steps:

1. Open your Terminal

2. Execute the following command to change ownership of the ~/.npm directory to the current user:

This command ensures that the necessary permissions are granted for Jan's installation.

"Failed to fetch" or "Something's Amiss" errors

When you start a chat with a model and encounter a Failed to Fetch or Something's Amiss error, here are some possible solutions to resolve it:

1. Check System & Hardware Requirements

• Hardware dependencies: Ensure your device meets all hardware requirements
• OS: Ensure your operating system meets the minimum requirements (Mac (opens in a new tab), Windows, Linux (opens in a new tab)
• RAM: Choose models that use less than 80% of your available RAM
  • For 8GB systems: Use models under 6GB
  • For 16GB systems: Use models under 13GB

2. Check Model Parameters

• In Engine Settings in right sidebar, check your ngl (number of GPU layers) setting to see if it's too high
• Start with a lower NGL value and increase gradually based on your GPU memory

3. Port Conflicts

If you check your app logs & see "Bind address failed at 127.0.0.1:39291", check port availability:

Default Jan ports:

• Jan and Cortex API Server: 1337
• Jan Documentation: 3001

4. Factory Reset

A factory reset can resolve persistent issues by returning Jan to its original state. This will remove all custom settings, downloaded models, and chat history.

1. Go to Settings > Advanced Settings
2. At Reset To Factory Settings, click Reset

5. Try a clean installation

• Uninstall Jan & clean Jan data folders (Mac, Windows, Linux)
• Install the latest stable release

OpenAI Unexpected Token Issue

The "Unexpected token" error usually relates to OpenAI API authentication or regional restrictions.

Step 1: API Key Sepup

1. Get a valid API key from OpenAI's developer platform (opens in a new tab)
2. Ensure the key has sufficient credits & appropriate permissions

Step 2: Regional Access

1. If you're in a region with restricted access, use a VPN service from a supported region
2. Verify your network can reach OpenAI's API endpoints

Performance Issues

Models Running Slowly:

• Enable GPU acceleration (see NVIDIA section above)
• Use appropriate model size for your hardware
• Close other memory-intensive applications
• Check Task Manager/Activity Monitor for resource usage

High Memory Usage:

• Switch to smaller model variants
• Reduce context length in model settings
• Enable model offloading in engine settings

Frequent Crashes:

• Update graphics drivers
• Check system temperature
• Reduce GPU layers if using GPU acceleration
• Verify adequate power supply (desktop systems)

Jan CLI

Windows: running jan opens the Jan application window

If typing jan in a terminal opens the Jan desktop app instead of the CLI, your system is resolving the jan command to the app launcher rather than the CLI binary.

To fix this, add the CLI binary directory to your Path environment variable:

1. Open System Properties → Advanced → Environment Variables
2. Under System variables (or User variables), select Path and click Edit
3. Click New and add:
   
   

   C:\Users\<username>\AppData\Local\Programs\Jan\resources\bin

   
   
   Replace <username> with your Windows username.
4. Click OK to save, then open a new terminal window and try jan-cli instead.

Need Further Support?

If these solutions don't work:

1. Gather Information: Copy your error logs and note your system specs
2. Get Community Support: Join our Discord (opens in a new tab) and post in #🆘|jan-help with your logs and system info