Yeah, we are still working through it. 
I’m still getting them today off and on.
Same here. Let me know if I can do anything to assist besides note that it’s happening 
Oh good, I’m getting this 502 “Bad Gateway” error as well. For me, I only noticed it when I switched from my old XP machine using Chrome to access the site, to my “new” WIn7 machine where I now use IE11. I post a reply, it appears straight away in the thread on the screen, but the status line says “Saving”. After a while I get the Bad Gateway error, so I click “No” or whatever to get rid. My comment re-appears as if I was editing it, so I click “abandon”. When I go back to the forum list my comment is there.
I was thinking it was my machine, so it’s good to know that it isn’t. Makes posting a bit of a pain though.
2 Likes
Oh, I’d also like to point out again, the link in the article to the forums to make a reply is broken. I had to go searching for this thread to make a reply.
And because it is getting on my nerves, the reply bug is also very annoying too. It is amazing it is taking so long for a “Ruby Team” to fix this. That was one of the reasons why you moved to Discourse, isn’t it? (Yes, I am rubbing your noses in it, purposely. It shouldn’t be that when I am trying to make a decent post, then I am confronted with such bugs on a professional website like Sitepoint!)
Once someone on the team, who can actually make a difference, has read this, it can be deleted. Or push it up to someone who can. This bug is terrible, because it not only gives me the error, it also mixes up my responses, because Discourse “thinks” I didn’t enter the post, when I post quickly in other threads. A real PITA.
Scott
Unfortunately, it isn’t a Ruby problem It is a conflict we are experiencing and that’s about as much detail as I’ll go into at this moment. We have the dev team working on it, it isn’t an easy fix and is requiring a lot of time.
1 Like
Yeah, I was thinking it is probably more a Javascript issue. Sorry for the poke in the side. Still, this is something one can expect from OSS and why upgrades of such software need to be sandboxed and tested thoroughly, before they are “let loose on the public”. 
Edit: From what I can see, it happens when the polling routine kicks for the autosave function.
If you’d like, please merge this conversation to a new thread or add it to any thread already existing. I am sure others have complained about the issue.
Scott
From what they have said before, nothing like this showed during their vigorous testing. This is pretty glaring flaw and their tests would have easily shown this problem.
It wasn’t until the upgrade in the production environment that this happened.
1 Like
@s_molinari, just wanted to let you know that I did merge it with an existing topic.
You are correct. Which is why your post should actually be saved, then the 502 occurs, but it fails to clear the editor (or notify the editor that the save was successful).
It has nothing to do with Discourse (the core code), so unfortunately we can’t blame them 
And we did. Our staging environment didn’t have this issue when the staff (forum staff) were doing their testing. Once the issue was present on Production, I was able to reproduce a few of the issues on Staging, but not all of them. Hence why it is taking a while to fix. It isn’t a glaringly obvious issue.
Be rest assured, we’re taking action to help mitigate this future going.
1 Like
Oh. Doh!
Ok. Well, then I would just like to suggest, put some coffee and pizza in front of the devs and tell them they can have it, once the problem is fixed. LOL!
I also wonder what can be so different between the live and test systems, that this issue only pops up in the live system.
Scott
I like how you think!
1 Like
Give them some options. I’m sure a few devs out there would prefer churros.
3 Likes
Not sure this has anything to do with this issue, but there is also a serious issue with timing and post order. This image should explain.
Needless to say, I was thinking “What the heck is going on here?” when I read those posts.
Scott
Can you post a link to that topic?
Tom double posted in there too.
That’s not an error of any kind. If you check the “edit history” (the pencil icon next to the timestamp on Tom’s post), you’ll see he edited his original post to include a quote from Michael’s subsequent reply.
Definitely odd behaviour, but not on the part of the forum software.
2 Likes
Um, so the 4h time showing is based on an edit and he edited his whole post to be an answer to Michael’s post below it? That is strange.
Scott
No, the 4 hour is when he originally made his post. (Or was; obviously it’s changed now. ) You can see the actual times of both the post and the edit by hovering over the timestamp and the edit icon.
And, as I say, if you click on the edit icon, you can see what changes were made to the post.
2 Likes
I just got a 502 error now as well. I cancelled and refreshed and it had posted anyway.
Yes, it is a pain… But in my particular case, it happens when I post from the office. Same with quoting… At the office I have so much problems to quote someone… but at home, I can do it.
So I suspect that office proxies and firewalls have lots to do with my issues Well, I do not suspect it… I’m sure