• It seems it can happen that one is not properly logged in when going to another subsite. Block editor will not work (save) and console reveals all calls to REST API and AJAX returns 403 Forbidden.

    Logging out, then back in, fixes this. That, however, makes this method not worth while and even dangerous for going high in CPU on server. When 403 is returned, block editor will retry endlesssly, many times per second and no error message (just hangs on save). If left at it, CPU peaks and stays high – server system (cPanel) may penalize this.

    It seems browser need to have all cookies correct to be able use AJAX/REST.

  • The topic ‘403 Forbidden on AJAX & REST’ is closed to new replies.