Setting up Magento using reverse proxy

Preconditions and environment

Magento version Magento Release 2.4.8-beta1
NGINX- nginx version: nginx/1.24.0 (Ubuntu)
AWS 8GB RM, Ubuntu 24.04 , 20 GB Vol.

Steps to reproduce

Magento works fine, if I use a sub-domain and let's encrypt certifcate. Due to some requirements, I want to communicate with Magento via Private-IP. Below are my NGINX configurations of both servers , The Magento server seems to force for SSL certificate even inside the same VPC using private IP.
Frappe(ec2-instance) Server Block Configuration

server {
    listen 80;
    server_name mydomain.com;

    location /shop {
        proxy_pass http://<private-ip-of-other-server>;
        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;
    }
}

Magento Server Block Configuration

upstream fastcgi_backend {
  server  unix:/run/php/php8.3-fpm.sock;
}

server {
  server_name <private-ip-of-server>;
  set $MAGE_ROOT /var/www/html/magento2;
  include /var/www/html/magento2/nginx.conf.sample;
    }

video6154492151515321014-ezgif com-video-to-gif-converter

Magento’s Base URL Configuration

bin/magento config:set web/unsecure/base_url http://mydomain.com/shop/
bin/magento config:set web/secure/base_url https://mydomain.com/shop/

Unsecure Base URL for Static Files: bin/magento config:set web/unsecure/base_static_url http://mydomain.com/shop/static/ Secure Base URL for Static Files: bin/magento config:set web/secure/base_static_url https://mydomain.com/shop/static/

Unsecure Base URL for Media: bin/magento config:set web/unsecure/base_media_url http://mydomain.com/shop/media/ Secure Base URL for Media: bin/magento config:set web/secure/base_media_url https://mydomain.com/shop/media/

Expected result

Should be able to view Magento's homepage @ mydomain.com/shop without any issues.

Actual result

Additional information

No response

Release note

No response

Triage and priority

[X] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
[ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
[ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
[ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
[ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

Hi @princessfrombabylon99. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

For more details, review the Magento Contributor Assistant documentation.
Add a comment to assign the issue: @magento I am working on this
To learn more about issue processing workflow, refer to the Code Contributions.

Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

magento / magento2