Connecting to www.directadmin.com[66.51.122.131]:443... failed: Connection timed out.

[wookie919]

Hi,

I've just got a trial license I am trying to setup direct admin on my server. I get connection time out during setup. Is the direct admin https server actually down, or could something be wrong with my server setup?

Please help.

Thanks,
wookie919.




Please enter your Client ID : xxxx
Please enter your License ID : xxxxx
Please enter your hostname \(server.domain.com\)
It must be a Fully Qualified Domain Name
Do *not* use a domain you plan on using for the hostname:
eg. don't use domain.com. Use server.domain.com instead.
Do not enter http:// or www

Enter your hostname (FQDN) : xxx.xxxxxxxx.xxx
Client ID: xxxx
License ID: xxxxx
Hostname: ns1.spacemonkey.co.nz
Is this correct? (y,n) : y
Is eth0 your network adaptor with the license IP? (y,n) : y
Is xxx.xxx.xxx.xxx the IP in your license? (y,n) : y

DirectAdmin will now be installed on: fedora 2
Is this correct? (must match license) (y,n) : y
beginning pre-checks, please wait...
--09:41:32-- http://files.directadmin.com/services/fedora_2/files.sh
=> `/usr/local/directadmin/scripts/files.sh'
Resolving files.directadmin.com... 199.237.54.170
Connecting to files.directadmin.com[199.237.54.170]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1,031 [application/x-sh]

100%[=========================================================================================>] 1,031 --.--K/s

09:41:32 (9.83 MB/s) - `/usr/local/directadmin/scripts/files.sh' saved [1,031/1,031]

./setup.sh: line 672: ldconfig: command not found
--09:41:32-- http://www.directadmin.com/named
=> `/etc/init.d/named'
Resolving www.directadmin.com... 66.51.122.131
Connecting to www.directadmin.com[66.51.122.131]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2,324 [text/plain]

100%[=========================================================================================>] 2,324 --.--K/s

09:41:33 (3.19 MB/s) - `/etc/init.d/named' saved [2,324/2,324]

--09:41:34-- https://www.directadmin.com/cgi-bin/daupdate?uid=8708&lid=21968
=> `/usr/local/directadmin/update.tar.gz'
Resolving www.directadmin.com... 66.51.122.131
Connecting to www.directadmin.com[66.51.122.131]:443... failed: Connection timed out.
Retrying.

--09:44:43-- https://www.directadmin.com/cgi-bin/daupdate?uid=8708&lid=21968
(try: 2) => `/usr/local/directadmin/update.tar.gz'
Connecting to www.directadmin.com[66.51.122.131]:443... failed: Connection timed out.
Retrying.

--09:47:54-- https://www.directadmin.com/cgi-bin/daupdate?uid=8708&lid=21968
(try: 3) => `/usr/local/directadmin/update.tar.gz'
Connecting to www.directadmin.com[66.51.122.131]:443... failed: Connection timed out.
Retrying.

--09:51:06-- https://www.directadmin.com/cgi-bin/daupdate?uid=8708&lid=21968
(try: 4) => `/usr/local/directadmin/update.tar.gz'
Connecting to www.directadmin.com[66.51.122.131]:443...

 

[wookie919]

Solved. My iptables setting was wrong.

Thanks all.

 

[robkirwan]

can i ask how you fixed this?

i am having the same problem

 

[floyd]

Evidently his iptables was blocking port 443. That is my guess.

 

[robkirwan]

When i install directadmin and it asks if 192.168.0.8 is my ip -i say no and enter my external ip but when it tries to install i get the same error as above, if i say yes to the ip being 192.168.0.8 it downloads and installs fine,

but i cannot navigate to 192.168.0.8:2222 when it is installed
just to point out if i navigate to 192.168.0.8 it loads the apache welcome page - so apache is working ok

any ideas?

 

[floyd]

The private ip address should not even be on the server at all.

 

[robkirwan]

yeah i have been reading bits all night and i think because the server is connected to a lan it is not working

my plan was to set the server up here and ship it to a colo datacentre, i am going to call isp tomorrow and get an extra ip for the server, i think that should do it

 

[nobaloney]

DirectAdmin requires a public IP#.

Jeff

 

[LionRock]

I have the same problem. I have 2 IP's one external and one local IP. I have a router and I have a port 80 forwarded to machin where I want to install DA. What else do I nead ?

 

[nobaloney]

You need a network interface (i.e., eth0) that answers to the same IP# as the outside world uses to reach the server.

For example, if I can reach your server by using 4.5.6.7, then your server must be listening on 4.5.6.7, not on (for example), 192.168.3.4.

Jeff