BigFix API HTTP 404 Error

Customizations
1

I’m attempting to test credentials to the API for a script, but am unable to get an authentication prompt. Instead, I get an error message and am unable to load the API page at all (per this article’s direction). My process is this:

  1. Go to Tools -> Launch Web Reports – from the BF Console.

  2. Modify the URL to https://SERVER-FQDN:52311/api

  3. When I navigate to that page, I get an error stating “This site can’t be reached”. Web Reports loads up fine, and I can authenticate to that, no problem.

What am I missing? Is it possible that the API tools are disabled? If so, how do I enable it?

Thanks for your assistance!

-Shane

2

use
https://SERVER-FQDN:52311/api/help
or
https://SERVER-FQDN:52311/api/login
-jgo

2 Likes
3

Thanks for the quick reply. I just tried that in both of those URL’s in IE and Firefox and am getting “The connection has timed out” and “This page can’t be displayed”.

4

You should be getting back an authentication prompt if that is your BigFix server.

Is it possible that you are using a port other than 52311 for your implementation?

-jgo

2 Likes
5

I’m not 100% sure on that. I inherited this environment. Is there a way I can look up which port might be in use for the API?

6

If you have the agent installed locally on your endpoint I would find the masthead and check.

Check in the file: C:\Program Files (x86)\BigFix Enterprise\BES Client\ActionSite.afxm

and look for the value = X-Fixlet-Site-Gather-URL

-Jgo

1 Like
7

I just checked that on this endpoint and it is, indeed, port 52311. The gather, report, registration URL’s are all port 52311.

8

can you telnet to the port 52311?

from a command prompt where you have telnet installed

telnet servernameORserverIP 52311

you should see a blinking cursor.

-jgo

1 Like
9

Do you see a screen like this?
image

1 Like
10

I can telnet to that port, yes – just a blinking cursor.

I have seen that message once or twice when first loading up the page (but it doesn’t show every time). I always click to continue to the website. After opening up a new IE window, I just got the message again. Once I clicked to continue, that’s when I got the “webpage cannot be found” error.

11

To be clear, are your Web Reports and Root Servers on different hosts?

You can only use REST API (on port 52311) against your Root Server, not a standalone web reports (as far as I’ve been able to tell). You can use SOAP API against the Web Reports server, on whichever port Web Reports is listening on (usually https 443).

I don’t think the docs are very clear on this.

12

There may be better guides, and definitely a better reference, at https://developer.bigfix.com/ . Check the “REST API” and “Other APIs” links at the top.

1 Like
13

@smillin - If you can telnet over 52311 to the BigFix server then one of the following URLS should offer an authentication mechanism.

https://SERVER-FQDN:52311/api/help

or

https://SERVER-FQDN:52311/api/login

There is a slight possibility that because of a self signed certificate and a local security setting you may not be able to load the site, but even then I don’t think a 404 error would be displayed. Something is not right.

Are you a master operator?
Do you have access to the Server?
You may want to log this in a PMR.

1 Like