siteurl or homeurl in your wp-config.php

In your wp-config, you have to look for

define('WP_HOME','https://example.com');
define('WP_SITEURL','https://example.com');

and change the http into https.

Hello Rogier,
Thanks for the reply, wp-config.php file is already modified and following are the two entries;

define(‘WP_SITEURL’, ‘https://’ . $_SERVER[‘HTTP_HOST’] . ‘/wordpress’);
define(‘WP_HOME’, ‘https://’ . $_SERVER[‘HTTP_HOST’] . ‘/wordpress’);

Any errors in the above entries,

Regards,

Can’t confirm the url of course, but the define(‘WP_SITEURL’,’https… part looks good.

Do you still get the warning with this code?

yes, the warning is still showing up.
Thanks

It goes away when Really simple SSl plugin deactivates.
Thanks

The warning is generated by really simple ssl, so it will disappear on deactivation. But it should only show when you have http constants in your wp-config.php, and the file is not writable.

There is no problem really, because your urls are already fixed. It’s just strange the message doesn’t disappear.

I’ll do some tests to see if I can find anything.

Did you check if there is another definition of the homeurl and siteurl in your wp-config.php?

In my testing your definitions were not detected at all, because of an extra space. I’m going to fix this, but that is clearly not your issue.

If the definitions are https, detected as such, and the wp-config.php is not writable, I do not get a warning, so maybe there is another definition in your file.

Using wp 401 with Genesis and w3tc on synthesis hosting platform

Hi, I have a similar problem with really simple ssl plugin that is saying

We detected a definition of siteurl or homeurl in your wp-config.php, but the file is not writable. Because of this, we cannot set the siteurl to https.

when I check the debug within really simple it shows (in part) otherwise plugin and ssl seems to be working.

not able to fix wpconfig siteurl/homeurl.

I looked at support site at RSSSL and found this thread.

In your wp-config, you have to look for

>>>
define(‘WP_HOME’,’https://example.com’);
define(‘WP_SITEURL’,’https://example.com’);
and change the http into https.
<<<<

However, when looking at my file wp-config.php

I don’t see the this

In your wp-config, you have to look for

define(‘WP_HOME’,’https://example.com&#8217;);
define(‘WP_SITEURL’,’https://example.com&#8217;);
and change the http into https.

What I see instead is

/** Enable W3 Total Cache Edge Mode */
define('W3TC_EDGE_MODE', true); // Added by W3 Total Cache

/** Enable W3 Total Cache */
define('WP_CACHE', true); // Added by W3 Total Cache

/** Enable W3TC PRO for Synthesis */
define('W3TC_PRO', true); // Added by Synthesis

/** Disable the default WordPress Cron */
define('DISABLE_WP_CRON', true);

/** code from really simple ssl */
//Begin Really Simple SSL Load balancing fix
if (isset($_SERVER["HTTP_X_FORWARDED_PROTO"] ) && "https" == $_SERVER["HTTP_X_FORWARDED_PROTO"] ) {
  $_SERVER["HTTPS"] = "on";
}

does that code for really simple ssl mitigate the issue and I am receiving a false report?

Or is there something that still needs to be fixed

The plugin checks for a definition of the siteurl in the wpconfig. If it is defined there and the wpconfig.php is not writable, the website cannot convert to https properly, so if the string “define(‘WP_SITEURL’,’https://&#8221; is encountered, you get this warning.

The code you refer to is something else and prevents Wp from getting in redirect loops. This string does not contain a siteurl or homeurl definition, so cannot cause the warning.

Did you do a search in your wp-config for the string WP_SITEURL or WP_HOME? Maybe it is somewhat more to the bottom of the file.

the define code was not in wp-config.php

I changed permissions for file to 644 and added

define(‘WP_HOME’,’https://contracostabee.com&#8217;);
define(‘WP_SITEURL’,’https://contracostabee.com&#8217;);

the nag is gone and I can change the permission back

In the next update I’ll change the preg_match check, maybe that causes this. Hard to debug, as I can’t reproduce it.

Thanks for the feedback.

Rogier

Change the file permission to 770 and the error message is gone.

Original file permission is 750.

-rwxrwx—. 1 root daemon 3580 Dec 2 10:07 wp-config.php

Thanks for the help,
Ra

I’ve released an update that should fix this issue. The check for defines in the wpconfig returned results, even when none were found.