Warning: file_get_contents connection timeout

Does the warning return if the log is cleared? It is possible this is a one time glitch on the network.

If the issue persists, I would check with your hosting provider if they are blocking requests from the server.

Thanks for the prompt response, Rogier. The warning does return if the log is cleared; seems like it occurs with a scheduled scan. There are no outbound blocks, as you can see from the wget command above that was run on the server. It can successfully connect and download the JSON signature file locally.

Any ideas on how to troubleshoot this?

@cosjef2023 I’ve done some searches on this, it seems that file_get_contents() requires a server setting allow_url_fopen = 1

Maybe using wp_remote_get works around this, I’ve created a branch with this adjustment, can you check if this works for you?

https://github.com/Really-Simple-Plugins/really-simple-ssl/tree/file_get_contents

What is the workflow to migrate to this branch? I have downloaded it on the server, decompressed it, and moved it to /public_html/wp-content/plugins directory. Do I deactivate the existing plugin, delete, then enable and activate your branch? Or is there a different order-of-operations I should follow here?

@cosjef2023 Easiest way I think is to

– ensure that the folder of the downloaded plugin is called “really-simple-ssl”
– then rename the current plugin folder on the server to really-simple-ssl-x.
– upload the really-simple-ssl folder with contents to the wp-content folder

If you don’t visit the plugins overview in the meantime, it won’t be deactivated.

Another method is to

– unzip the downloaded zip, rename the folder to “really-simple-ss”, and zip again.
– Go to plugins, add new, upload. Select this zip.
– WordPress will ask if you want to replace. Choose yes.

Replaced successfully with your branch. Cleared the log, so lets see what happens…Thanks!