Can;t get into the dashboard

Perhaps a plugin is interfering?

You’ll need either FTP or cPanel to gain access to your file directories on your server. Navigate to the “wp-content” folder.

Once there, look for the “plugins” folder. RENAME this folder to something like “plugins-testing”. Now, when you log into your admin panel, all plugins will be automatically disabled.

Check to see if you are able to login successfully.

If so, go back and RENAME your “plugins-testing” folder back to it’s original “plugins” name.

You can reactivate plugins (one at a time) checking to see which one causes the issue.

Thanks Josh, I got into the cPanel and here’s something quite odd, the url is not showing in the public_html folder. Spooky, it’s definitely not expired. What do you think that could be?

the url is not showing in the public_html folder

I’m not sure I understand. I don’t think it’s the url that shows in the “public_html” folder; but rather an account user name or something. Or, perhaps it’s up to the hosting provider on how they structure the root files?

Do you see a folder marked “wp-content” anywhere?

I do see that, but the site should show along with about 10-other sites I have under the primary domain’s public_html which will each contain their own specific wp-content folder, which to be honest is where I’d assumed you were sending me ??

But now you’re aware I’ve got quite a few sites, let me ask:

If I were to carry out your great and very welcome instructions in the wp-content folder you’ve flagged up, will it disable all the plugins on all my domains?

I’m aware that the site should show up in the public_html folder, no matter what it’s status, so I’m still wondering about that?

the URL you gave got wrong address, is this typo?!!
https://myneshealth.com/wp-login.php?redirect_to=http%3A%2F%2Fwww.myneshealth.com%2Fwp-admin%2F&reauth=1

does take to a log in page, but wp-admin is 404. check or clean your htaccess file might help

Thanks for your input shamratdewan, but I’ve been to the login page you’ve given a link to, and it just takes me back to the typo url with the flagged error, because of this .comwww.:

https://myneshealth.comww./wp-login.blah-di-blah

And the cPanel is behaving weirdly in not showing the url under public_html along with all my other domains. Any thoughts on that, in relation to the problem?

And the cPanel is behaving weirdly in not showing the url under public_html along with all my other domains.

I’d contact your host. That is an area they should be able to help.

If I were to carry out your great and very welcome instructions in the wp-content folder you’ve flagged up, will it disable all the plugins on all my domains?

It shouldn’t. But I’m not sure what’s going on with your other sites not appearing properly. I’d start with a call to the hosting provider. Once the sites are back to being listed properly; then carry out the instructions above.

Thanks Josh I’m on with the host now, as it goes. Just to clarify all my other sites are fine which is why I don’t want to disable their plugins as well. I’m sure you understand.

So to rectify the original problem, and not disable the other plugins, can I just follow the same instructions in the relevant url’s wp-content – plugins -instead?

So to rectify the original problem, and not disable the other plugins, can I just follow the same instructions in the relevant url’s wp-content – plugins -instead?

Precisely ??

What happens when you rename the associated sites “plugins” directory; you are blocking the path WordPress will follow the next time you log into the admin panel and go to the “Plugins” admin page. Since the file path to the plugins directory is “broken”; all plugins will be disabled. They will still be there; but they just won’t be available in your admin panel. Once you rename that folder back to “plugins”; you’ll be able to use them as normal (activate, deactivate, etc.).

Thanks guys, just to let you know HG fixed both aspects, the conversation didn’t fully copy and paste, so although I asked I can’t remember what he said the problem was, although it was to do with the url being captured, somehow under the error name, no ideas how that happened nut again thanks for your input.

Great!
Glad you got it working properly.
Congrats ??