How to Make Koha Available in Network in 2026
Learn how to make Koha available in network so library staff can open the Koha staff client and OPAC from other computers using a local IP address, static IP setup, and simple troubleshooting steps.
Many beginners install Koha successfully, but then face one common problem: Koha opens on the server computer only. Staff computers, circulation desk systems, and OPAC terminals cannot access it. This usually happens because the Koha server IP address is not configured or shared properly on the local network.
This article explains how to make Koha available in network using beginner-friendly steps. The focus is local library access, not risky public internet exposure. You will learn how to find the server IP, test Koha from another computer, set a static IP, and fix common connection errors.
What It Means to Make Koha Available in Network
To make Koha available in network means that other computers connected to the same router, switch, WiFi, or LAN can open Koha through a browser. Instead of using Koha on one server only, library staff can use it from different systems inside the library building.
For example, the librarian may use the Koha staff client from the cataloging room, circulation staff may issue and return books from the front desk, and students may search the OPAC from a dedicated computer. This setup is very useful for schools, colleges, universities, public libraries, and small institutional libraries.
LAN Access vs Internet Access
Local network access and internet access are not the same. LAN access means Koha opens only inside your library network. Internet access means Koha can open from outside the building using a domain name, public IP, SSL, firewall rules, and secure hosting setup.
Beginners should start with LAN access first. It is easier, safer, and enough for most small libraries. Public internet access should be configured only when you understand server security, HTTPS, backups, firewall rules, and user permissions.
| Access Type | Best For | Security Level Needed |
|---|---|---|
| Local Network / LAN | Library staff, OPAC terminals, internal users | Basic firewall and strong Koha passwords |
| Public Internet | Remote access, hosted OPAC, online users | SSL, firewall, backups, secure hosting, updates |
Before You Start: Simple Checklist
Before changing any network setting, make sure Koha is already working on the server computer. Open the Koha staff client and OPAC locally first. If Koha does not open on the server, network sharing will not solve the problem.
You also need admin access to Ubuntu, access to the router or LAN network, and at least one other computer connected to the same network. Keep a note of your current IP address, gateway, and network interface name before making changes.
Required
Koha installed and running on Ubuntu server or local machine.
Required
All computers connected to the same router, switch, or WiFi network.
Required
Ubuntu admin password to check and update network settings.
Recommended
Use wired LAN for the Koha server for better speed and stability.
Find Your Koha Server IP Address
The first step is to find the local IP address of the computer where Koha is installed. This IP address is used by other computers to open the Koha staff client and OPAC.
Open Terminal on the Koha server and run this command:
ip aLook for an IP address that starts with something like 192.168.x.x, 10.x.x.x, or 172.16.x.x. In many small networks, it may look like this:
192.168.1.50enp0s3, ens33, eth0, or wlan0.
Quick Method: Test Koha from Another Computer
Before setting a static IP, test whether Koha is already reachable on your network. Go to another computer connected to the same router or WiFi and open a browser.
Replace the example IP address with your own Koha server IP. Try the OPAC and staff client URLs below:
http://192.168.1.50http://192.168.1.50:8080If these URLs open successfully, your Koha is already available on the network. The next important step is to set a static IP so the address does not change after restart.
Best 2026 Method: Set a Static IP for Koha Server
A dynamic IP can change when the server restarts or reconnects to the router. If the IP changes, staff computers will lose access because the old Koha URL will stop working. A static IP keeps the Koha server address fixed.
Modern Ubuntu systems commonly use Netplan for network configuration. First, check your Netplan files:
ls /etc/netplan/Open the Netplan file. The filename may be different on your system, such as 00-installer-config.yaml, 01-netcfg.yaml, or 50-cloud-init.yaml.
sudo nano /etc/netplan/00-installer-config.yamlHere is a simple example for a wired network interface. Change enp0s3, IP address, gateway, and DNS according to your own network:
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: no
addresses:
- 192.168.1.50/24
routes:
- to: default
via: 192.168.1.1
nameservers:
addresses:
- 8.8.8.8
- 1.1.1.1Save the file, then apply the new network configuration:
sudo netplan applyHow to Choose the Right Static IP Address
Choose an IP address that belongs to your router network but is not already used by another device. For example, if your router is 192.168.1.1, you may choose 192.168.1.50 for the Koha server.
Avoid using the same IP as your router, printer, CCTV, access point, or another computer. If your router has a DHCP range such as 192.168.1.100 to 192.168.1.200, choose an address outside that range, such as 192.168.1.50.
| Network Item | Example Value | What It Means |
|---|---|---|
| Router / Gateway | 192.168.1.1 | Main router address |
| Koha Static IP | 192.168.1.50 | Fixed address for Koha server |
| Subnet | /24 | Same as 255.255.255.0 |
| DNS | 8.8.8.8 or 1.1.1.1 | Used for internet name resolution |
Koha URLs to Open from Other Computers
After setting the server IP, use that address from any computer on the same network. The OPAC usually opens on the normal web port, while the staff client often opens on port 8080.
Use the following table as a simple reference. Replace 192.168.1.50 with your own Koha server IP address.
| Koha Area | Example URL | Used By |
|---|---|---|
| OPAC | http://192.168.1.50 |
Students, readers, library users |
| Staff Client | http://192.168.1.50:8080 |
Librarians and authorized staff |
| Server Test | ping 192.168.1.50 |
Network troubleshooting |
If Koha Does Not Open on Other Computers
If Koha does not open from another computer, do not panic. Most errors are caused by wrong IP address, different WiFi networks, firewall blocking, Apache service issues, or router isolation settings.
Use the troubleshooting table below to find the likely issue and fix it step by step.
| Problem | Likely Cause | Simple Fix |
|---|---|---|
| Browser says site cannot be reached | Wrong IP or server offline | Run ip a again and confirm the server is powered on |
| OPAC opens but staff client does not | Port 8080 blocked or staff site not active | Check Apache sites and firewall rules |
| Works on server but not on other PCs | Firewall or different network | Check sudo ufw status and confirm same WiFi/LAN |
| IP changes after restart | DHCP is enabled | Set a static IP using Netplan |
| Slow Koha loading | Weak WiFi or old server hardware | Use LAN cable, SSD, and enough RAM |
Useful Commands for Koha Network Checking
These commands help beginners check the network and Koha server status. Run them on the Koha server when something does not open correctly.
Start with the IP address, gateway, firewall, and Apache service because these are the most common points of failure.
ip aip route showsudo ufw statussudo systemctl status apache2sudo systemctl restart apache2Should You Allow Koha Through the Firewall?
If UFW firewall is active, you may need to allow HTTP and staff client access. For a basic LAN setup, many Koha installations need port 80 for OPAC and port 8080 for staff client.
Use these commands only if your firewall is enabled and blocking access:
sudo ufw allow 80/tcp
sudo ufw allow 8080/tcp
sudo ufw reloadReal Example: Small School Library Koha Network
Imagine a school library with one Koha server in the librarian office. The server has a static IP address: 192.168.1.50. Three staff computers and two OPAC terminals are connected to the same router.
Staff members open http://192.168.1.50:8080 for circulation and cataloging. Students open http://192.168.1.50 to search the OPAC. This simple setup makes Koha available in network without reinstalling Koha on every computer.
How to Make Koha Faster on a Local Network
Once you make Koha available in network, speed matters. A slow Koha server can frustrate staff during book issue, return, catalog search, and patron lookup. Network quality and server hardware both affect performance.
Use a LAN cable for the server instead of weak WiFi. Add an SSD if the server uses an old hard drive. Keep enough RAM, update Ubuntu regularly, and avoid running unnecessary software on the Koha server.
Use Wired LAN
A LAN cable is more stable than WiFi for the main Koha server.
Use SSD Storage
An SSD helps Koha pages, reports, and database queries load faster.
Keep Server Updated
Regular updates improve reliability and security.
Limit Heavy Use
Avoid running unrelated heavy apps on the Koha server.
Related Koha Resources from VWS Online
If you are learning Koha setup, installation, and library automation, these related resources can help you continue from basic network access to a more complete Koha environment.
Use these internal links to support your Koha learning and improve site navigation for readers.
Koha Installation
Koha Installation on Ubuntu explains the setup process for modern Ubuntu systems.
Koha Overview
Koha Open Source Library Management System explains what Koha is and why libraries use it.
Beginner Guide
A Guide to Koha Library Management System is useful for new Koha users.
Koha Live
Koha Live DVD is helpful for learning and testing Koha environments.
Library Automation
Open Source Library Automation compares useful library software options.
Koha Articles
Koha Category Archive includes more Koha tutorials and updates.
Frequently Asked Questions
How do I make Koha available in network?
Find the Koha server IP address, connect other computers to the same LAN or WiFi, then open the Koha OPAC or staff client using the server IP address in a browser.
What is the Koha staff client URL on a local network?
In many Koha setups, the staff client opens with the server IP and port 8080, such as http://192.168.1.50:8080.
What is the Koha OPAC URL on a local network?
The OPAC usually opens with the server IP address, such as http://192.168.1.50, depending on your Apache and Koha configuration.
Do I need internet to access Koha on LAN?
No. Koha can work inside a local network without internet as long as the server and client computers are connected to the same router or switch.
Why should I use a static IP for Koha?
A static IP keeps the Koha server address fixed. Without it, the IP may change after restart and staff computers may lose access.
Why is Koha not opening from another computer?
Common reasons include wrong IP address, firewall blocking, different WiFi network, Apache service issue, or router guest isolation.
Can I make Koha available on the internet?
Yes, but it needs proper security. Use a domain, SSL certificate, firewall rules, strong passwords, backups, and regular server updates.
Is WiFi enough for a Koha server?
WiFi can work for small testing, but a wired LAN connection is better for a stable library production server.
Final Thoughts
Learning how to make Koha available in network is one of the first practical steps after installing Koha. Once the server IP is fixed and other computers can open Koha, your library team can use circulation, cataloging, patron services, and OPAC access more smoothly.
For more Koha setup tutorials and library automation resources, visit Virtual World Solutions.
