The first and most important thing to know is that your SSL certificate is tied to a SPECIFIC Domain Name. Using a CNAME to create an alias from another Domain Name WILL route your traffic to the other URL BUT unless you have also purchased an SSL Certificate for the other site & setup an … Read more
Changing proxy_set_header Host $host; to proxy_set_header Host $http_host; fixed the issue. (source)
I don’t think this question can be answered without identifying the problem, which explains the comments. The main challenge is finding the cause, not fixing it. So here are some different solutions, some which were already mentioned in comments: Disable caching and refresh the page. In chrome press F12, go to Network tab, and check … Read more
If you are using docker-compose and the WORDPRESS_EXTRA_CONFIG as I was, when I stumbled across that error, the solution would be to use double-dollar-sign notation as described in a corresponding issue in the docker-compose repo on GitHub. This additional environment variable is described in the “How to use this image” of the official image documentation … Read more
I had the same problem and solved it by moving the two define statements up before the require_once that includes wp-settings.php. Seems this was the issue all along. Source: https://stackoverflow.com/a/27193576/117268
From the description of the error you get, it seems like you do not get at all to your account related software when trying to access the child on http. This sounds like a web server configuration error, so in your case you need to make sure that in your cpanel you enabled subdomains for … Read more
WordPress has built-in function for this purpose – is_ssl(). http://codex.wordpress.org/Function_Reference/is_ssl So, you should edit this widget and put something like if ( is_ssl() ) { } else { echo ‘you should use ssl’; }
Do you have to have secure.domain.com function or can it redirect? The tl;dr is that you don’t. The primary domain is the cheese: it stands alone. However…. You can use .htaccess to check ‘If someone is coming from secure.domain.com, send them to domain.com’ RewriteCond %{HTTP_HOST} ^secure\.domain\.com RewriteRule ^(.*) http://domain.com/$1 [L,R=301] RewriteCond %{HTTP_HOST} ^www\.domain\.com RewriteRule ^(.*) … Read more
If assets are enqueued properly they are using the exact URL they are enqueued with. If the protocol in URL is hardcoded that causes mismatch issues you are seeing. For proper protocol support enqueued URLs need to be either: created with protocol-aware API function from WP API (most if not all functions that produce URLs … Read more
Just figured it out… It was the positioning of the define statement. I added the below above the /* That’s all, stop editing! Happy blogging. */ line define(‘FORCE_SSL_ADMIN’, true); define(‘FORCE_SSL_LOGIN’, true); Thanks!