Resolved WP Toolkit site URL not https

[DerDanilo]

The site url is not beeing detected as https, though it is https on backend and frontend.

• Checked that WP settings all contain https
• Checked Security Plugins
• Did several rescans with WP Toolkit

How does the WP Toolkit detect the url here?
Could you allow admins to manually edit the url for the page? (currently not possible)

Thanks!

 

[UFHH01]

Hi Danilo Schwabe,

did you as well consider to check the current "Hosting Settings" for the (sub)domain? If the option "Permanent SEO-safe 301 redirect from HTTP to HTTPS " isn't set, the option to use "HTTP" is still available with your webserver configuration files ( if you don't manually add redirects ).

How does the WP Toolkit detect the url here?

This depends on your webserver configuration files for the corresponding (sub)domain.

Could you allow admins to manually edit the url for the page? (currently not possible)

Could you pls. explain, WHY you desire such a manual edit - feature and in which cases this might be relevant?

 

[DerDanilo]

Thanks for your reply @UFHH01

Hi Danilo Schwabe,

did you as well consider to check the current "Hosting Settings" for the (sub)domain? If the option "Permanent SEO-safe 301 redirect from HTTP to HTTPS " isn't set, the option to use "HTTP" is still available with your webserver configuration files ( if you don't manually add redirects ).

This option was/is enabled.

Could you pls. explain, WHY you desire such a manual edit - feature and in which cases this might be relevant?

This is in case the automatic detection fails for some reason.


I just did a rescan (again) of all pages and for some reason it detected all pages with https now.
Any idea why it didn't detect this earlier?

 

[trialotto]

@Danilo Schwabe

In reaction to the question

I just did a rescan (again) of all pages and for some reason it detected all pages with https now.
Any idea why it didn't detect this earlier?

I can only state: it is not entirely clear "why".

I can mention that, at least in my experience, some issues can arise from the method that Plesk uses to store WP related data:

- the https prefix should be stored in the database associated with the WP instance on the specific domain,
- the WPT data is primarily stored in some specific tables in the psa database,
- the WPT also "reads" (and, in some cases, "writes") data from specific files and/or directories belonging to the domain hosting the WP instance,

and you can imagine by now that a temporary difference can occur between the actual values and the values presented by Plesk and the WPT in particular.

I hope that this explains a bit of the background relevant for the WPT.

Regards.....