discuss.answer
That is an issue with cURL being used to check if the core is accessible or not. Error 6 means that it couldn't resolve the host. It may be looking for "localhost" when it needs to be looking for an IP address. Or vice verse.
Try going into the database and in the dashboard_widget_placement table delete the row for widget 5. You should probably check the dashboard_widgets table to make sure the w_configcheck widget is #5. I'm not sure this will solve your problem, but not having the widget in the dashboard at all may get you into the Manager.
Have you tried accessing a Manager action directly, bypassing the Dashboard? Something like manager/?a=resource/update&id=1
-
- 8 Posts
Hi sottwell, thx! The widget definitely was the problem, or, should I say the cause that I can't login anymore?
Calling a specific url like your suggested 'manager/?a=resource/update&id=1' worked. I deleted the row of widget 5 in 'dashboard_widget_placement' and now I can open the homepage of the manager.
Thank you very much!