Error 520 problems - no solution since months

Getting Started
#1

Hello,

I posted our error here:

But I got no solution so far. The 520 error appears every day again (when I am saving something in our WordPress backend.

This page I got problems with: https://www.unaufschiebbar.de/

Here you find a screenshot of an actual error message (12/10/2021 15:02:52):

Bildschirmfoto 2021-10-12 um 15.02.58
Bildschirmfoto 2021-10-12 um 15.02.581920Ă—1200 94.4 KB

What can I do?

Best regards,

Christian

#2

I am still baffled by you saying your server address does not end in 73.

$ curl -s https://www.unaufschiebbar.de | grep Willkommen
Willkommen bei unaufschiebbar! Unser Weltreiseblog teilt sich in zwei Bereiche: <br>
<h2 style="text-align: center;">Willkommen auf unserem Reiseblog</h2>

$ curl -sk --resolve www.unaufschiebbar.de:443:X.X.X.73 https://www.unaufschiebbar.de | grep Willkommen
Willkommen bei unaufschiebbar! Unser Weltreiseblog teilt sich in zwei Bereiche: <br>
        <h2 style="text-align: center;">Willkommen auf unserem Reiseblog</h2>
1 Like
#3

Hi, I am deeply sorry. I don’t know what this means and above all what I can do if this fix the problem.

Could you please advise me?

Best regards

Christian

#4

I have now put the security option from here:

Bildschirmfoto 2021-10-14 um 08.36.09
Bildschirmfoto 2021-10-14 um 08.36.092052Ă—914 187 KB

to here:

Bildschirmfoto 2021-10-14 um 08.41.01
Bildschirmfoto 2021-10-14 um 08.41.012164Ă—1114 169 KB

But after that, I get “Error 526 Ray ID: 69decb75caa45b4a • 2021-10-14 06:36:41 UTC
Invalid SSL certificate”

Would it be working if I am ordering the “advanced certifiacte mnager” for 10 $ pe rmonth? Or what should I do to prevent the security issue?

#5

That’s precisely because you have an invalid certificate on your server. You need to fix this and configure a valid one.

Why you should choose Full Strict, and only Full Strict has all on that.

#6

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.