The HTTP request which makes use of CORS failed because the HTTP connection
failed at either the network or protocol level. The error is not directly
related to CORS, but is a fundamental network error of some kind.
In many cases, it is caused by a browser plugin (e.g. an ad blocker or
privacy protector) blocking the request.
Other possible causes include:
Trying to access an https resource that has an invalid certificate will
cause this error.
Trying to access an http resource from a page with an https origin will
also cause this error.
As of Firefox 68, https pages are not permitted to access
http://localhost, although this may be changed by Bug 1488740.
The server did not respond to the actual request (even if it responded
to the Preflight request). One scenario might be an HTTP service being
developed that panicked without returning any data.
Checked the TLS Certificates with https://www.digicert.com/help/ :
and the result is:
" TLS Certificate has not been revoked.
TLS Certificate expires soon. The primary TLS Certificate expires on
February 28, 2020 (30 days remaining)
Certificate Name matches ggc.world
TLS Certificate is correctly installed "
So may be my nginx configuration has to be improved.
That seems to show that from a different machine, you can access nginx,
which reverse-proxies to vue; and the content from vue includes links or
redirects to localhost (and to localhost:8080). And those links will fail.
I cannot tell from these pictures what one http request was made and what
response was received -- maybe the output of "curl -vk https://ggc.world"
from this machine will show something?
If the issue is that vue is returning a http 301 or 302 redirect to
something below localhost or localhost:8080, then either changing that
in vue, or adding proxy_redirect in nginx, may be best.
If the issue is that vue is returning a http 200 with content that links
to localhost, then that should be changed in vue.
I suspect that almost anything in the vue config that mentions localhost,
should be removed. But vue people may be a better source of information
That picture looks like the right-hand side is showing the "request
details" of the fifth request down, the red "info" one.
Look at the first few successful requests instead.
Or maybe "view source" of the main page, and look at the html that
was returned. What puts the word "localhost" into that html?
> " Either a http redirect response header, or some response body content,
> invites the browser to try to access localhost" :
> as far as I see and understand, the requested URL, or the URL to which the
> initial request is redirected, from the initial https://ggc.world , is:
> Request URL: https://localhost/sockjs-node/info?t=1580484448072
I don't see that.
Can you see or show the complete response to the initial request?
> I ask you... am I right or wrong in thinking that this proxy_pass address
> has to be changed?
I think it probably does not need to be changed.
I think that either you need to add some nginx proxy_redirect lines; or
you need to change the vue setup to never use the word "localhost". Or
If you can show where the word "localhost" appears in the response to the
request for ggc.world, it may be clearer where the change should be made.