"502 bad gateway error nginx" - web app working in http://itrendsolution.org:5000 but cant redirect "itrendsolution.org" to this address

Question

My web app runs in http://191.101.1.48:5000 My domain itrendsolution.org has IP address 191.101.1.48 [correctly pointing] but when i visit itrendsolution.org it shows "502 Bad gateway error nginx". I use cloudpanel (VPS hosting) to host the Flask web app , which has connection with MySql.

I used Nginx , so that when one visits https://itrendsolution.org they get redirected to the web app which runs in port 5000 in http [http://191.101.1.48:5000] through "proxy pass" of nginx configuration.

I do have ssl certificate . still when i visit itrendsolution.org its not working. it shows "502 bad gateway error nginx" How to make a web app running in http://191.101.1.48:5000 to get run in https://191.101.1.48 or itrendsolution.org ?

i tried nginx configuration to redirect.

nginx configuration:

server {
    listen 80;
    server_name itrendsolution.org www.itrendsolution.org;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    server_name itrendsolution.org www.itrendsolution.org;

    ssl_certificate /etc/letsencrypt/live/itrendsolution.org/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/itrendsolution.org/privkey.pem;

    location / {
        proxy_pass http://191.101.1.48:5000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    # Additional SSL settings
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_prefer_server_ciphers off;
    ssl_ciphers 'TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384';
    ssl_session_timeout 1d;
    ssl_session_cache shared:MozSSL:10m;
    ssl_session_tickets off;
    ssl_stapling on;
    ssl_stapling_verify on;

    # Additional configurations if needed

    location ~ /\.well-known {
        allow all;
    }
}

Answer 1

You should specify protocol in proxy_pass, e.g. proxy_pass http://191.101.1.48:5000; If nginx and your app are running on the same host, you can try to use proxy_pass http://127.0.0.1:5000;