Skip to content
This repository has been archived by the owner on Sep 3, 2024. It is now read-only.

No 'Access-Control-Allow-Private-Network' header was present in the preflight response #571

Open
PedroSouzaSRS opened this issue Mar 14, 2024 · 4 comments

Comments

@PedroSouzaSRS
Copy link

Hello everyone.

I have the following error when accessing tools.fortifyapp.com:

Access to fetch at 'https://127.0.0.1:31337/.well-known/webcrypto-socket' from origin 'https://tools.fortifyapp.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Private-Network' header was present in the preflight response for this private network request targeting the local address space.

Browser: Google Chrome 122.0.6261.112

Does anyone have an idea how to solve it?

@donskov
Copy link
Collaborator

donskov commented Mar 15, 2024

Hello @PedroSouzaSRS. What version of Fortify are you using?

@PedroSouzaSRS
Copy link
Author

Hello @donskov. Version 1.8.4

@donskov
Copy link
Collaborator

donskov commented Mar 25, 2024

@PedroSouzaSRS It seems that your browser does not trust the resource that Fortify is sending requests to.
Try to:

  1. remove the your home directory/.fortify folder.
  2. remove and install again Fortify.

@PedroSouzaSRS
Copy link
Author

@donskov I followed the recommended process but it didn't work.

Wouldn't it be necessary for Fortify to respond to the request with the "access-control-allow-private-network" header with the value "true"?

I verified that this header is not actually present in the preflight response.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants