What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Error HTTP/1.1 404 Not Found after update Fortigate

Votes:

0

HTTP sensor send error HTTP/1.1 404, any idea what happen?

404 fortigate http prtg

Created on Jun 26, 2021 1:26:03 AM



4 Replies

Votes:

0

Are you able to open the URL in a browser (on the same system as the Probe that runs the sensor)?

Kind regards,
Sasa Ignjatovic, Tech Support Team

Created on Jun 30, 2021 7:39:51 AM by Sasa Ignjatovic [Paessler Support]

Last change on Jun 30, 2021 7:40:03 AM by Sasa Ignjatovic [Paessler Support]



Votes:

0

Hi, yes , the URL open in probe server, port usage from url is: https://name.myfirewall:44435, can be problem a port not standard?

Created on Jul 5, 2021 12:34:24 PM



Votes:

0

The sensor should still work. Did you enter the URL in the sensor including the port (so: https://name.myfirewall:44435)?

Kind regards,
Sasa Ignjatovic, Tech Support Team

Created on Jul 6, 2021 9:08:42 AM by Sasa Ignjatovic [Paessler Support]



Votes:

0

I had the same problem. It seems like after a fortigate update, when acessing the URL "https:///Fortigate-Firewall/" there is a HTTP-Redirection and the PRTG Sensor does not follow the redirection, instead issuing a Error HTTP/1.1 404 Not Found.

The Workaround is to change the URL to "https://Fortigate-Firewall/login" then the sensor is OK again.

Created on Sep 28, 2021 12:36:23 PM




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.