Lost access to Wordpress
-
I usually log into Wordpress with my username and Cloudron password, but it suddently stopped working. My site is still up, but I can't login or reset my password. I tried resetting my Cloudron password and logging in again but that didn't work. I haven't made any changes to WP recently.
-
I have not checked the source of the app just now, but as far as I remember it auto configures ldap access on restart of the app, so if the ldap somehow got misconfigured a restart of the app should fix it.
-
@fbartels I did try rebooting it, no dice. I ended up making another user to get in via qp cli in the meantime.
-
Now my entire site is down
I was in the theme customizer and it just died.
-
@ianhyzy is there anything in the app logs and is the server otherwise ok?
-
@nebulon everything else on the server is fine, nothing weird in the app log that I can see (it seems like an internal WP error - likely a plugin?) I don't seem to be able to connect with SFTP to try removing plugins/themes.
-
@ianhyzy Weird, tried logging in one more time and it worked. I just disabled a plugin that I thin hasn't been updated in a few months.
-
@ianhyzy Still can't login with my Cloudron account, though. TRying both email and username, and it keeps telling me the password is wrong
-
@ianhyzy is there any hint in the wordpress logs and do you see related login attempts in the eventlog in your Cloudron?
-
@nebulon i used another account to turn back on Jetpack/WordPress.org login and was able to get back in, I don't recall turning it off - does that interfere with cloudrons LDAP sync? That might have been it
-
@ianhyzy I have the same issue, just started today. I would like to know if there is a solution.
-
@schnyd I was able to reset the password by accessing the DB through command line. There are several walk throughs that can show you how.
-
@schnyd Any idea how this happened yet?
-
@schnyd did you also have Jetpack plugin installed in your WP instance?
-
@girish I may have been, I removed a bunch of plugins which may have been when the issue started.