✔️ Resolved 502 errors on forum

[SoluDome]

Does anyone else get these error here or it's just me?

 

[Cedric]

Can'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.

 

[SoluDome]

Can'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.

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

 

[Tyrsson]

Interesting

 

[Cedric]

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

This is already disabled.

 

[Cory]

I'm on other forums that do this too. Like Jcink, for instance, it can sometimes happen semi-frequently. So, I don't think it's limited to just Admin Junkies.

 

[Tyrsson]

Ok, so, after doing a little digging I am curious about a couple things.

@Cory could you provide links to those sites please? I want to check and see what http version their site is using.

After reading that post and checking a couple things here I noticed a couple things that are odd.

@Cory your site responds via http/1.1
@Cedric your site also responds via http/1.1 on the main thread, however, you have code that is kicking off an ajax post request to the following url:
https://admin-junkies.com/job.php (what is this file for?)
which is being made via http/2, to a http/1.1 version server (from what I can discern from the little digging I've done).

From reading the CloudFlare docs in regards to this they claim they return the 502 (520 is not a standard response code) when the origin server responds with a 502.

This leads me to a couple of questions.
@Cedric can you find records of the 502's in the server logs for aj's? If so can you cross check those with logs from the forum please and let me know if there is any intersection of those two base on timestamp, does not matter what the error in the forum log is for if the timestamps are very very close.

@Cory is it possible for you to do the same for your site?

If either has any type of monitoring setup it may pay to check those as well for the same time periods.

@Cedric what I am looking for is an intersection with something like the log entry you sent me on discord.

 

[Cedric]

I’ll see what I can find about job.php later today. Got some work to do first. And as soon as I get back, this will be top priority.

 

[Empire]

Been resolved, I don't ahve any errrs wile bolstering here

 

[Debashis]

I've been receiving the error a couple of times today. First time for me.

 

[Tyrsson]

This thread is getting confusing due to both error codes being referenced in the same thread. A 520 and a 502 are not the same return code.

@Cedric can you split this topic and replies based on response code so we can keep track of them please.

It could also possibly help if the users that are experiencing this will make a note of the exact url and post it in their replies to the relevant topic.

I've been receiving the error a couple of times today. First time for me.

View attachment 1922

@Debashis your errors could be result of server configuration changes. It is being looked into.

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.

 

[SoluDome]

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.

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.

And for 502 error i think that is something for which you should check your server logs for Apache/Ngnix and tune your server to handle more users. Though I have not received these errors again.

Reference: https://support.cpanel.net/hc/en-us/articles/4402673881751-About-502-Bad-Gateway-errors

 

[Debashis]

Hi Team,

I've been coming across this error since yesterday don't know why.
To keep a track on it, I'm creating this topic.

Thanks!

 

[Cedric]

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.

 

[Debashis]

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.

Sure, Cedric! Thanks! Will do.

 

[Debashis]

@Cedric I faced the error message again just now while accessing a conversation.

 

[Cedric]

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.

 

[Alex]

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.

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.

 

[Debashis]

Just got that error again.

 

[Cory]

@Cory could you provide links to those sites please? I want to check and see what http version their site is using.

They happen across the Jcink network, even my own board, but I haven't had it happen in a while now.

@Cory is it possible for you to do the same for your site?

I don't have access to that info.