Unable to post Let's Play update

[Omicron]

Hello. I am Omicron and I write Let's Play Every Final Fantasy Game In Order Of Release.

I am currently unable to post my next update. Doing so causes me to receive the message: "Oops! We ran into some problems. Please try again later. More error details may be in the browser console." (I don't know how to parse the 'browser console' so these extra details would be useless to me.)

I normally post updates with 50 pictures. In the past, I've had to deal with being unable to post because I had more than 50 pictures, and at times, my subscriber privileges temporarily lapsed, reducing me to no more than 20 pictures. Accordingly, I've attempted to post 49, 20, and 18 pictures. Every time, the same error message shows up. I am able to make a post with 4 or 5 pictures in it; however, around 7 or 8, I get the error message and can no longer post.

Additionally, the Save function of the reply box appears to break when I attempt to save my draft, and do not recognize any changes until I delete the entire draft and Save a draft with fewer than a handful of pictures.

This is making it impossible for me to update and I would like some understanding of the issue that is occurring.

 

[CmptrWz]

For anyone else reading the thread, I've been given access to things via other channels to take a look.

Using that, I was able to test the post myself and determine that CloudFlare has an issue with the content, and I don't know what that issue actually is.

I don't have enough access to CloudFlare (as in I don't have any) to see what the actual problem is, assuming they'll tell us. I did get a Ray ID though: 9372ce940d304375

@Xon probably needs to take a look on that front.

 

[Xon]

@Omicron I've disabled the clouldflare setting which had been accidently turned on which appears to be causing this

 

[Omicron]

Thank you, it works now!

 

[DanZapman]

(I don't know how to parse the 'browser console' so these extra details would be useless to me.)

Click to shrink...

In case this is useful for you or anyone else reading this thread in the future, you can usually access this by pressing F12 on Firefox, by right-clicking and clicking Inspect Element, or by pressing Ctrl-Shift-J (Command-Option-J for Mac) on Chrome, and possibly switching tabs from inspector to console. Screenshotting that is often helpful, if only for narrowing things down.