Cannot log in to Usermin

Submitted by clwheatley on Mon, 07/05/2010 - 09:30

Users are currently unable to log in to Usermin. The log in interface fails to load when going to webmail.mydomain or https://mydomain:20000 - it just times out.

I've looked through logs and cannot pinpoint where it is failing, though there are a couple of cryptic errors in the /var/webmin/miniserv.error, but with no time stamp

Time server different with local time is too large : 40362 days cat: /etc/redhat-release: No such file or directory

Restarting the service does not change anything. /var/usermin/miniserv.error outputs:

[05/Jul/2010:07:14:39 -0700] miniserv.pl started [05/Jul/2010:07:14:39 -0700] PAM authentication enabled

Thanks,

Chris

Status: 
Closed (fixed)

Comments

Submitted by andreychek on Mon, 07/05/2010 - 09:55

So you can log into Virtualmin at mydomain.tld:10000, but you can't access Usermin at mydomain.tld:20000?

If you log in as root over SSH, and run this command, what output do you get:

netstat -an | grep :20000

Also, has Usermin previously worked on this particular server?

Submitted by clwheatley on Mon, 07/05/2010 - 10:08

Yes, I can log in to Virtualmin just fine, Usermin is the issue.

netstat -an | grep :20000 outputs:

tcp 0 0 0.0.0.0:20000 0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:20000 0.0.0.0:*

Submitted by clwheatley on Tue, 07/06/2010 - 14:01

I also forgot to mention, Usermin has worked fine up until last week.

Submitted by JamieCameron on Tue, 07/06/2010 - 14:16

Could you give us an example Usermin URL that I can try connecting to? I'd like to see exactly what goes wrong..

Submitted by clwheatley on Tue, 07/06/2010 - 14:23

webmail.calvaryweb.com

Submitted by andreychek on Tue, 07/06/2010 - 14:32

Yeah, I can't connect to Usermin either.

Being as your system is listening on port 20000, you may be seeing some sort of firewall issue.

Is your server behind a NAT firewall of some sort? Or are you otherwise running firewall software on your server?

Submitted by JamieCameron on Tue, 07/06/2010 - 14:33

I see the issue - port 20000 is blocked on your system. Is that port perhaps blocked by the firewall on your system, or the firewall on some other gateway?

Submitted by clwheatley on Tue, 07/06/2010 - 15:08

strange that it would be. All that has changed were system updates. I'll double check to make sure something isn't blocking

Submitted by clwheatley on Thu, 07/08/2010 - 18:01

Ok, so there was an old rule for our old server that was hacked which happened to be forwarding port 20000 to BOTH servers. The rule was removed to lock down access to the server which was rebuilt and put back in place as a backup, but it took down access for this server as well. All is well.