Bug overview description.
Basically, attempting to upload through e926 will redirect you to a "bad gateway" error. This does not seem to apply for e621, however.

What part(s) of the site page(s) are affected?
e926 uploading.

What is the expected behavior?
Images should upload onto e926 without problems.

What actual behavior is given instead?
However, the site redirects to a "bad gateway" error, stating that the error is coming from e926.net.

Time of incident (if applicable)
This has been happening since at least three months ago

Can you reproduce the bug every time?
I can easily reproduce the error once again. This occurs every time I attempt to upload on e926.

What steps did you take to replicate this bug?
Go to the "Upload" section of e9, put in the image and the necessary details, and then click "submit". It will show a loading wheel, as if working to get to a new page, before redirecting to an error 502 "bad gateway" message.

Errors or other messages returned (if any)
This is a link to a video containing unedited footage of one of these error messages, filmed this morning: https://youtu.be/UZwQh7dIOFs

_{*Is about to suggest a direct template to fill in to prevent members from not including the template in their posts*}

Isn't a gateway error something temporary and/or user-related?

Hudson said:
_{*Is about to suggest a direct template to fill in to prevent members from not including the template in their posts*}

Isn't a gateway error something temporary and/or user-related?

502s aren't user-related. If clearing a browser cache and retrying and/or trying another browser isn't helping anything, then it isn't related to the user at all. 502s come from server communication errors (one server receiving an invalid response from another), not really so much what the person behind the screen is doing.

Hudson said:
_{*Is about to suggest a direct template to fill in to prevent members from not including the template in their posts*}

Isn't a gateway error something temporary and/or user-related?

This problem showed up about three months ago and is still active. I wouldn't exactly call that temporary.

Ratte said:
502s aren't user-related. If clearing a browser cache and retrying and/or trying another browser isn't helping anything, then it isn't related to the user at all. 502s come from server communication errors (one server receiving an invalid response from another), not really so much what the person behind the screen is doing.

And once again, e621 doesn't seem to have this problem, it only seems to occur on e926.

Another thing I'd like to note; I have a browser addon that informs you of which websites are risky. It lists e621 as completely trustworthy, yet lists e926 as having moderate risk.

Unsure if that is related, but it's just something else I found curious.

I'm not a dev so I can't help you much here, but please make sure your post follows the bug template.

OliCoon said:
This problem showed up about three months ago and is still active. I wouldn't exactly call that temporary.

I didn't say it was, I assumed it was.

_{Then again I'm not very techical...}

I'm not sure 100% what is going on here. I'm adding some additional logging to the uploading code and will see about deploying it over onto e926 here soon.

I have resolved the issue with uploading on e926.net.