Register or log in to explore all our content and services for free on Admin Junkies.
Last i read on XF, it was related to http/2 connection from CF to server, that was causing it. Try this fixCan't say I ever had that. Checked the server errors and nothing came up. I think it can happen sometimes with us being on Cloudflare. Refreshing solves the problem, but like I said, don't know really what causes it to happen.
This is already disabled.Last i read on XF, it was related to http/2 connection from CF to server, that was causing it. Try this fix
Suddenly tons of CF 520 errors
Hello everybody, since yesterday afternoon there are 520 error messages from Cloudflare in our forum. The error occurs completely randomly and everywhere. We only moved to a new server a few weeks ago and everything went perfectly. I will of course also contact my hoster. But I have already...xenforo.com
@Debashis your errors could be result of server configuration changes. It is being looked into.
Well it was a mistake at my end. It was 502 error from the start, I have mentioned 520 from beginning. Just edited the thread title.I would also note.
For any user that comes across either of these errors. The more information you can provide the better. Why? Well.... In the spec for http2 does away with response reason phrases as most developers know them. Now, if the response is in http2 / http3 you do not get a phrase, you only get the code. Why does that matter? Well, with a custom reason phrase the developer can provide context to the message. In this particular situation that context is missing. Furthermore, as I stated before the 520 is a custom, but well known, response code that is primarily returned from cloudflare, but in reality means very little when trying to diagnose the issues. Thank you for your patience in regards to this matter. Please know, @Cedric and others are working on resolving the issue.
Sure, Cedric! Thanks! Will do.Thanks Deba, we're monitoring the server logs frequently and see if we can find the connection that causes this. So, if it happens, report back to this topic and include details such as the link you were trying to visit.
You ideally need to be running on 8.1 until the next update. This error could also be caused by the add ons not being compatible with the latest php version. You can always try disabling the add ons by changing config.php and starting a sandbox to see if that is where the issue is at. Replace the listeners line with the following: $config['enableListeners'] = false; and this will disable add ons temporarily to see if this could be causing the problem.Seems to be more happening since the upgrade to php 8.2. We’ll probably do some more investigation later today and check some settings.
They happen across the Jcink network, even my own board, but I haven't had it happen in a while now.@Cory could you provide links to those sites please? I want to check and see what http version their site is using.
I don't have access to that info.@Cory is it possible for you to do the same for your site?
Log in or register to unlock full forum benefits!