#failed to fetch 2.0

44 messages · Page 1 of 1 (latest)

calm creek
#

i was getting this error (view the screenshot 1)
I added <meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">
And now i get this:

#

my app runs on remote linux server. Frontend runs on nginx and backend is a java app

#

i am lost. What to do in that situation?

safe oyster
#

Enable HTTPS?

calm creek
calm creek
#

i changed my rul several times:
https
http
domain instead of localhost
ip of server instead of localhost
Tried to add meta tag
Nothing worked

safe oyster
#

dafaq? enabling https has nothing to do with meta tags

calm creek
#

And can i ask you to answer to messages, so i can get pinged

safe oyster
#

with what little information you provided, it sure sounds like you should be able to just set up an nginx reverse proxy for the API routes

calm creek
safe oyster
#

The API server (as I said)

calm creek
safe oyster
#

Then stop sending HTTP requests…

calm creek
#

but nothing changed

#

look

safe oyster
#

Clearly your API server is not accepting HTTPS connections on port 8080

calm creek
#

and it worked

safe oyster
#

congrats

calm creek
#

it only means, that backend is fine

#

and problem is with frontend

safe oyster
#

not necessarily

calm creek
#

maybe nginx

calm creek
safe oyster
#

all sorts of things on the backend could allow local connections but not remote connections (firewalls, nginx configs, etc.). what is behind the red line?

#

if it's localhost or 127.0.0.1, that's possibly your issue. if not, nginx is probably not configured to handle whatever host/port it is

safe oyster
#

that's meaningless. it could be a LAN IP or a localhost IP, which wouldn't be accessible from elsewhere

safe oyster
#

...

calm creek
calm creek
calm creek
#

lmao

#

thanks for help, mr ironic

#

but now i have new errors😁

safe oyster
#

not sure what part of my comments would be ironic, but okay