Ombi: Can't get through installation. "We are running on http://*:5000

[anderson115]

Ombi build Version:

V 3.0.4036

Update Branch:

Open Beta

Media Sever:

Plex/Emby

Media Server Version:

Operating System:

Windows 10 64-bit

Ombi Applicable Logs (from /logs/ directory or the Admin page):

(Logs go here. Don't remove the ' tags for showing your logs correctly. Please make sure you remove any personal information from the logs)

Problem Description:

Cannot get past installation. Get a message that we are running on http://*:5000. Tried localhost:5000 and nothing loads.

Reproduction Steps:

Please include any steps to reproduce the issue, this the request that is causing the problem etc.

Clean install.
When running Ombi for the first time I get the following:

Hello, welcome to Ombi
Valid options are:
Ombi 3.0.4036-master
Copyright (C) 2019 Ombi

--host (Default: http://:5000) Set to a semicolon-separated (;) list
of URL prefixes to which the server should respond. For example,
http://localhost:123. Use "" to indicate that the server should
listen for requests on any IP address or hostname using the
specified port and protocol (for example, http://*:5000). The
protocol (http:// or https://) must be included with each URL.
Supported formats vary between servers.

--storage Storage path, where we save the logs and database

--baseurl The base URL for reverse proxy scenarios

--help Display this help screen.

--version Display version information.

We are running on http://*:5000

[tidusjar]

There is nothing wrong here with what provided

[anderson115]

When I access localhost:5000, program doesn't load. Any idea what I"m doing wrong?

[tidusjar]

Nope, did you unblock the zip file before extracting? Right Click > Properties > Unblock

[Berserkir-Wolf]

If you're already at that point, you're doing well to begin with. It's running.
To confirm Ombi is actually listening, you could open a Command Prompt and run:
netstat -ano | findstr 5000
You should see something like the following if it's running:
TCP 0.0.0.0:5000 0.0.0.0:0 LISTENING 19980 TCP 127.0.0.1:53496 127.0.0.1:5000 TIME_WAIT 0 TCP 127.0.0.1:53522 127.0.0.1:5000 TIME_WAIT 0
If you see nothing in response, it's not actually listening - you'll have to go back to the drawing board there.
If you do get something in response, we can continue to the next step - ensuring it's actually being allowed through the firewall.
By default, Windows 10 does not accept connections on port 5000, so of course won't allow inbound connections through the firewall. We can change that with Powershell.
Open PS as administrator, and enter the following to allow port 5000 through the firewall:
New-NetFirewallRule -DisplayName Ombi -Profile Any -Direction Inbound -Action Allow -Description "A service to take content requests." -Protocol TCP -LocalPort 5000 -Enabled True
This will create a firewall exception to allow connections to port 5000 through. The rule will be called Ombi, and have a nice description. Personally, I add a variable to the end for the rule creation for Ombi/Sonarr/Radarr etc to group them all, like so:
-Group "1 - Media Tools"
Once the rule is in place, try opening "http://localhost:5000" again and see if you get a connection. If you do, then the next thing to look into is a reverse proxy setup for it - that way anyone you allow to request content can have a nice URL to access it, rather than having to specify a port for it. It also could allow you to set up a nice path for you, instead of having to remember multiple ports etc. could be URL/ombi, URL/sonarr, URL/radarr etc - rather than URL:5000, URL:8989, URL:7878 etc. Just easier.

[anderson115]

Berserkir-Wolf -- Thanks for the super detailed response. I went through the steps and realized my VirtualBox connection wasn't communicating with my networked drive where I installed Ombi. Re-installed directly on VB and it worked! Thank you for taking the time to help me.