Got it solved. Turns out the server was hosted behind a reversed proxy, causing WordPress not knowing it was running over https. Once I knew this, I found the solutions in the official documentation: http://codex.wordpress.org/Administration_Over_SSL (under “Using a Reverse Proxy”) This was needed in my wp-config. define(‘FORCE_SSL_ADMIN’, true); if ($_SERVER[‘HTTP_X_FORWARDED_PROTO’] == ‘https’) $_SERVER[‘HTTPS’]=’on’
First, rename the folder wp-content/plugins/wordpress-https to wp-content/plugins/wordpress-https-OFF so that WordPress can’t find it to run it. Second, add the following lines to your wp-config.php file, replacing the domain name with your domain name: define( ‘WP_SITEURL’, ‘http://example.com/’ ); define( ‘WP_HOME’, ‘http://example.com/’ );
You’ve put the code in the wrong place. The HTTP to HTTPS directives must go before the WordPress front-controller, otherwise it’s simply never going to get processed for anything other than direct file requests. Your custom directives should also be outside the # BEGIN WordPress block, otherwise WordPress itself is likely to override your directives … Read more
I should think that you can use phpAdmin Find and Replace where you find “http://www.example.com” and replace with “https://www.example.com“. This should handle all internal linking (if blog, then internal linking as well as images, etc.). It would not cover relative addressing like “//www.example.com”. In the case of WordPress, this would be done on the wp_posts … Read more
You will need to convert the relative links to absolute links. You can do this in the wp_nav_menu_objects filter, which gets all menu items. Just edit the url property of each item. Another option would be to extend the default Walker_Nav_Menu with one that overrides start_el(), so you can modify the passed $item there before … Read more
If available always use https, it is securer for obvious reasons, it is better received by search engines and browsers nowadays, it is just overall preferable. 1 Backup Should go without saying, but backup your database. There is always a possibility that something goes wrong. Additionally, make sure you have access – ssh, ftp, etc … Read more
Issue was caused by nginx serving example.com/index.php while WordPress was redirecting to example.com/, thus causing a redirect loop. This is the working config I used to fixed the redirect loop: server { server_name example.com; root /var/www/example.com; index index.php; listen 443 ssl; ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; include /etc/letsencrypt/options-ssl-nginx.conf; ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; location / { try_files $uri @apache; … Read more
Make default new sites https (multisite)
Add this code in to wp-config.php just before – require_once ABSPATH . ‘wp-settings.php’; line if ($_SERVER[‘HTTP_X_FORWARDED_PROTO’] == ‘https’) $_SERVER[‘HTTPS’]=’on’;
If you can access the SSL version of your blog without a problem, then it means you can redirect all your traffic to it. To do so, take these 2 steps: Access your database using PhpMyAdmin or any other software you want. Head over to wp_options table, and change to values of siteurl and homeurl … Read more