Keywords: WordPress + NGINX + SSL - AWS - Technical issue - Secure Connections (SSL/HTTPS)
bnsupport ID: 4a232bd8-fcfd-428c-afcd-809438084fd9
In all WP + HTTPS Docs, and in my previous experience, you set the wp-config.php variables WP_HOME et al to https:// sitename/, you open up the https port and you enable redirect from :80 to :443. The first setting causes WP scripts and such to attempt to link to media, access the rest api et c over HTTPS, the second makes it possible to access the site and the last one makes HTTPS mandatory.
Now in the docs for Bitnami WP + NGINX + SSL it says to leave the WP-config variables as http:// sitename/, the port is already open and HTTPS redirect in NGINX is configured according to bitnami docs.
Now as seems logical to me, the site has a broken padlock over mixed content warning, since I effectively haven’t told WP to link back to itself over HTTPS, but if I just for a laugh change the WP-config.php variables to https:// sitename/, the padlock returns (maybe?), but login to WP-admin breaks.
What have I missed? How do I make WP “talk to itself “ over HTTPS?