• Hi there,

    We’re in the process of moving our blog from a sub-domain to the main domain directory. We’re not able to host a WordPress blog with our main domain servers (for reason beyond the scope of this post) so we hosted it elsewhere and pointed the sub-domain at it.

    We’ve now made the necessary changes to point our main domain at the blog although it is still hosted with another provider. I can visit the blog from the main domain (www.cruisenation.com/blog as well as blog.cruisenation.com) and all of the posts and files (css, js etc) work when I replace the sub-domain address with the main domain address.

    Now when I change the WordPress settings from blog.cruisenation.com to cruisenation.com/blog, the home page of the blog works, but all of the posts appear as a 500 Internal Server error, and some of the images don’t work correctly (but some do…).

    I’m not particularly skilled with hosting or WordPress so could really do with a pointer as to what I’m doing wrong and how to get this working!

    Thanks in advance

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator James Huff

    (@macmanx)

    Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your Dashboard, 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 Twenty Seventeen theme to rule-out a theme-specific issue. If you don’t have access to your Dashboard, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), 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 specific time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

    Thread Starter neilpcn

    (@neilpcn)

    Hi James,
    Firstly, thank you so much for taking the time to try and help fix this problem I am experiencing – I really do appreciate it.

    I have followed your steps, and unfortunately, there are still issues. I have access to the dashboard, so it was a pretty quick process. I deactivated all plugins and the problem remained although the images all appeared on the home page, which was an improvement from before!

    I changed the theme and it changed but the problems persisted.

    I changed the name of the htaccess file and the home page still works but the posts are now bringing a 404 error instead of a 500 internal server error.

    I’ve accessed the error logs and I get the following:

    [Tue Jun 12 04:34:11 2018] [error] [client 83.231.191.29] File does not exist: /home/cruisena/public_html/blog/404.shtml, referer: https://www.cruisenation.com/blog
    [Tue Jun 12 04:34:11 2018] [error] [client 83.231.191.29] File does not exist: /home/cruisena/public_html/blog/2018, referer: https://www.cruisenation.com/blog

    Hopefully something there will help? Thanks again.

    Moderator James Huff

    (@macmanx)

    Excellent, try re-saving your permalink structure at Settings/Permalinks in your admin panel. If WordPress cannot automatically edit the .htaccess file, it will provide manual instructions after saving.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Moving domains’ is closed to new replies.