• Resolved tonycollinet

    (@tonycollinet)


    I was having this problem on a new site, to which I’d imported an old database. I thought the database might be the issue, so I’ve just installed a new untouched 6.2.2 installation and it is still happening. (untouched = no posts/pagest etc created. No plugins installed or active etc)

    If I change the permalinks to anything other than ‘Plain’, then site health gives the REST API error shown below. I am also unable to load the site editor (I get a permanently spinning wheel). Switching back to ‘Plain’ solves both problems.

    As part of diagnosis, I noticed that there is no HTACCESS file. So wordpress is not creating this. I’ve tried repeated saves of the permalink setting. No error message is given.

    The server is a synology NAS. PHP 7.4, and nginx webserver.
    The HTTP user has full read and write access to the folder.

    Thanks for any help.
    Ant.

    ****rest api error****
    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://grandpops.collinsho.myds.me/wp-json/wp/v2/types/post?context=edit
    REST API Response: (404) Not Found

    • This topic was modified 1 year, 8 months ago by tonycollinet.

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator t-p

    (@t-p)

    If I change the permalinks to anything other than ‘Plain’, then site health gives the REST API error shown below

    If ‘Plain’ works, then try reading Using_Permalinks before setting a custom permalink structure again.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Also, make sure that you have “AllowOverride All” set up in your apache configuration for the directory in which you have WP installed.

    Thread Starter tonycollinet

    (@tonycollinet)

    OK – I think your suggesting server side settings (Although currently using nginx rather than apache). Will have a look a bit more and get back.

    Thread Starter tonycollinet

    (@tonycollinet)

    Just to help anyone else with the same problem. For me this was solved simply by changing the HTTP back end from nginx to Apache.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Synology server – REST API problem, no HT Access file.’ is closed to new replies.