The installer finished, you typed the address, and the browser shows a cold error page. Do not reinstall in a panic — a dead Odoo page has a short list of usual causes, and this guide checks them in the order that fixes real installs.
A fresh Odoo that will not open feels like a disaster, but the system is only three moving parts: the Odoo service, the PostgreSQL database, and port 8069, the door your browser knocks on. If any one of the three is down, the browser shows the same empty result, which is why guessing fails and checking wins. Work through this page top to bottom. Each step takes a minute, each answer tells you where the break is, and the last section covers the one situation where reinstalling really is the right move — a half-finished earlier install haunting the new one.
Press Windows + R, type services.msc and press Enter. Find the Odoo service in the list. Its status should read Running and its startup type Automatic. If it is stopped, right-click and choose Start, then refresh the browser page. If it starts and immediately stops again, the service is crashing on launch — that points downwards in this list, usually at the database or the configuration, not at the browser. Also honest and common: the PC simply restarted and the service is still starting. Give a slow office PC a full two minutes after login before you diagnose anything.
In the same Services list, find the PostgreSQL service that the Odoo installer added. Odoo without its database is a shopkeeper with no godown — the program starts, finds nothing to serve, and gives up. If PostgreSQL is stopped, start it, then restart the Odoo service so it connects fresh. If PostgreSQL refuses to start, note the exact error it shows; a database service that will not start after a forced shutdown or a disk-full event is a data problem, not an Odoo problem, and reinstalling Odoo will not cure it. Check your disk is not completely full — a 100 percent full drive stops databases silently and is embarrassingly common on small office PCs.
Port conflicts produce the rudest version of this bug: another program already owns 8069, so your browser talks to the wrong tenant or to nobody. The installer itself may warn 'the specified port number is not available' — believe it. Usual squatters are a previous Odoo install still running, or another development tool. The fix order matters: first make sure only one Odoo service exists and is running. If some other needed program truly owns the port, change Odoo's port instead — open the odoo.conf file in the installation folder, set http_port to a free port such as 8070, save, and restart the Odoo service. Your address becomes http://localhost:8070. Ugly, but honest and working beats pretty and dead.
Two cheap tests before deeper surgery. First, try a different browser and the exact address http://localhost:8069 — not a bookmark, not a search. Aggressive browser extensions and cached error pages fake this bug regularly. Second, test from the server PC itself, as above — if Odoo opens locally but not from other office PCs, the server is fine and the Windows Firewall is the wall: it needs an inbound rule allowing the Odoo port for your local network. That distinction — dead everywhere versus dead only from other desks — splits this problem in half, so always make the local test first.
Here is the failure behind many forum posts: an earlier Odoo or PostgreSQL install was removed incompletely, and its leftover services and folders confuse the new setup. Symptoms include the port warning on a 'fresh' install and database errors mentioning an old PostgreSQL. The honest cure is unglamorous: uninstall Odoo, check Services for orphaned Odoo or PostgreSQL entries from the old copy, remove the leftover installation folders, restart the PC, and install once more — this time ticking both components and keeping the service option on. Rushing this cleanup is how people install Odoo four times in one afternoon and fix it on the fifth.
Reinstall freely in exactly one situation: a brand-new install with no real data that never worked. You lose nothing but twenty minutes. The moment a real company database exists — customers, invoices, stock — stop reinstalling. A reinstall never fixes a database problem and can bury your data under a fresh empty system. Instead, take a backup copy of the whole installation folder and the database first (our backup guide in this series shows the safe routine), then repair. Graded honestly: nine out of ten 'Odoo is broken' calls end at steps 1 to 3 of this page. The tenth one is data — and data deserves a backup before it deserves a technician.
Watch the Odoo setup video once more and compare each screen with your install — the component ticks and service options shown there are the ones these fixes assume.
▶️ Watch Full VideoAlmost always one of three things: the Odoo Windows service is not running, the PostgreSQL service is not running, or another program already uses port 8069. Open services.msc and check both services first — that alone resolves most fresh-install failures.
The server itself is healthy; the Windows Firewall on the server PC is blocking other machines. Add an inbound firewall rule for the Odoo port (8069 by default) on your local network, and make sure the other PCs use the server's network address, not the word localhost.
Stop reinstalling and look for leftovers: an old Odoo or PostgreSQL service or folder from a previous incomplete removal commonly poisons new installs. Uninstall, remove the orphaned services and folders, restart, and install once with both components ticked. If real data exists, back everything up before touching anything.