I recently uploaded an image that I had been trying to upload for days now from my computer, but every time it gave me a 502 Bad Gateway error. So today, I uploaded the image through URL, and it worked perfectly.

So let me get this straight: Uploading through URL works fine, but uploading from the computer apparently doesn't. Every time I try to upload from my computer, I get a 502 Bad Gateway. Yet a URL upload works without fail.

Can someone explain the logic of this?? And why is it that I seem to be the only one who has this issue?

I suspect it may have to do with the path, ie C:\Pictures\ねこ\female` may cause problems due to the Japanese text, or \ƒemale` for the stylized F.

Furrin_Gok said:
I suspect it may have to do with the path, ie C:\Pictures\ねこ\female` may cause problems due to the Japanese text, or \ƒemale` for the stylized F.

I'm literally trying to upload from C:/Pictures. I'm not sure what the problem is, and it bugs the hell out of me.

First and foremost, think this is related: forum #193238
So no idea what you gain for making seperate topic about pretty much the same issue.

Furrin_Gok said:
I suspect it may have to do with the path, ie C:\Pictures\ねこ\female\` may cause problems due to the Japanese text, or \ƒemale for the stylized F. [/quote] For some reason I really doubt this, because it's browsers job to take the file from location to send it, only thing actually send is the file itself. And even then, I have send tons of files with japanese, scandinavian and other odd characters in the filename from my computer without issue, because site renames the filename to MD5 hash. Only thing I have bumped is indeed that for some reason file is corrupted in some level, making site unable to get the header information it needs. Because I do know that the site should check for filetype and change it, so that nobody renames jpg to png and gets dimensions of the media. I have two flash files which are impossible to upload here because of that, other ones header I was able to manually fix, but other one may never get here. First I must ask: has that been the only image you have been trying to upload so far? Second, have you compared the MD5 hash of ORIGINAL image to FULL image on the G+ and Facebook? Because I'm looking at that posts history which has both G+ preview image and Facebook preview image as sources. That means both of those images has been resized and altered by those services, meaning if original image was corrupted, then non-corrupted version worked of course. So if the local versions MD5 is not 3AB4E60FFD479D011B3F032D5B91325D, that means it's differend from what you linked earlier, making it impossible to help with that image in particular as that's the file that KiraNoot (hopefully) tested in previous thread. Because in both services you have to click the "download" button to get full images URL, right clicking image to get the address is only for preview. Meaning they are differend image from what you are trying to upload from local computer, so of course they work! And even the download links full image might be completely differend from one in your computer because those sites may compress them to save space.

The easiest way to check if it's corrupted is to open it in an image editor and save it as a new file with a new name, then try uploading that file. I'd try IrfanView for this as well because that thing understands every image and might be more prone to open a corrupted file than your standard image editor.

NotMeNotYou said:
The easiest way to check if it's corrupted is to open it in an image editor and save it as a new file with a new name, then try uploading that file. I'd try IrfanView for this as well because that thing understands every image and might be more prone to open a corrupted file than your standard image editor.

I downloaded Irfanview, opened the image (punkcoon.jpg), and then saved as it as a PNG file labelled "repunkcoon". I tried to upload "repunkcoon.png" and got yet another visit from my good old friend, Error 502.

I don't know what is preventing this image from uploading, and quite frankly, it is starting to really piss me off.

Mario69 said:
First and foremost, think this is related: forum #193238
So no idea what you gain for making seperate topic about pretty much the same issue.

I created a new topic because I had learned that I could upload, however, not directly from my computer, and while I seem to be the only one having this issue, I still wanted help and/or answers.

Okay, small update:

I tried uploading some random artwork from my computer. Worked like a charm.

So I suppose punkcoon.jpg and repunkcoon.png are corrupted somehow.

So How Can I Fix Image Corruption??

and this is a case where keeping all of ones pics, gifs, swfs...and other related stuff all crammed into one main and countless sub folders on the desktop might come in handy.

it's a good thing i'm the only user of this laptop and should anyone else happen to use it, they don't get curious or notice a folder titled 'furry'.

thanks to that, i never have to worry about the directory path when loading (unless the length of said path hits windows limits on occasion. >.>).

regarding the corruption, my best guess would be to open them in an art program then, while said program is still open, delete the original file(s) and simply resave them. though i'm not too sure how well that works since i've very rarely ever had that happen, if at all.

OliCoon said:
Okay, small update:

I tried uploading some random artwork from my computer. Worked like a charm.

So I suppose punkcoon.jpg and repunkcoon.png are corrupted somehow.

So How Can I Fix Image Corruption??

Repunkcoon.png is resaved version of punkcoon.jpg, meaning even if punkcoon.jpg was corrupted, the repunkcoon.png should not be anymore as program saving it had to redo whole header and convert the file into whole another file format.

There's not much that can be done anymore to be frank, one thing you still can do is to give exact times and dates of upload attempts so someone from site can check possible logs created by your attempts, but considering you can't upload recreated file and admin was able to upload it in test enviroment I don't know how much that will help. Also I would start looking if there's something wrong with your computer or internet connection, preventing the file from being uploaded or corrupting the stuff in upload process. I have seen many cases of antivirus software simply preventing stuff without notifying user. Also basics like running malwarebytes if there's something nasty in your browsers configs done by adware.

One thing to counter it as you can download trough URL, is to simply use services whitelisted: https://e621.net/upload_whitelist?limit=90&page=1
So uploading image to dropbox, imgur, etc. account instead and uploading from there then removing the file from the service.

treos said:
regarding the corruption, my best guess would be to open them in an art program then, while said program is still open, delete the original file(s) and simply resave them. though i'm not too sure how well that works since i've very rarely ever had that happen, if at all.

It's pretty rare, because storage devices and internet connections are pretty reliable these days so corruption is pretty rare on something like small image files, but still pretty plausible.
However this was already suggested and done earlier.

Mario69 said:
Repunkcoon.png is resaved version of punkcoon.jpg, meaning even if punkcoon.jpg was corrupted, the repunkcoon.png should not be anymore as program saving it had to redo whole header and convert the file into whole another file format.

There's not much that can be done anymore to be frank, one thing you still can do is to give exact times and dates of upload attempts so someone from site can check possible logs created by your attempts, but considering you can't upload recreated file and admin was able to upload it in test enviroment I don't know how much that will help. Also I would start looking if there's something wrong with your computer or internet connection, preventing the file from being uploaded or corrupting the stuff in upload process. I have seen many cases of antivirus software simply preventing stuff without notifying user. Also basics like running malwarebytes if there's something nasty in your browsers configs done by adware.

One thing to counter it as you can download trough URL, is to simply use services whitelisted: https://e621.net/upload_whitelist?limit=90&page=1
So uploading image to dropbox, imgur, etc. account instead and uploading from there then removing the file from the service.

It's pretty rare, because storage devices and internet connections are pretty reliable these days so corruption is pretty rare on something like small image files, but still pretty plausible.
However this was already suggested and done earlier.

After a three-month-long break, I seem to have pinpointed the problem.

Whenever I try to upload an image through e926, the site crashes.

However, uploading through e621 works just fine.

Not sure why this is, since they are sister sites, but I just tried it. It crashed when I tried to upload through e926, so I switched over to e621 and uploaded through there without fail.

OliCoon said:
After a three-month-long break, I seem to have pinpointed the problem.

Whenever I try to upload an image through e926, the site crashes.

However, uploading through e621 works just fine.

huh. i have had trouble with uploading through e926 too.

so basically i tried to upload two largish images at our school because school has good internet. naturally i picked e926 so chances for random furry dicks on screen would be minimal and it just gave me some error message. i tried again few days later and same message popped up and i just forgot about it. i never tried to upload them at home through e621 because my internet is painfully slow here but im gonna try now.

Mutisija said:
huh. i have had trouble with uploading through e926 too.

so basically i tried to upload two largish images at our school because school has good internet. naturally i picked e926 so chances for random furry dicks on screen would be minimal and it just gave me some error message. i tried again few days later and same message popped up and i just forgot about it. i never tried to upload them at home through e621 because my internet is painfully slow here but im gonna try now.

You could also blacklist -rating:s for a bit and go onto 621. Only difference there is less results per page since the blacklisted ones are hidden, but still count towards the total number on the page.

Furrin_Gok said:
You could also blacklist -rating:s for a bit and go onto 621. Only difference there is less results per page since the blacklisted ones are hidden, but still count towards the total number on the page.

its not same. on e926 i can open nsfw posts but it wont show the images and tells to go view it on e621 instead but i can still browse the comments and stuff. on e621 i could easily get accidentally screen full of furry titties while lurking tickets and records for some delicious drama

but anyways i uploaded the images throught e621 without any problem

Mutisija said:
huh. i have had trouble with uploading through e926 too.

so basically i tried to upload two largish images at our school because school has good internet. naturally i picked e926 so chances for random furry dicks on screen would be minimal and it just gave me some error message. i tried again few days later and same message popped up and i just forgot about it. i never tried to upload them at home through e621 because my internet is painfully slow here but im gonna try now.

Mutisija said:
its not same. on e926 i can open nsfw posts but it wont show the images and tells to go view it on e621 instead but i can still browse the comments and stuff. on e621 i could easily get accidentally screen full of furry titties while lurking tickets and records for some delicious drama

Mutisija said:
but anyways i uploaded the images throught e621 without any problem

Exactly. It seems that uploading through e9 is glitched, and we need to bring this to the administrators' attention.

One thing I do have to note, though. I have an extension on my browser, Google Chrome, by the anti-virus company Webroot. It basically lets you know how dangerous a website is, yknow, the probability of being exposed to malicious links and other risks.

It labels e621 as having little to no risks, yet e926 is labelled as fairly risky, despite them practically being the same site.

I can verify that e621 cannot upload special characters or parse Japanese text, when uploading the nikukyu art I had to save everything under a Japanese name and rename it to an English filename before uploading.

GDelscribe said:
I can verify that e621 cannot upload special characters or parse Japanese text, when uploading the nikukyu art I had to save everything under a Japanese name and rename it to an English filename before uploading.

My filenames are entirely in English text, Roman lettering.

OliCoon said:
My filenames are entirely in English text, Roman lettering.

same here. it had nothing to do with name since it went through e621 without problem and only e926 was not able to post it. there is something wrong with e926

GDelscribe said:
I can verify that e621 cannot upload special characters or parse Japanese text, when uploading the nikukyu art I had to save everything under a Japanese name and rename it to an English filename before uploading.

My latest upload had scandinavian letters in it and not too long ago uploaded stuff with kanji just fine.

And the problem has been already pinpointed to e9.

Mario69 said:
My latest upload had scandinavian letters in it and not too long ago uploaded stuff with kanji just fine.

And the problem has been already pinpointed to e9.

How long ago was it pinpointed, and why isn't it fixed?

OliCoon said:
How long ago was it pinpointed, and why isn't it fixed?

Well, you pinpointed it. And it's not fixed because this isn't an official bug report. Fill out the bug report with correct bug report table and someone higher up gets on it.

Mario69 said:
Well, you pinpointed it. And it's not fixed because this isn't an official bug report. Fill out the bug report with correct bug report table and someone higher up gets on it.

Alright, the report's been filled out. Hopefully someone will fix it.