NASASpaceflight.com and NSF Forum Bug Reports

[catdlr]

Error 502's continue.

Yeah, I gave up counting. At one point during a 30-minute period an hour ago, it was almost every 5 screens. I was doing a bunch of updates. It's enough to throw my PC down the fire escape. And to top it off, it's slow.

[catdlr]

Error 502's continue.

Yeah, I gave up counting. At one point during a 30-minute period an hour ago, it was almost every 5 screens. I was doing a bunch of updates. It's enough to throw my PC down the fire escape. And to top it off, it's slow.

And I got a 502 posting above.  Gee

Cloudflare Ray ID: 9be9cf04dd5397ca

[catdlr]

Error 502's continue.

Yeah, I gave up counting. At one point during a 30-minute period an hour ago, it was almost every 5 screens. I was doing a bunch of updates. It's enough to throw my PC down the fire escape. And to top it off, it's slow.

And I got a 502 posting above.  Gee

Cloudflare Ray ID: 9be9cf04dd5397ca

and it did it again:   Cloudflare Ray ID: 9be9d0967ab097ca

[russianhalo117]

Error 502's continue.

Error 502's continue.

Yeah, I gave up counting. At one point during a 30-minute period an hour ago, it was almost every 5 screens. I was doing a bunch of updates. It's enough to throw my PC down the fire escape. And to top it off, it's slow.

And I got a 502 posting above.  Gee

Cloudflare Ray ID: 9be9cf04dd5397ca

and it did it again:   Cloudflare Ray ID: 9be9d0967ab097ca

I cant even reliably edit schedules right now.

[zubenelgenubi]

Error 502's continue.

Error 502's continue.

Yeah, I gave up counting. At one point during a 30-minute period an hour ago, it was almost every 5 screens. I was doing a bunch of updates. It's enough to throw my PC down the fire escape. And to top it off, it's slow.

And I got a 502 posting above.  Gee

Cloudflare Ray ID: 9be9cf04dd5397ca

and it did it again:   Cloudflare Ray ID: 9be9d0967ab097ca

I cant even reliably edit schedules right now.

Yes, it's happened while working on one of Salo's schedules.

[Chris Bergin]

Sorry guys, it's going to be a pain for a bit longer. Mark says he will deploy a fix over the weekend.

[Chris Bergin]

Per the issue noted in the recent posts, fix is in place. Give it 24 hours. Again, you can get the occasional bad gateway (like those five mins early in the morning UTC).

Thanks for your patience!

[StraumliBlight]

There appears to be an attachment issue, where images are not displayed.

[  Tony adding - Including Rdale in L2 and several others in the public thread that I saw having the same issue starting yesterday ]

[catdlr]

There appears to be an attachment issue, where images are not displayed.

[  Tony adding - Including Rdale in L2 and several others in the public thread that I saw having the same issue starting yesterday ]

and that now includes me.  That will keep me from posting live coverage screengrabs of any launches

https://forum.nasaspaceflight.com/index.php?topic=51175.msg2754343#msg2754343

[Yellowstone10]

Seeing the same bug - the forum post seems to know the image is there and the size it's supposed to be, but when you click the link to download, it's a 0-byte file.

[russianhalo117]

Seeing the same bug - the forum post seems to know the image is there and the size it's supposed to be, but when you click the link to download, it's a 0-byte file.

Indeed. I'm seeing the same behaviour. It appears to be public side, potentially posting privileges dependant (basic member versus administrator privileges dependant) or is timestamp dependant and not all threads appear to be affected by the problem.

[catdlr]

There appears to be an attachment issue, where images are not displayed.

[  Tony adding - Including Rdale in L2 and several others in the public thread that I saw having the same issue starting yesterday ]

That appears to have been resolved. I don't know who. If you have been holding back on posting, go ahead. If you posted previously, you need to return to your post, delete the attachment, and reattach a fresh copy.

[Chris Bergin]

Ah yes sorry. I didn't know it affected older ones, I noticed it with a few new ones and Mark fixed it. So all will be good now (issue would have been hours between me noticing and Mark fixing. Didn't know anyone had noticed as I didn't know it affected older ones too )