![]() |
#1 |
Junior Member
Join Date: Aug 2009
Posts: 24
![]() |
![]()
In our testbed right now, we have servers for each of the following:
BILLmanager ISPmanager Pro VDSmanager IPmanager DNSmanager (1) DNSmanager (2) On the DNSmanager side, a user is configured with "top" namespace access. When we try to configure the ISPmanager Pro server to connect to either of the DNSmanager servers (using the admin user we have on them), we keep getting the following on the form entry screen in red: "Error: unable_connect " Please offer advice as we see no reason for the ISPmanager Pro server to fail to connect. Last edited by getnetworks; 09-10-2009 at 06:22 AM. Reason: typo |
![]() |
![]() |
![]() |
#3 | |
Junior Member
Join Date: Aug 2009
Posts: 24
![]() |
![]() Quote:
For what exactly is the IP Address field? The IP Address of what? There are no docs on this topic at all. The DNSmanager docs are mostly comprised of VDSmanager docs. |
|
![]() |
![]() |
![]() |
#4 |
Junior Member
Join Date: Aug 2009
Posts: 24
![]() |
![]()
Also, where exactly in ISPmanager do you set up the connection with DNSmanager? there doesn't seem to be a 'Remote DNS' section.
|
![]() |
![]() |
![]() |
#6 |
Junior Member
Join Date: Aug 2009
Posts: 24
![]() |
![]()
It doesn't work. When we try to add either of our DNSmanager servers, we just get an error:
"Error: Unable to connect remote service with giving parameters" We have tried using both the admin user and a customer user for the username/password fields on the form. |
![]() |
![]() |
![]() |
#8 | |
Junior Member
Join Date: Aug 2009
Posts: 24
![]() |
![]() Quote:
The DNSmanager log shows nothing during the attempt. The ISPmanager log shows the following (we've masked our IPs): --- Sep 11 00:08:21 INFO Request [Y.Y.Y.Y][root] 'addr=X.X.X.X&stype=dnsmgr&user=admin&passwd=*&fun c=domain.slave.edit&elid=&sok=ok' Sep 11 00:08:21 ERROR Exception 9: Unable to connect remote service with giving parameters --- We confirmed the ISPmanager server can talk to the DNSmanager server over port 443: --- telnet X.X.X.X 443 Trying X.X.X.X... Connected to X.X.X.X. Escape character is '^]'. HEAD / HTTP/1.1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> ... etc. --- Last edited by getnetworks; 09-11-2009 at 07:19 AM. Reason: more info |
|
![]() |
![]() |
![]() |
#9 | |
ISPsystem team
Join Date: May 2008
Location: ISPsystem
Posts: 588
![]() |
![]() Quote:
https://dnsmanager/manager/dnsmgr must be work in web-browser, but you work without SSL over HTTP (not HTTPS) and for this reason does not work |
|
![]() |
![]() |
![]() |
#10 | |
Junior Member
Join Date: Aug 2009
Posts: 24
![]() |
![]() Quote:
--- telnet X.X.X.X 443 Trying X.X.X.X... Connected to X.X.X.X. Escape character is '^]'. HEAD / HTTP/1.1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>400 Bad Request</title> </head><body> <h1>Bad Request</h1> <p>Your browser sent a request that this server could not understand.<br /> Reason: You're speaking plain HTTP to an SSL-enabled server port.<br /> Instead use the HTTPS scheme to access this URL, please.<br /> <blockquote>Hint: <a href="https://ourmaskedhost.com/"><b>https://ourmaskedhost.com/</b></a></blockquote></p> <hr> <address>Apache/2.2.3 (Red Hat) Server at ourmaskedhost.com Port 443</address> </body></html> Connection closed by foreign host. --- As you should clearly see, SSL on port 443 is active. If it wasn't, we would have received an error as follows: "Could not open a connection to host on port 443 : Connect failed". Please learn about this topic before making incorrect statements. And as we also clearly stated, we are *only* using SSL via the web browser, i.e., https://ourmaskedhost.com/manager/dnsmgr. The problem has nothing to do with SSL. Last edited by getnetworks; 09-11-2009 at 10:37 AM. Reason: remove url |
|
![]() |
![]() |
![]() |
Thread Tools | |
|
|