Latest update killed my admin credentials

Ch3vr0n

Verified User
Joined
Aug 24, 2014
Messages
88
Just updated from 1.61 to the latest release (not RC), it's a bit of a jump but i don't always need admin access. Shortly after i got logged out, and my admin credentials no longer work. What also happens since then is that i simply can't access the admin panel at all. Firefox fails to setup a secure connection. Chrome gives ERR_HTTP2_PROTOCOL_ERROR when that happens.

So the problem is now 2-fold. How do i restore my admin DA access (i can log in just fine on SSH using those same credentials) and how to i fix that protocol error.
 
More problems. This apparently has killed the httpd service. Trying to restart the service yields error: /usr/bin/systemctl start httpd.service 2>&1
 
Just updated from 1.61 to the latest release (not RC), it's a bit of a jump but i don't always need admin access. Shortly after i got logged out, and my admin credentials no longer work. What also happens since then is that i simply can't access the admin panel at all. Firefox fails to setup a secure connection. Chrome gives ERR_HTTP2_PROTOCOL_ERROR when that happens.

So the problem is now 2-fold. How do i restore my admin DA access (i can log in just fine on SSH using those same credentials) and how to i fix that protocol error.
No ( da credential lost here) we had that to ,o nly waiting longer and try other browser da came back at our box, more had this problems, but after a while DA did came back


Yup i did got that before update to 16... now updating i must do every toem i wait ne week , in the hope that thes kind or erros are solved with the newer updates.

OS version do uou have?

Strange thing hard to find errors, browser time out but you have to look in every log in server sometimes you see related to something in DA panel of custombuild update a script form those, but also no error in logs still that kind of timeout and need to refresh. ( and or use other browser while edge for example take longer time to come back on that server. ) opcache is on

If closing browser , ( delete browser cache is not enough) so new session then i goes ok, some time da itself takes time but came back then
 
Last edited:
Well it was something with the SSL that was spotty. One moment the login would load, the next one it wouldn't but primarily firefox wouldn't work. So when i noticed FF didn't work, i clicked the password reset link in chrome. Took a few tries but eventually i was able to reset the PW, login on chrome, and set the pw back to what it was.

Then the httpd service, i don't know what it was but an entire rebuild of apache just now, restored the service functionality and brought the site back up. So i guess the problem is solved (for now)
 
Read about some help with httpd down here in forum BUG en then in ssh the comman directadmin p or so

 
Well it was something with the SSL that was spotty. One moment the login would load, the next one it wouldn't but primarily firefox wouldn't work. So when i noticed FF didn't work,)
Yup that is still sometimes with the newest version at box i am behind now, but it can work hours without a problem same things script sites and workflow, then out of the blue that problem.

I had this for example with trying to load a log file only 3-5 lines in DA evo . Then had to close restart EDge ( setting is session cleanup at close so the most easy way) but if doing the fast in the error problem it don't work, other browser yup but some time to
 
Back
Top