You’ve specified two different URLs in your settings – one with an “s” and one without. If you want to use only one of them, you’ll need to update the other accordingly.
Otherwise, I don’t see any place in the frontend where your website’s pages are linked using https://. So I’m not sure how you came up with the URL mentioned above.
But yes, you can adjust this manually – that is, access your pages with an “s” – because your host provides you with the necessary SSL certificate. But you obviously have to do this manually; as far as I can see, nothing on your website leads there.
Not using SSL has also been a disadvantage for search engine visibility for many years. Search engines like Google prefer websites with an SSL certificate. Compared to others offering similar content, your website will therefore rank lower in search engine results simply because of the lack of https:// links. This has nothing to do with what you might collect from your visitors. It serves the security of your visitors, since they know neither you nor your website. And that’s important to Google, too.
Sorry, I’m none the wiser.
In the General Settings, both the WordPress Address (URL) and Site Address (URL) are set to http://www.fhithich.uk .
I am happy with this.
In the Permalink Settings, the setting is https://www.fhithich.uk/…
I would like to change this, but I don’t see how.
HTTP has served me well for 11 years, ranking lower in search engines, I can live with. It is a non-commercial site with a small regular user base, and I need to keep costs down. I am reluctant to spend the £150 my host (123Reg) asks for issuing their certificate. As for Let’s Encrypt, it’s a complete mystery. So I am happy to leave things as they are — if it weren’t for this Permalink Setting.
Thanks.
I see in your website’s settings from the outside that you should have two different entries for the Website URL under Settings > General. I’m referring to this screen here: https://ww.wp.xz.cn/documentation/article/settings-general-screen/
I’m surprised to see that you have a domain listed under Permalinks. I’m guessing you can’t edit it there? I’m referring to this screen here: https://ww.wp.xz.cn/documentation/article/settings-permalinks-screen/ – if you can or have entered a domain there, something is generally wrong with the settings there. That section only defines the structure of the URLs; it doesn’t set up a domain.
Feel free to show us what you see with a screenshot; see: https://ww.wp.xz.cn/support/forum-user-guide/block-editor/#adding-screenshots
Interesting. Then it’s possible that a plugin you’re using is altering the URL. Are you using a security plugin? As a test, you could try deactivating them all and see if that changes the output in the permalinks.
As I said, though, this doesn’t affect the front end. There, all links are still without SSL.
Thanks. I deactivated each of my 9 plugins in turn but it made no difference to the permalinks settings
Hi @fhithich ,
I would be delighted to help you resolve this. The problem is not from your plugin but from a snippet of code in your root wp-config.php file. This code forces WordPress to disregard the URL submitted in the ‘permalinks’ section.
Go to your site files (File Manager) through your hosting account’s cPanel and edit the wp-config.php file. You should see this snippets of code:
define( 'WP_HOME', 'http://www.fhithich.uk' );
define( 'WP_SITEURL', 'http://www.fhithich.uk' );
You can delete both lines of code so WordPress honours the URL set in permalinks section and to avoid further mixed content issues.
Also ensure your DNS server is well propagated so the www and the non-www version of your site is available to visitors. Let me know if this fixed the issue or if you need help with something else.
Thank you for your help. I located the wp-config.php file but can not see the two define statements you mention.
Here is my wp-config.php file. I have replaced anything that looks remotely like a password or authorisation key by asterisks, just in case.
<?php
/**
* The base configurations of the WordPress.
*
* This file has the following configurations: MySQL settings, Table Prefix,
* Secret Keys, WordPress Language, and ABSPATH. You can find more information
* by visiting {@link http://codex.ww.wp.xz.cn/Editing_wp-config.php Editing
* wp-config.php} Codex page. You can get the MySQL settings from your web host.
*
* This file is used by the wp-config.php creation script during the
* installation. You don't have to use the web site, you can just copy this file
* to "wp-config.php" and fill in the values.
*
* @package WordPress
*/
// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'ssf0qfc_a-wor-tb');
/** MySQL database username */
define('DB_USER', 'ssf0qfc_a-wor-tbx-u-137765');
/** MySQL database password */
define('DB_PASSWORD', '************');
/** MySQL hostname */
define('DB_HOST', 'localhost');
/** Database Charset to use in creating database tables. */
define('DB_CHARSET', 'utf8');
/** The Database Collate type. Don't change this if in doubt. */
define('DB_COLLATE', '');
/**#@+
* Authentication Unique Keys and Salts.
*
* Change these to different unique phrases!
* You can generate these using the {@link https://api.ww.wp.xz.cn/secret-key/1.1/salt/ ww.wp.xz.cn secret-key service}
* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
*
* @since 2.6.0
*/
define('AUTH_KEY', ''************');
define('SECURE_AUTH_KEY', ''************');
define('LOGGED_IN_KEY', ''************);
define('NONCE_KEY', ''************);
define('AUTH_SALT', ''************);
define('SECURE_AUTH_SALT', ''************);
define('LOGGED_IN_SALT', ''************');
define('NONCE_SALT', '************);
/**#@-*/
/**
* WordPress Database Table prefix.
*
* You can have multiple installations in one database if you give each a unique
* prefix. Only numbers, letters, and underscores please!
*/
$table_prefix = 'wp_';
/**
* WordPress Localized Language, defaults to English.
*
* Change this to localize WordPress. A corresponding MO file for the chosen
* language must be installed to wp-content/languages. For example, install
* de.mo to wp-content/languages and set WPLANG to 'de' to enable German
* language support.
*/
define('WPLANG', '');
/**
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*/
// Enable WP_DEBUG mode
define( 'WP_DEBUG', false );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', false );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );
/**
* Change this to true to run multiple blogs on this installation.
* Then login as admin and go to Tools -> Network
*/
define('WP_ALLOW_MULTISITE', false);
/* That's all, stop editing! Happy blogging. */
/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
define('ABSPATH', dirname(__FILE__) . '/');
/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');
/* Destination directory for file streaming */
define('WP_TEMP_DIR', ABSPATH . 'wp-content/');
@fhithich ,
Thanks for the update. I visited your website and it seems everything now works fine.
I’m really confused. I’ve changed nothing. I was getting loads of complaints that users were getting security warnings but I must admit they’ve seemed to have stopped. Fingers crossed.
Thanks for your help.
