Hi @neptun, thanks for reaching out to us for this.
That error typically means two things. Firstly, that the site is unable to connect to our servers and back to itself and secondly, the problem is likely to due to be the enforcement of SSL (or a secure https:// connection with a padlock icon as you’d usually see it in your browser.)
We may require you to relay information back to your host or try some steps, but I will try to make that as clear as possible.
For now, can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.
Note: For the fastest response time, please make sure and add any information or questions directly to this topic and not the email address above unless asked.
Thanks,
Peter.
Thread Starter
neptun
(@neptun)
Now (22.12.20 at 13.50 Finnish time) the scan seems to work! The scan once took a short break because my browser connection had to be confirmed. However, for the sake of certainty, I will be sending a diagnostic report that has been done right now.
Thanks a lot for the help!
Hi @neptun, no worries at all.
I’ve given your diagnostics a close look and there are no fails or errors in detecting things like IP or routes to our servers or back to your server. It may have been an intermittent issue at your host that has now resolved.
Thanks again,
Peter.