Know Your Ports

localhost:11501Khajane 2 (K2) Treasury App Port Guide

Oct 24, 2026

localhost:11501

Khajane 2 (K2) Local App Port

Open https://localhost:11501

Opens the Khajane 2 app running on this computer. Note the https://

Localhost:11501 is the port used by the Khajane II (K2) desktop application. K2 is the Government of Karnataka’s Integrated Financial Management System, run by the Department of Treasuries, and it is what drawing and disbursing officers (DDOs) and treasury staff use for bill preparation and other treasury work. The installer, listed as “Khajane II Application” from DOT - Government of Karnataka, runs a small HTTPS server on your PC at https://localhost:11501.

Why does a web portal need a program on your PC at all? A web page can’t talk to USB hardware such as a Digital Signature Certificate (DSC) token on its own, so government portals that need signing usually ship a small local helper and have the page call it on localhost. The Department of Treasuries says a DSC is needed for work on K2, and that biometric registration is compulsory for every K2 user.

Two things trip most people up:

  • It’s https://, not http://. Typing http://localhost:11501 won’t work.
  • The certificate is self-signed. Your browser will show a “Your connection is not private” warning the first time. On your own machine, for this app, that’s expected.

Can You Open localhost:11501 From Another Device?

No, and for K2 you shouldn’t try. localhost means “this computer”, so the K2 app has to run on the same PC as your browser and your DSC token. Opening localhost:11501 on your phone looks for the app on your phone, where it doesn’t exist.

Don’t put the K2 app on the internet with a tunnel either. It is the bridge to your DSC token, and a public URL pointing at it is a public URL pointing at your signing setup. If you need K2 on a different computer, install the K2 app and your token driver there.

If 11501 Is Your Own App

Port 11501 isn’t reserved for K2. If you’ve picked it for your own dev server and want to share it, a Pinggy tunnel gives it a public URL:

SSH CLI
Mac / Linux Windows Powershell Windows CMD

That’s useful for showing a work-in-progress app to a teammate, testing it on a phone, or receiving webhooks. Keep it to apps you’d be fine with anyone reaching.

What Uses Port 11501

Khajane II (K2)

  • Khajane II Application: The Windows app from the Department of Treasuries that serves https://localhost:11501
  • K2 web portal: The treasury site your browser has open, which calls the local app

What K2 Works Alongside

  • DSC USB token: Your Digital Signature Certificate, plus the token driver from its vendor
  • Biometric registration: Done in person at your treasury, as the department requires for all K2 users

Get the K2 installer from your district treasury office rather than a third-party download site. The app needs to be installed and running before anything on https://localhost:11501 will load.

How to Troubleshoot Localhost:11501

If https://localhost:11501 won’t open, work through these in order:

Step 1: Check That the K2 App Is Running

Action: Start the Khajane II app from the Start menu or its desktop shortcut, then give it a few seconds.

How to check: Run netstat -ano | findstr :11501 in Command Prompt. A line ending in LISTENING means something is serving the port.

Step 2: Use https:// and Accept the Certificate

Action: Open https://localhost:11501 with the s.

How to fix the warning: In Chrome or Edge, click Advanced, then Proceed to localhost (unsafe) or Continue to localhost (unsafe). In Firefox, click Advanced, then Accept the Risk and Continue. Then go back to the K2 portal and retry.

Step 3: Look for a Port Conflict

Action: Make sure the program on 11501 is actually K2.

How to check: Take the PID from the last column of the netstat output and run tasklist /FI "PID eq <pid>". If it's some other program, close it and restart K2.

Common Problems and Solutions

"This site can't be reached" (ERR_CONNECTION_REFUSED)

Problem: Nothing is listening on port 11501.

Solution: The K2 app isn't running, or it crashed. Start it again. If it closes straight away, check whether your antivirus quarantined it.

"Your connection is not private" (NET::ERR_CERT_AUTHORITY_INVALID)

Problem: The browser doesn't trust K2's self-signed certificate.

Solution: This is expected for the K2 app on your own computer. Click Advanced and proceed. Only do this for localhost, never for a site on the internet.

404 or Blank Page After Proceeding

Problem: You accepted the warning and got a 404 or an empty page.

Solution: That usually just means the app is up and the certificate is accepted. The local app isn't meant to be browsed directly, so go back to the K2 portal and try again.

DSC Token Not Detected

Problem: K2 loads, but signing fails or finds no certificate.

Solution: Install the driver for your token's make, plug the token straight into the PC (not a hub), and check the certificate hasn't expired. If it still fails, contact your district treasury help desk.

Summary

  • What it is: https://localhost:11501 is where the Khajane II (K2) desktop app from Karnataka’s Department of Treasuries runs on your PC.
  • Who uses it: DDOs and treasury staff working on K2, alongside a DSC token.
  • Troubleshooting: Make sure the app is running, use https://, and accept the self-signed certificate warning.
  • Remote access: Don’t tunnel it. K2 needs to run on the same computer as your browser and DSC token.

Quick Check Commands (Windows)

# Is anything listening on 11501?
netstat -ano | findstr :11501

# Which program owns that PID?
tasklist /FI "PID eq <pid>"

# Open the K2 local app in your default browser
start https://localhost:11501