• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:
    https://survey.webpros.com/
  • On Plesk for Linux mod_status is disabled on upgrades to improve Apache security.
    This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.

Question Cors error on HTTP2 in google chrome

A

andyalvarez.developer

New Pleskian
Server operating system version
Debian 10
Plesk version and microupdate number
Web Host Edition VPS
The error is the following:
Access to XMLHttpRequest at ‘https://admin.example.com/’ from origin ‘https://admin.example.com/’ has been blocked by CORS policy: Request had a target IP address space of unknown yet the resource is in address space public.
Click to expand...

From the last update of google chrome, version: 102.0.5005.63 it only throws the mentioned error and not the functions it does not fulfill correctly…

I have read this official update note: Private Network Access update: Introducing a deprecation trial - Chrome Developers

Implement the necessary headers but the error persists on any apache website
Access-Control-Allow-Private-Network: true
Access-Control-Request-Private-Network: true
Click to expand...
 
You must log in or register to reply here.

Similar threads

s-light
Question NINGX CORS for multiple sub.domains
Replies
1
Views
3K
s-light
s-light
K
Issue Plesk NodeJS Server: CORS error upon every request
Replies
4
Views
4K
keithchasen
K
I
Issue CORS: "Only One Origin Allowed"-Error - where does second origin * come from?
Replies
0
Views
2K
it78croix
I
M
Issue plesk cors policy, either no header or multiple headers
Replies
2
Views
4K
Peter Debik
P
PeopleInside
Resolved Issue with Cors
Replies
16
Views
8K
PeopleInside
PeopleInside
Back
Top