Fresh install - admin login problem

A

Artis

Verified User
Joined
Jun 24, 2012
Messages
36
Location
Zagreb - Croatia
First hi to all,

I have fresh CentOS 6 (x86) and directadmin on it.

After installation of DA, I can not load page for login.

Apache is runing and you can see it on 88.198.86.208, but when I try to login to admin page :2222 the page is not loading.

I try to disable firewall
HTML: 
[root@.... bin]# service iptables stop
iptables: Flushing firewall rules:                         [  OK  ]
iptables: Setting chains to policy ACCEPT: mangle filter na[  OK  ]
iptables: Unloading modules:                               [  OK  ]

Then I try to see errors
HTML: 
[root@..... bin]# tail /var/log/directadmin/error.log
2012:10:17-02:56:57: secure_access_group=access did not exist (9999). Creating it and adding defaults.

Any suggestions about this ?


Best regards
 
As you can see, DirectAdmin doesn't use apache; it's got it's own port 2222 web interface. Can you see the login screen? Can you see the login screen on any other DirectAdmin server?

The problem could be an issue with port 2222 being blocked by your local provider. l Check the DirectAdmin Knowledgebase. Also check this knowledgebase article for running DirectAdmin on port 80 using Apache.

Jeff
 
Maybe you have active SELinux or some block on port 2222 (should be hw firewall aswell).

Also, i did notice that from your netstat, your DA is listening ONLY in IPv6 , not IPv4, i suppose that's the problem

Regards
 
I try to do everything what is in Knowledgebase.

After all, i decide to do clean install directadmin for CentOS 5.xx (x86)

Thanks for helping, I wish that CentOS 5.xx installation will be ok.

I will update this thread after DA change my license to OS version 5.xx (if i will solve my problem)

Best regards
 
Definitly not a good reason to step back. CentOS 6 is pretty compatible and is the latest stable version, definitly the suggester version to use...

Regards
 
Ok, now I have clean install CentOS 5.8 (x86)

From Knowledgebase (http://help.directadmin.com/item.php?id=75) i did:

1.
HTML: 
/sbin/service iptables stop
 /sbin/chkconfig iptables off

Directadmin not working on port 2222

2.
HTML: 
[root@..... ~]# tail /var/log/directadmin/error.log
2012:10:17-09:33:54: secure_access_group=access did not exist (9999). Creating it and adding defaults.

3. directadmin.conf file, I have venet0:0 (it's VPS)
HTML: 
tmpdir=../../../home/tmp
max_username_length=10
login_history=10
log_rotate_size=5
unified_ftp_password_file=1
secure_access_group=access
check_subdomain_owner=1
brute_force_log_scanner=1
ethernet_dev=venet0:0
quota_partition=/
frontpage_on=0
apache_ver=2.0
dovecot=1

5. My ip is not on blacklist

6. Debug directadmin
HTML: 
[root@..... directadmin]# ./directadmin b200
Debug mode. Level 200

DirectAdmin 1.41.1
Accepting Connections on port 2222

After 20min I'm still waiting for something ... I stop debug mode after 1h

After all only what I did not try is this http://help.directadmin.com/item.php?id=84 (I will do it tonight)

Now I'm waiting for my server provider to confirm that firewall is not blocking port 2222

After this from knowledgebase can anyone have any suggestions about this problem ?
 
scsi said:
You definitely should not go back to centos 5. That would be the stupidest decision ever.

Read this guide:

http://help.directadmin.com/item.php?id=75

Also if it comes down to it change the port that directadmin runs on to something else.
Click to expand...


Thanks for suggestion, and I must say that I agree with you for CentOS, but now I'm at 5.8 and still I have the problem. I was thinking that IPv6 was making problems (because i have problems with disabling it).

I will try to solve problem on CentOS 5.8 and after I solve the problem I will do clean install of centos 6.3.

I try to solve problem with that link that you give to me (see my last post)
 
I would say they are definitely blocking port 2222 then. No reason to keep debug open an hour. If you start debug and try to connect and it shows nothing then that means the connection is blocked.
 
My VPS provider answered me that is no firewall installed on the nod.

Now I have no clue for solving this problem.

Help ? :)

EDIT:
I try to change port for directadmin (i change it to 222 and restart directadmin service) but i can not connect to login page.
 
@scsi, I don't think DirectAdmin is responsible for disabling SELinux.

@Artis, shell into your server and read up on how to disable SELinux somewhere, and if it's running, disable it.

If it's a VPS, then ask your VPS vendor.

Jeff
 
nobaloney said:
@scsi, I don't think DirectAdmin is responsible for disabling SELinux.

@Artis, shell into your server and read up on how to disable SELinux somewhere, and if it's running, disable it.

If it's a VPS, then ask your VPS vendor.

Jeff
Click to expand...

Dear Jeff,

SeLLeRoNe already ask me to disable SELinux, what i did with command "setenforce 0" and I have no result.
 
Artis said:
SeLLeRoNe already ask me to disable SELinux, what i did with command "setenforce 0" and I have no result.
Click to expand...
Once you turn off SELinux (since I don't run it I'm not sure if that's all you need to do or not) you then need to restart the server for it to reboot without SELinux running.

None of us knows with certainty the problem with your server. I don't believe you're going to get help without someone logging into your server to figure it out. You can contact DirectAdmin Support or you can hire me or someone else to log into your system. Should you be interested in hiring me you should contact me by email at the address shown below in my siglines, for fastest response.

Jeff
 
You must log in or register to reply here.
Back
Top