DA not allowing me to login
- Thread starter TheBear
- Start date
toml
Verified User
Try looking at the log files in /var/log/directadmin they might give you a clue. It could be a session problem.
Hello,
Thanks for the suggestion. I won't be able to do that until tonight when I get home (no ssh access from here).
This is very scary to all of a sudden be locked out from all accounts (I have 3-4 logins from admin, reseller and end user levels - all are locked out).
I have so far tested from 2 different Macintoshs running Safari and FireFox and 1 windows machine with both IE and firefox. There are machines where I have accessed the server before.
Thanks
Thanks for the suggestion. I won't be able to do that until tonight when I get home (no ssh access from here).
This is very scary to all of a sudden be locked out from all accounts (I have 3-4 logins from admin, reseller and end user levels - all are locked out).
toml said:
I have so far tested from 2 different Macintoshs running Safari and FireFox and 1 windows machine with both IE and firefox. There are machines where I have accessed the server before.
Thanks
Right. /var/log/directadmin/error.log gives me:
And yes, like TheBear, I have also tried multiple logins, multiple browsers, and multiple PC's (having multiple IP's). So I'm pretty sure it's not a client-side thing.
and when I edit /usr/local/directadmin/conf/directadmin.conf to set SSL=0 it gives me:
And yes, like TheBear, I have also tried multiple logins, multiple browsers, and multiple PC's (having multiple IP's). So I'm pretty sure it's not a client-side thing.
More stuff I've tried:
I read the latest update log and noticed it involved some session-related stuff. Since the latest update.tar.gz was dated oct 15th (before the new version was released) I thought I'd give the manual update (as in the knowledge base) a try, but to no avail. I also tried manually creating the new session dir and chmod/chown'ing it according to the instructions in the version history, and also checked directadmin.conf to see if the session_dir directive was set (it wasn't, and should hence default to the new session location).
I read the latest update log and noticed it involved some session-related stuff. Since the latest update.tar.gz was dated oct 15th (before the new version was released) I thought I'd give the manual update (as in the knowledge base) a try, but to no avail. I also tried manually creating the new session dir and chmod/chown'ing it according to the instructions in the version history, and also checked directadmin.conf to see if the session_dir directive was set (it wasn't, and should hence default to the new session location).
nobaloney
NoBaloney Internet Svcs - In Memoriam †
roel, have you tried contacting DirectAdmin support?
These forums are not the best way to reach them.
Jeff
These forums are not the best way to reach them.
Jeff
Yeah, I have.
However, I may have tracked down the problem: seems the backup script filled up the drive. No more space = no more sessions. Pretty obvious, now that I think about it.
TheBear: Check if this is the same problem you have (use the 'df' command to check free disk space). If it is, the easiest way to fix this is probably to delete some old backups, in /home/backup
Good luck!
However, I may have tracked down the problem: seems the backup script filled up the drive. No more space = no more sessions. Pretty obvious, now that I think about it.
TheBear: Check if this is the same problem you have (use the 'df' command to check free disk space). If it is, the easiest way to fix this is probably to delete some old backups, in /home/backup
Good luck!
Last edited:
nobaloney
NoBaloney Internet Svcs - In Memoriam †
That'll do it every time.
Jeff
Jeff