Open Jira to Your Team Port 8080 and Windows Firewall
Install complete, wizard done — and only one person in the office can see Jira: whoever stands at the server. This guide opens it to your team safely, in the right order.
✍️ Technical Anshu🪟 Windows⏱️ 5 minute fix
🎥 The install video ends at first login — this guide takes it to the whole team
The gap between "installed" and "used by the office" is almost always three small things: a fixed address, one firewall rule, and a URL the team can remember. Here they are, plus the one shortcut you must never take.
From localhost to the whole team — the access chain (illustration)
On the server itselfhttp://localhost:8080 — works
From a team PC, blockedWindows Firewall — no inbound rule yet
Team URL after the fixhttp://192.168.1.50:8080 (example)
Directly on the public internetNever — use VPN or a secured proxy
👆 The classic pattern: Jira works on the server and nowhere else. That is almost never a Jira fault — it is the firewall doing its job. Example IP shown; yours will differ.
1
Why Localhost Works but the Team Cannot Connect
During setup you open http://localhost:8080 on the server itself. That traffic never leaves the machine, so nothing can block it. When a colleague opens the server's address from their PC, the request arrives at the server's network card — and Windows Defender Firewall drops it, because no rule yet says Jira may receive connections. One inbound rule fixes it.
2
Give the Server a Fixed Address First
Set a static IP on the server (or a DHCP reservation on your router) so its address never changes. A Jira that moves house weekly will lose its team.
Find the address: open Command Prompt on the server and run ipconfig — note the IPv4 address.
The team URL becomes http://SERVER-IP:8080 — for example http://192.168.1.50:8080. A friendly name like http://jira:8080 needs a DNS entry; ask whoever manages your network, or use the IP meanwhile.
3
Add the Firewall Rule
On the server, open Windows Defender Firewall with Advanced Security.
Choose Inbound Rules → New Rule → Port.
Select TCP, specific local port 8080 (or whichever port you chose in the installer).
Allow the connection, apply it to the Domain and Private profiles — not Public — name it something honest like Jira 8080 LAN, and finish.
Test from a colleague's PC, not from the server. Server-side tests prove nothing about the network path.
4
The Internet Question — Answer It Carefully
Remote staff will ask for Jira "from home". Do not forward port 8080 on your router to an unpatched or plain-HTTP Jira. The professional routes are a VPN into the office network, or a reverse proxy with HTTPS in front of Jira, ideally with additional sign-in protection. For a Server edition that no longer receives security patches, VPN-only access is the honest recommendation.
🎥 Watch the Complete Install in the Video
The full installation, screen by screen, is in the video — this page is your written companion for every step and warning.
Jira opens on the server but not on other PCs. What is wrong?
Almost always Windows Defender Firewall on the server — it has no inbound rule for Jira yet. Add an inbound TCP rule for port 8080 on the Domain and Private profiles, then test from a team PC using the server IP address.
Can I change Jira to port 80 so the URL looks clean?
You can pick another port in the installer, but port 80 is often held by other software and the :8080 in the URL harms nothing on a LAN. A cleaner answer for daily use is a DNS name plus a bookmark — keep the port.
How should remote staff reach our self-hosted Jira?
Through a VPN into the office network. Do not publish a self-hosted Jira — especially the unsupported Server edition — directly on the internet with a router port-forward.
This guide is based on the Technical Anshu Jira Server installation video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏