New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


call api do not work

Votes:

0

Your Vote:

Up

Down

Has anyone had this problem, please follow the settings and the problem (CORE configured for SSL):

Same network
Call API by HTTP is received at 80 and is directed to 443 and it works:

Another network
Calling API by HTTP is received at 80 but is not directed to 443 and does not work, and when the call is with https nor appears in the logs.

Can someone give a light?

api call https

Created on Oct 26, 2018 1:42:08 PM by  francisgoliveira (0) 1

Last change on Oct 26, 2018 6:22:14 PM by  Stephan Linke [Paessler Support]



4 Replies

Votes:

0

Your Vote:

Up

Down

Why not calling HTTPS directly instead of relying on the redirect?


PRTG Scheduler | PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Created on Oct 26, 2018 6:22:55 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello stephan, because:

"when the call is with https nor appears in the logs"

That not works both.

Only work in my network, the other side is a service OTRS.

Created on Oct 26, 2018 6:27:17 PM by  francisgoliveira (0) 1



Votes:

0

Your Vote:

Up

Down

Ah okay - webinterface not listening on all IPs as per PRTG Administration Tool's Webserver tab?


PRTG Scheduler | PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Created on Oct 26, 2018 6:58:28 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

444/5000 in fact, works on the local network only. Either using http or https.

It does not work at all:

When the kernel is configured for ssl:

- call http - in the log is the call - call https - no log no call

It used to work on 80, but it does not work any more.

My configuration is HTTP by 443 and only 1 ip specified, which is the webserver itself.

What I do not understand, is because it works not local and external.

Created on Oct 26, 2018 7:56:50 PM by  francisgoliveira (0) 1



Please log in or register to enter your reply.


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.