Dear Team,
please note that we are facing the below issue when we are testing a new module in our ERP for calling the api .
our HSNM Manager portal working fine from any where , but the api call working only on local network ???
below example
----
call from outside the network using base url
https:// ZZZ.dyndns.com/api/v1/
result :
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /api/v1/testapi/apikey=XXX/sparam=XXX was not found on this server.</p>
</body></html>
------
call from same local network using base url 172.16.16.2/api/v1/
result :
"TestAPI function ok (2019-03-23 00:27:11)"
is this is related to some SSl certificate ,or Apache update Version or its related to some configuration in my network ?please advice
we are using V 6.0.171.
and for some unknown reason we dont see any ability to upgrade we just see ability to downgrade to V 6.0.170
and apatchi update always there showing the button to "upgrade now" even we tried several time to upgrade it
thank you
API CALL // connect from outside the local network error//
General questions and topics about hsnm
-
Magenta
- Posts: 50
- Joined: 12 Mar 2019, 05:48
-
HSNMSupport
- Posts: 1553
- Joined: 26 Jul 2016, 09:16
Hi Magenta
If the API call works on local network it must works also calling it from outside. If it doesn't work, mean that there are some misconfiguration on your network.
Please check to have correctly configured:
1) the "Domain name" on "System Settings"
2) The A records on your DNS settings or on your DynDNS
3) Port forwarding or firewall rules on your firewall.
Also I advise you to upgrade your HSNM to the latest version and then do the Apache upgrade again.
Best regards
If the API call works on local network it must works also calling it from outside. If it doesn't work, mean that there are some misconfiguration on your network.
Please check to have correctly configured:
1) the "Domain name" on "System Settings"
2) The A records on your DNS settings or on your DynDNS
3) Port forwarding or firewall rules on your firewall.
Also I advise you to upgrade your HSNM to the latest version and then do the Apache upgrade again.
Best regards
-
Magenta
- Posts: 50
- Joined: 12 Mar 2019, 05:48
as i mentioned earlier,
for some unknown reason we dont see any ability to upgrade we just see ability to downgrade to V 6.0.170
Pelase let me know how we can solve that
appreciate if somebody can remotely access into our system and see the problems .
for some unknown reason we dont see any ability to upgrade we just see ability to downgrade to V 6.0.170
Pelase let me know how we can solve that
appreciate if somebody can remotely access into our system and see the problems .
-
HSNMSupport
- Posts: 1553
- Joined: 26 Jul 2016, 09:16
Hi Magenta,
can you send us an email to support@hsnetworkmanager.com providing credentials and URL in order to access to your HSNM and check?
Thank you in advance,
Best Regards.
can you send us an email to support@hsnetworkmanager.com providing credentials and URL in order to access to your HSNM and check?
Thank you in advance,
Best Regards.
-
HSNMSupport
- Posts: 1553
- Joined: 26 Jul 2016, 09:16
Thank you to provide us the access to your HSNM; we found and solve the problem: it was caused by our license server. Now you can upgrade your HSNM to the latest 6.1.55 version.
Please upgrade it and then try again to use the API
Best regards
Please upgrade it and then try again to use the API
Best regards
-
Magenta
- Posts: 50
- Joined: 12 Mar 2019, 05:48
what is the port used by HSNM to access the API CALLS ??
-
HSNMSupport
- Posts: 1553
- Joined: 26 Jul 2016, 09:16
Hi
The port used is port 80.
Connecting to your HSNM I see that on "Domain name" inside HSNM "System Settings" you leave yourdomain.com, instead you have to set a FQDN used to reach your HSNM from Internet.
Probably this is the issue because you were not able to call the API from Internet.
Best regards
The port used is port 80.
Connecting to your HSNM I see that on "Domain name" inside HSNM "System Settings" you leave yourdomain.com, instead you have to set a FQDN used to reach your HSNM from Internet.
Probably this is the issue because you were not able to call the API from Internet.
Best regards
-
Magenta
- Posts: 50
- Joined: 12 Mar 2019, 05:48
thank you very much
its working fine now
its working fine now
-
HSNMSupport
- Posts: 1553
- Joined: 26 Jul 2016, 09:16
Hi Magenta
It is working because we have set, on "Domain name", the FQDN that you sent us by e-mail.
Anyway good to hear that it is working now.
Best regards
It is working because we have set, on "Domain name", the FQDN that you sent us by e-mail.
Anyway good to hear that it is working now.
Best regards
Rate this topic
Who is online
Users browsing this forum: No registered users and 27 guests
It is currently 04 Dec 2024, 19:58