Unable To Connect To DirectAdmin Services On Localhost

FishGuy876

FishGuy876

Verified User
Joined
Dec 17, 2009
Messages
10
Location
Ephrata, PA
Hi,

I am having a strange problem with my new DirectAdmin server. I am running on Debian 6.0.2, although I dont know if the problem is specific to this version or not. Previously, I ran a VPS for a couple of years with DirectAdmin and didnt have too many problems. Thanks to the DA team for making migrations from one server to another very smooth!

It seems I am having troble with localhost, or more specifically, when the box is trying to connect to other services locally within itself. When logging in from the outside world to any service, such as imap or ftp, there are no problems. If I am SSH as root into the server, and I try to connect to any of those services on localhost, it always times out. Even if I use any of the 5 server IP's directly from SSH, it will still time out. I noticed this problem when I was trying to troubleshoot why roundcube wouldn't connect to imap, and noticed it happes on all services too.

I have spent the last couple of days scouring around on these forums for answers, checked the /etc/hosts file for correct localhost and a few other obvious settings, but don't seem to be able to troubleshoot why localhost access to everything is blocked. If anyone has any ideas or suggestions on what to try to troubleshoot why something like 'telnet localhost imap' won't connect, I would be interested in hearing them :)

My etc/hosts file:

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
127.0.1.1 server.jdc.local server

::1 ip6-localhost ip6-loopback
#::1 localhost6.localdomain6 localhost6
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
204.27.58.210 server.andykellett.com

SSH Session:
root@server:~# telnet localhost 143
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection timed out

SSH from a different box:
root@cvgm:~# telnet 204.27.58.210 143
Trying 204.27.58.210...
Connected to 204.27.58.210.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN] Dovecot DA ready.

Please move this post to another forum if it belongs there instead. Thanks!
 
Some additional info on how listed services are currently configured:

root@server:~# netstat -lntp | grep tcp
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 2492/dovecot
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 2492/dovecot
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1004/portmap
tcp 0 0 204.27.58.214:53 0.0.0.0:* LISTEN 3042/named
tcp 0 0 204.27.58.213:53 0.0.0.0:* LISTEN 3042/named
tcp 0 0 204.27.58.212:53 0.0.0.0:* LISTEN 3042/named
tcp 0 0 204.27.58.211:53 0.0.0.0:* LISTEN 3042/named
tcp 0 0 204.27.58.210:53 0.0.0.0:* LISTEN 3042/named
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2804/sshd
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 2306/exim
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 2492/dovecot
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 2492/dovecot
tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 2306/exim
tcp6 0 0 :::2222 :::* LISTEN 2487/directadmin
tcp6 0 0 :::80 :::* LISTEN 2896/httpd
tcp6 0 0 :::21 :::* LISTEN 3057/proftpd: (acce
tcp6 0 0 :::53 :::* LISTEN 3042/named
tcp6 0 0 :::22 :::* LISTEN 2804/sshd
tcp6 0 0 :::25 :::* LISTEN 2306/exim
tcp6 0 0 :::443 :::* LISTEN 2896/httpd
tcp6 0 0 :::8000 :::* LISTEN 2341/icecast2
tcp6 0 0 :::3306 :::* LISTEN 2887/mysqld
tcp6 0 0 :::587 :::* LISTEN 2306/exim
 
IPtables rules are empty:


root@server:~# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

I normally have some IP's blocked as they seem to be brute attacking the box to log in. No change in behaviour, and I have no other firewall installed. This is a plain DA box.
 
imap_listen = *
Click to expand...

Doesn't seem to work on the Dovecot version supplied with DirectAdmin, it is instead listed in the config files as listen = *, and starting the service with that change produces an error (and subsequently fails to restart dovecot).

This was one of the things I tried yesterday, thanks :)
 
I have managed to fix this issue, it would seem lo was broken and wouldnt start. Once it started, everything started working again. Thanks to everyone who sent me messages :)
 
You must log in or register to reply here.
Back
Top