Digitalocean step by step guide to nginx configuration

[phenomlab]

@justoverclock Anytime

[phenomlab]

@justoverclock You should change your app so that it only listens on localhost or 127.0.0.1 for security reasons as you are currently exposing it publicly via port 8080. The reverse proxy means that this is not required, as nginx redirects it for you and is fully secure.

[justoverclock]

@phenomlab so now this app use a server created by me with nodejs…so all the api endpoints are available through port 3030

can i set the env variable to https://vfgest.it:3030 ?

[phenomlab]

@justoverclock If the app is listening on 8080, which it typically would, then no, leave it alone. Are the endpoints intended to be public ? Typically, these aren’t accessible via nginx

[justoverclock]

@phenomlab if now i try to login, the endpoint of my api doesn’t work because of mixed content

Mixed Content: The page at 'https://vfgest.it/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://MYSERVERIP:3030/api/login'. This request has been blocked; the content must be served over HTTPS.

[phenomlab]

@justoverclock Yes, that’s expected. You should change your endpoint so it works over https otherwise it won’t be secure, and is then subject to eavesdropping as the traffic is being sent in clear text. From a security standpoint, this is an absolute no.

[justoverclock]

@phenomlab ok, so i can add https, can i leave the ip or i need to add vfgest.it:3030?

[phenomlab]

@justoverclock You can use either, but if the API is not meant to be exposed publicly, and should only be accessed by the app itself, then you should use 127.0.0.1. Ultimately, the design is up to you.

[justoverclock]

@phenomlab well, i’ve learned something new, no its a private crm developed by me, so no external use

[phenomlab]

@justoverclock Exactly - that’s why I asked You won’t be exposing the API then. Any issues, let me know.

[justoverclock]

@phenomlab ok i’ll try later when people are not using the crm :P, and i’ll post here the result

[phenomlab]

@justoverclock No problems.

[justoverclock]

@phenomlab its odd but doesn’t work if i use https://vfgest.it:3030 or https://SERVERIP:3030 or https://127.0.0.1:3030

must be something related to proxy…because server and client are on the same server…but works if i restore all to previous unsecure http connection

[justoverclock]

@justoverclock i’ve found an article that says
To resolve your issue you can setup nginx to proxy your http backend urls via https. With nginx server you will need to call your api like https://your_domain/api/some_path and nginx will proxy your request to api host, that you will set in config

so my server actually is on port 3030, what should i do?

thx!

[justoverclock]

@justoverclock ok i’ve found the solution by myself watching your files…

-i’ve created a subdomain

• a new server blocks that proxy requests to the backend endpoint
• secured with certbot

all works fine

[phenomlab]

@justoverclock Beat me to it ! I was going to say that you could add another server block to the existing configuration, so for example

location /api {
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header Host $http_host;
                proxy_set_header X-NginX-Proxy true;
 
                proxy_pass http://127.0.0.1:3030/;
                proxy_redirect off;
 
                # Socket.IO Support
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
}

[justoverclock]

@phenomlab i’m learning ahahahah

[phenomlab]

@justoverclock said in Digitalocean step by step guide to nginx configuration:

i’m learning

And that’s the whole point of this site If you don’t learn anything, you gain nothing.