• Hello,

    I’m hoping someone can help me with this issue. The client has a GoDaddy account with lots of files and folders… pretty chaotic. They have a primary domain that points to the root and some other domains pointing to sub-directories.

    They asked me to create a WordPress landing page and make it live. So I created a sub-directory in the root where I placed all the WordPress files and pointed one of their secondary domains to that folder. For the sake of this example, I named the sub-directory “subdir”. In the WP general settings I added the WordPress Address and Site URL.

    WordPress Address: https://www.example.com/subdir
    Site URL: https://www.newexample.com (this is the new landing page domain)

    The page is loading and works great. Now, the problem is that when I try to add a new page, I get a 500 internal server error. The browser is going to https://www.newexample.com/newpage to try to find the page. When I enter https://www.example.com/subdir/newpage, the page loads.

    Can someone please suggest a fix for this or point me in the right direction?

    Thanks!
    Mariana

    • This topic was modified 7 years, 1 month ago by RataCross.
Viewing 1 replies (of 1 total)
  • Moderator t-p

    (@t-p)

    Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the default theme for your version of WordPress to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

    If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.

    If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

Viewing 1 replies (of 1 total)
  • The topic ‘New Pages throwing 500 error’ is closed to new replies.