Ad Widget

**WillG** · 18-05-2021, 14:42

It doesn't matter, I get the same result either way. Yes you have the recommended endpoint, I had omitted the "zabbix" part or the url in an attempt to connect.

**Atsushi** · 19-05-2021, 03:23

Are you specifying the same host name or IP address as when accessing the web frontend?
If the URL to access is different, it is possible that another directory will be accessed and a 404 error will occur depending on the settings such as the virtual host.

**WillG** · 20-05-2021, 13:07

I have tried localhost, 127.0.0.1 as well as using the static IP from both the server and the agent. All attempts have resulted in the same response.

**WillG** · 20-05-2021, 13:15

So I have discovered that the following API call works from the terminal on localhost. When I submit this call I receive a json response with an authentication token as expected. Note that I have removed the '/zabbix/' part of the URL path and have changed the Content-Type to application/json.

Code:

curl -H "Content-Type: application/json" -X POST http://localhost/api_jsonrpc.php -d'
{
"jsonrpc": "2.0",
"method": "user.login",
"params": {
"user": "Admin",
"password": "zabbix"},
"id": 1
}'

The API calls are still answered by 404 from any other machine on the network.

**Atsushi** · 21-05-2021, 02:03

Are you sure that you can access Zabbix's Web front end using a web browser with the URL "http://localhost/"?

**WillG** · 21-05-2021, 12:55

Yes, that's only way of accessing the Zabbix front end. So this issue is resolved as the only need for us is to access Zabbix from the zabbix server itself. Thanks.