Make WordPress Core

#48971 closed defect (bug) (invalid)

Errors after update to 5.3.1

Reported by: caraya Owned by: audrasjb
Milestone: Priority: normal
Severity: normal Version: 5.3.1
Component: Bootstrap/Load Keywords: reporter-feedback close
Focuses: Cc:


I am getting the following errors when previewing a post after upgrade to 5.3.1

public-api.wordpress.com/wp-admin/rest-proxy/?v=2.0:6 WebSocket connection to 'wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data' failed: Error during WebSocket handshake: Unexpected response code: 403

==/?p=789855&preview_id=789855&preview_nonce=8860e6b287&post_format=standard&_thumbnail_id=-1&preview=true:1 Failed to set referrer policy: The value 'is not one of 'no-referrer', 'no-referrer-when-downgrade',
'origin', 'origin-when-cross-origin', 'same-origin', 'strict-origin', 'strict-origin-when-cross-origin', or 'unsafe-url'. The referrer policy has been left unchanged.

Normally I wouldn't have noticed but it keeps reloading my syntax highlighter plugin and changing the way that code looks in the post. The same errors happen in Firefox Nightly, Chrome Canary (80) and Crome Stable (79)

Change History (5)

This ticket was mentioned in Slack in #core by audrasjb. View the logs.

22 months ago

#2 @audrasjb
22 months ago

  • Keywords reporter-feedback close added
  • Owner set to audrasjb
  • Status changed from new to reviewing

Hi @caraya thank you for this ticket and welcome to WordPress Trac!

Looks like an issue with your plugin. Could you please mention its name?

(adding close keyword as it seems to be plugin related)

#3 @SergeyBiryukov
22 months ago

To clarify a bit, WordPress core does not have any references to public-api.wordpress.com/wp-admin/rest-proxy/, so this does seem like a plugin issue.

Does it still happen with all plugins disabled and a default theme (Twenty Twenty) activated?

This ticket was mentioned in Slack in #core by audrasjb. View the logs.

22 months ago

#5 @audrasjb
22 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from reviewing to closed

Closing this ticket as invalid (which is Trac resolution keyword used for tickets that are not related to WP Core) after waiting for reporter feedback, as it doesn't looks to be related to WordPress Core.

Feel free to reopen the ticket if you have further information about the context of the issue.

Note: See TracTickets for help on using tickets.