John Dittmar

I looked at the page’s requested content and it was trying to load in a javascript asset from https://localhost:3131 which is rather odd. The main site does bring up so it does look like the home and site URL is set properly which is what I believed the issue might be. That being said it doesn’t rule out that the home and site URL is https://localhost:3131 because your domain name might be hard coded inside the theme.\

You change check your site’s home and site URL via phpMyAdmin (if available) by checking the wp_options table of the database.

If it looks good with the domain name, most likely the issue lies is plugins or the theme. You can do this manually by checking the file system of the install under wp-content/themes to get the available themes and updating them via phpMyAdmin from wp_options:

https://www.inmotionhosting.com/support/edu/wordpress/change-theme-in-db

You may also want to try to disable your site’s plugins as well if that fails too.

https://perishablepress.com/quickly-disable-or-enable-all-wordpress-plugins-via-the-database/

Cheers!

Hello there David!

Majority of the time if an issue is regarding FTP this would be something host-related moreso than WordPress. Hearing that the file permissions are set to 000 most likely means that the host may of zero’d out the file permissions for one reason or another. This makes changing the permissions impossible as the file permissions don’t allow you to make permissions changes (sorta a catch-22 situation). I can’t say for sure though but your best bet here is to reach out to them for more insight.

Cheers!

It could be a number of things without seeing the logs, possibly plugins or themes. The .htaccess that Tim provided is a file in the root of the WordPress install. It’s notorious to cause 500 errors for WordPress installs. You may try to look at this file by asking your host on how to gain access to your site’s files; majority of the time it is via FTP.

I would also try to reach out to your hosting provider for your site’s error log. Once we can see the error in the error log it makes troubleshooting much easier to identify the issue.

Are you able to access your server’s/site’s apache error log? Majority of the time 500 errors are reported there with some information to go off of.

Cheers!