nexcloud helm
Strict reverse proxies¶ This image uses a self-signed certificate by default. This naturally means the scheme is https. If you are using a reverse proxy which validates certificates, you need to disable this check for the container. src: https://docs.linuxserver.io/FAQ/#strict-proxy ... server { listen 10.1.2.3:80; server_name 10.1.2.3 myproxy.mycompany.com; location / { proxy_pass https://backend.server.ip/; proxy_ssl_trusted_certificate /etc/nginx/sslcerts/backend.server.pem; proxy_ssl_verify off; ... other proxy settings } src: https://serverfault.com/questions/341023/nginx-as-reverse-proxy-with-upstream-ssl ignored for now: proxy_ssl_trusted_certificate hope it works without…