Multi server setup

Hello,

Problem is serius, because I cannot transfer domains!
When trying to test multi server setup, DA displays error:
----------------------------------
192.168.1.2 :
Unable to connect to 192.168.1.2
Unable to connect to secure socket
----------------------------------

and in directadmin/error.log :

----------------------------------
Unable to connect to secure socket: Some I/O error occurred. The OpenSSL error queue may contain more information on the error. If the error queue is empty (i.e. ERR_get_error() returns 0), ret can be used to find out more about the error: If ret == 0, an EOF was observed that violates the protocol. If ret == -1, the underlying BIO reported an I/O error (for socket I/O on Unix systems, consult errno for details).
-----------------------------------

What is the reason, and howto get rid with this problem.
This configuration works great few days ago.



Any idea?

You need an internet routeable ip address not a lan one.

I've tried both - public and private.
The same problem occurs when using public IP.

Are you running DirectAdmin through http or through https? Only https allows secure socket. You may also need to check any firewalls. Always use publicly routable IP#s; the others won't route.

Jeff

Why isn't there a good explanation on how multi server setup works!

What do you need to run multi server?
How it works with IPs etc

Directadmin.com tells nothing about it, only how it works with dns

I have 2 VPS and 2 registred nameservers on de VPS IPadresses
How many Ips do you need etc
Do you need 2 DA license or does DA make a copy on VPS2?

I also get "Unable to connect" when I test connection to VPS2


I'm getting crazy on this

You need 2 copies of directadmin. There are many other ways to do master slave dns without using directadmin multiserver.

scsi said:

You need 2 copies of directadmin. There are many other ways to do master slave dns without using directadmin multiserver.

Click to expand...

So I need a second license?

DirectAdmin multi-user option only works for DNS. It does require a second DirectAdmin license. If you need to set up automatic DNS slaving, but don't want another DirectAdmin license you can search these forums for my Master2Slave DNS Replicator.

Jeff

jlasman said:

DirectAdmin multi-user option only works for DNS. It does require a second DirectAdmin license. If you need to set up automatic DNS slaving, but don't want another DirectAdmin license you can search these forums for my Master2Slave DNS Replicator.

Jeff

Click to expand...

I shall look for "Master2Slave DNS Replicator" on this forum. Thanks for your help!

NuSneller said:

Why isn't there a good explanation on how multi server setup works!

What do you need to run multi server?
How it works with IPs etc

Directadmin.com tells nothing about it, only how it works with dns

I have 2 VPS and 2 registred nameservers on de VPS IPadresses
How many Ips do you need etc
Do you need 2 DA license or does DA make a copy on VPS2?

I also get "Unable to connect" when I test connection to VPS2


I'm getting crazy on this

Click to expand...

+1 unless I'm just not finding one.

Hi I had Working Multiserver setup but now... lets see
/var/log/directadmin/security.log
2011:12:16-10:47:32: Unable to connect to secure socket: Some I/O error occurred. The OpenSSL error queue may contain more information on the error. If the error queue is empty (i.e. ERR_get_error() returns 0), ret can be used to find out more about the error: If ret == 0, an EOF was observed that violates the protocol. If ret == -1, the underlying BIO reported an I/O error (for socket I/O on Unix systems, consult errno for details).

hmm I loooking for solution... but if some guru there

I did

yum update ...

cd /usr/local/directadmin/custombuild
./build update
./build versions
./build update_versions

./build all d

but still the same :-(

Unable to connect to secure socket

I connect to my directadmin admin panel through http.

I have done a tcpdump and saw that directadmin connected to the licensing server through a http rather than a https.

Moving the directadmin panel from http to https is the trick to make it work.