SSL mixed content issue

We are using Nexus Repository Manager version OSS 3.15.2-01,
We using Let’sencrypt for SSL, And we are using Nginx for proxy server.
After applying SSL for Nexus repository, we facing the mixed content error,
Can anybody help me on this?

You need to configure nginx to send the X-Forwarded-Proto header:

https://help.sonatype.com/repomanager3/installation/run-behind-a-reverse-proxy#RunBehindaReverseProxy-nginx.2

Regards,

Rich

have changed the X-Forwarded-Proto header to “https”
still i am facing the same error.

For you reference, this is my nginx.conf file:

server {
listen 80;
listen [::]:80;
server_name
registry.example.com
;

return 301 https://registry.example.com$request_uri;

}

server {
listen 443 ssl;
listen [::]:443 ssl;
server_name
registry.example.com
;

if ( $host ~* “^www.(.*)$” ) {
return 301 https://registry.example.com$request_uri;
}

access_log  /var/log/nginx/registry.example.com.access.log;
error_log  /var/log/nginx/registry.example.com.log;

ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot
proxy_intercept_errors on;

error_page 404 /error_404.html;

location = /error_404.html {

root /etc/nginx/error-html-pages;

internal;

}

error_page 502 503 504 /error_other.html;

location = /error_other.html {

root /etc/nginx/error-html-pages;

internal;

}

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-SSL   on;
proxy_set_header    X-Forwarded-Proto "https";

ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
ssl_ciphers "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 EECDH EDH+aRSA HIGH !RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS";

include /etc/nginx/conf.d/sites-enabled/frontend.d/*.conf;
}

upstream frontend {

server 177.67.65.10:8081;
}