Problem after migration to local server

  • Resolved ericwm

    (@ericwm)


    1 month, 4 weeks ago

    Recently migrated a copy of my site to a home server. All went well and I am able to log into wp-admin however when I try to access my site all i get is my masthead and menu and a message that says-

    It seems we can’t find what you’re looking for. Perhaps searching can help. Search for:

    but this search does not work. I also get page not found in the search bar. I have disabled all my plugins to see if this improves things but no luck.

    I did reset all urls to the local server address

    Advice would be appreciated

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter ericwm

    (@ericwm)

    Further to the above if I do a site health check I get-

    The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.

    When testing the REST API, an unexpected result was returned:

    REST API Endpoint: https://192.168.0.104/simonstown.org/wp-json/wp/v2/types/post?context=edit
    REST API Response: (404) Not Found

    For starters, could you enable debugging on your migrated site and see if you notice any fatal errors there? You will need to enable debugging and login to the WP Admin backend >> Visit the frontend (homepage) and then navigate to the /wp-content/ directory where you will find a debug.log file generated, which can give you some more insights about the issue.

    Here is how you can enable debugging: https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/#example-wp-config-php-for-debugging

    Also, when you mention
    > I did reset all urls to the local server address
    Do you mean that you also resaved the permalinks? If not, could you please do that first and see if that helps?

    Navigate to WP Admin >> Settings >> Permalinks >> Save Changes

    (Note: Please make a backup of your site before taking any action)

    Regards,
    Saurabh

    Thread Starter ericwm

    (@ericwm)

    I did try resaving the permalinks but get error .htaccess file is unwriteable but it is . even tried settting permissions to 777. Apache2 config var/www/html has AllowOverides set to all.

    If I try choosing the first option PLAIN it says that the ,htaccess file has been updated but it is not. I then went back to POSTSCRIPT and get the unwriteable error again. Tried editing the .htaccess file and inserting the suggested contents but still get pages not found

    Your issue appears to be related to server configuration or owner/group file/folder permissions, I believe the best solution would be to contact your hosting provider.

    If you want to gather more info you can go to wp-admin -> tools -> site health -> info and check the file and permissions section, if is there any permissions issues you should see that folder and not writable.

    You can find the same issue here in this thread, you may need to change the user group and owner to fix it:
    https://www.ads-software.com/support/topic/could-not-write-to-the-htaccess-file-please-check-the-file-permissions-3/#post-15803506

    Regards,
    Amin

    Thread Starter ericwm

    (@ericwm)

    Thank you for your response. My live installation is running ok. I downloaded the public_html folder and the database and installed them on a local server with a fresh copy of word press.

    Site health shows 1 Recommendation which is not under Critical Errors as follows

    The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.

    When testing the REST API, an unexpected result was returned:

    REST API Endpoint: https://192.168.0.104/simonstown.org/wp-json/wp/v2/types/post?context=edit
    REST API Response: (404) Not Found

    Under File Permissions only one Directory “FONTS” is shown as unwritable but ownership is www-data:www-data and permissions are for test purposes 777 so don’t know why getting this error.

    .htaccess file has ownership root:www-data and permissions 777 have tried root:root and www-data:www-data and still get unable to write to .htaccess file when saving permalinks. So I deleted this file and created a new one and inserted what the permalink save said it should be but still get 404 errors

    Thread Starter ericwm

    (@ericwm)

    deleted everything and started with a fresh wordpress install and fresh backup. Everything working OK.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.