Please change the default theme from "winter" to "none". I ate all the cookies.

Images routinely fail to load on my browser. Everything else on the page is normal, but no image. Not even any evidence an image was supposed to be there; no broken icon, no big empty space.

where the image should be is a seemingly random set of the image's tags. Immediately below that is the Edit / Respond / Download/ Full Size bar, and the comments below that.

If I click on the download button, it brings me to a gray-ish screen that displays the image's URL, saying it can't be opened because it contains errors.

This happens seemingly at random. Im using the latest version of Firefox, but this has been happening for some time now.

MintMint said:
Images routinely fail to load on my browser. Everything else on the page is normal, but no image. Not even any evidence an image was supposed to be there; no broken icon, no big empty space.

where the image should be is a seemingly random set of the image's tags. Immediately below that is the Edit / Respond / Download/ Full Size bar, and the comments below that.

If I click on the download button, it brings me to a gray-ish screen that displays the image's URL, saying it can't be opened because it contains errors.

This happens seemingly at random. Im using the latest version of Firefox, but this has been happening for some time now.

Something similar happens to me. Bigger images very often are not loading and there's either black image, or just tags displayed. Restarting firefox or changing browser to IE makes them open correctly. It seems that it's firefox problem because it also happens on other sites (like rule34.paheal)

@Granberia @MintMint - I used to get this bug all the time, or at least it was similar. Happened in Firefox and I think I also had it happen in another browser if it was used for long enough in a browsing session (not sure though, it's been awhile). Just like you said, things would browse fine for awhile, and then at some seemingly random point it would start refusing to load medium large images and up. (sometimes it would happen pretty quickly after the browser session was started; other times it would be awhile before it stopping wanting to load a percentage of the images clicked on). I remember that no amount of clearing cache etc would make it start behaving again. But that clearing both cache and cookies would temporarily fix it, but only for a few page loads before it would act up again. However, it was too much of a pain and too temporary of a fix to deal with re-logging back in all the time. Restarting the browser would get things back to normal with images loading again fine. Until at some random point (sometimes sooner, sometimes later) it would stop loading some of the images again, and I'd have to close the browser and re-open it again to get things working again. It was very frustrating and I never could figure out what the problem was or how to fix it.

So I tried other browsers just to use for this site. IE doesn't seem to have any problems loading images consistently (though I think it had issues loading WebM format?). But IE is crap in so many other ways though, so I only used it for this site for a couple months.

Now I use Opera for browsing e621, which doesn't seem to have the loading bug that firefox develops after some browsing. On Opera you can browse as much as you want and it will load everything without problems no matter how many images you look at. The only issue Opera seems to have in my experience, is that sometimes it balks a little bit sooner when trying to view a percentage of the superabsurd_res size images. But that is in fact part of why we have that tag: not every browser/computer/hardware combination can handle those without choking on it. Strangely enough, sometimes a superabsurd_res image that Opera gives me an error for, another browser will be able to handle. So I guess no one browser does it all.

So, unless someone knows how to fix the problem with sustained browsing e621 in firefox, using another browser (like Opera or IE) for e621 is a pretty successful workaround. Though if someone knows how to fix that issue in firefox I'm all ears, because I love to keep my options open and not have to segregate my browsing by browser. lol

Granberia said:
Something similar happens to me. Bigger images very often are not loading and there's either black image, or just tags displayed. Restarting firefox or changing browser to IE makes them open correctly. It seems that it's firefox problem because it also happens on other sites (like rule34.paheal)

Install eSix Extend (forum #66904) and enable 'Apply the "HTTP Tweak" on every image'. Fixed the problem for me.

Munkelzahn said:
Install eSix Extend (forum #66904) and enable 'Apply the "HTTP Tweak" on every image'. Fixed the problem for me.

I have eSix Extend, so I've just tried this option and there are still some pics that on IE displays like this while on FF like this.
Though this image doesn't load properly on FF even after restarting it so maybe this option in eSix helps in some other cases.

https://e621.net/post/index/1/chartags:%3C1%20towergirls
https://e621.net/post/index/1/chartags:0%20towergirls
https://e621.net/post/index/1/towergirls%20chartags:0

char type metatag broken in above examples

Search will turn up:
post #483599 (0 char tags, for now)
post #482883 (1 char tag)

I'm getting

NoMethodError in PostController#create
undefined method []' for nil:NilClass [/quote] when trying to upload a pic. Judging by the fact that no pic was uploaded since 8 hours I guess I'm not alone with this problem.

Been getting the same error or a 500 error when uploading. Guess it'll be a while on that...

I can't upload anything and the site always gets crashed on my site with the dump message ---, or sometimes it ends up on a bad gateway on the cloudfare overlay.

It seems like everyone is having the same problem.

Just_Another_Dragon said:
I can't upload anything and the site always gets crashed on my site with the dump message ---, or sometimes it ends up on a bad gateway on the cloudfare overlay.

It seems like everyone is having the same problem.

How much you willing to bet we're all getting Ddos'ed?

Just_Another_Dragon said:
I can't upload anything and the site always gets crashed on my site with the dump message ---, or sometimes it ends up on a bad gateway on the cloudfare overlay.

It seems like everyone is having the same problem.

Yea...odd thing is it only seems to affect uploading. I can still navigate the site easily enough.

Just_Another_Dragon said:
I can't upload anything and the site always gets crashed on my site with the dump message ---, or sometimes it ends up on a bad gateway on the cloudfare overlay.

It seems like everyone is having the same problem.

Same here.

Uploading was fixed late last night.

TonyLemur said:
Uploading was fixed late last night.

I'm still getting this:

NoMethodError in PostController#create

undefined method []' for nil:NilClass I suppose I should take a day or two off from uploading images. I can still work on other things for the time being (tagging).

GameManiac said:
I'm still getting this:

NoMethodError in PostController#create

undefined method []' for nil:NilClass I suppose I should take a day or two off from uploading images. I can still work on other things for the time being (tagging).[/quote] It was temporarily fixed, but is still an ongoing issue. So a more permanent solution to keep it from reoccurring is scheduled for later today/tomorrow. It will involve some downtime as the servers are worked on, and will be announced in the news banner when we know more about exactly when that will be happening. So thanks for letting us know, as feedback for how it's holding in there until it gets fixed. Hopefully it will be back to fully functioning again in the next day or two. *fingers crossed that it all goes according to plan*

furrypickle said:
It was temporarily fixed, but is still an ongoing issue. So a more permanent solution to keep it from reoccurring is scheduled for later today/tomorrow. It will involve some downtime as the servers are worked on, and will be announced in the news banner when we know more about exactly when that will be happening. So thanks for letting us know, as feedback for how it's holding in there until it gets fixed. Hopefully it will be back to fully functioning again in the next day or two. *fingers crossed that it all goes according to plan*

Awesome. I'll just wait and go over my To-Do (upload) list.

reading a lot of stuff here, and maybe some of you know what THIS means.. it keeps show up when i try to upload something.

*edit: message above this one says enough. :P

arttags:0 is broken (again)

that's why people should use unknown_artist

After the recent outage flagging a post is no longer working.
Every time I've tried it it has resulted in the "error" page.

Peekaboo said:
After the recent outage flagging a post is no longer working.
Every time I've tried it it has resulted in the "error" page.

You can still flag posts that have a parent.
(must be set before you flag the post)
I've only tried this with the "duplicate or inferior version" option, though.

Tag subscriptions bugs:

https://e621.net/user/show/33842

I have:

Artists 1
Artists 2
Artists 3 (empty)
Characters
Long Tail

What's displayed is:

Artists 1 = Artists 1
Artists 2 = (nothing)
Artists 3 = Characters
Characters = Long Tail
Long Tail = (nothing)

Index error?

Currently E926 isn't working properly. Accessing without https will cause it to redirect to E621 and with https you get a certificate error and explicit results.

furrypickle said:
So, unless someone knows how to fix the problem with sustained browsing e621 in firefox, using another browser (like Opera or IE) for e621 is a pretty successful workaround. Though if someone knows how to fix that issue in firefox I'm all ears, because I love to keep my options open and not have to segregate my browsing by browser. lol

I don't have that problem with Firefox. I know I've seen it before, but it's been a long time since then. I assume Ctrl + F5 does not help. Some things I have that affect how websites load:

HTTPS Everywhere (may have been disabled for e621???)
NoScript (whitelist e621.net only... I can export and upload my config somewhere if you want it)
Ghostery (unlikely)
uBlock (probably not)
MVPS HOSTS (very unlikely)
browser.cache.disk.enable;false
browser.cache.memory.capacity;-1
browser.cache.memory.enable;true
content.interrupt.parsing;true
content.notify.interval;300000
content.notify.ontimer;true
nglayout.initialpaint.delay;0
(I don't think pipelining or max connection tweaks matter)
Accept third-party cookies = never
Keep cookies until = they expire
Always browse e621 in a private window, but keep e621.net cookies (css, _cfduid, e621, mode (at present))
e621 user settings, enable = Resize images, Show image samples

Other than that, a lack of any other non-default settings and extensions might also correct the issue, so try fooling around in a clean Firefox profile. You'll note that I do not have eSix Extend. Then there's networking crap that probably isn't feasible for you to fix. You can also poke around in Firefox's developer tools; check samples from before and after the issue occurs; see if something suddenly "broke", throws an error, or stops loading; maybe try comparing against the dev tools in other browsers or downloading custom troubleshooting extensions/plugins if you're going hardcore ;). But I've only recently taken an interest in that route for troubleshooting and I'm not too proficient on what everything specifically means, so I can't offer targeted instructions or advice.

M3W said:
Currently E926 isn't working properly. Accessing without https will cause it to redirect to E621 and with https you get a certificate error and explicit results.

I sent an email to Dave and they are aware of the issue and it should be fixed fairly soon.

In the meantime, if you want a partial workaround (it unfortunately won't help with explicit ads) I'd recommend putting this in your blacklist:

rating:explicit

rating:questionable

And checking this box directly underneath it:

[x] Apply blacklist to avatars

I'm using iOS. e926 is not functioning properly. It just started working identically to e621. Everything but the URL is exactly the same. Posting anything results in me being on e621, not that there's any difference.

Bug:the url e926.net automatically redirects to https://e621.net[/b]

ignore this comment

When flagging a post for deletion, putting the parent posts ID in the "This post is a repost" field still causes a crash.
It is possible to edit the to-be-deleted posts parent post in the normal edit menu and then flag it, but I thought you guys should know that this bug is still in effect.

I think there's a problem with the Blips system when on iOS.

I'm using Chrome and I think when pressing the "Go Back" button on the same tab you used for posting a blip would "repost" the blip again, causing multiple blips of the same message to be posted again.

I don't know if this is just me or is a bug.

parasprite said:
I sent an email to Dave and they are aware of the issue and it should be fixed fairly soon.

In the meantime, if you want a partial workaround (it unfortunately won't help with explicit ads) I'd recommend putting this in your blacklist:

rating:explicit

rating:questionable

And checking this box directly underneath it:

[x] Apply blacklist to avatars

Sadly, the reason I link to e926 is not related to MY personal account but the fact that I link people to the page that do not share my account. This bug defeats the purpose of linking to it.

M3W said:
Sadly, the reason I link to e926 is not related to MY personal account but the fact that I link people to the page that do not share my account. This bug defeats the purpose of linking to it.

I just ran a few tests and it looks like everything is now working as expected including not showing explicit ads, so it looks like it's been fixed.

It should be good to go, but let me know if you are still having issues.

Okay i can't browse freely roght now, because everytime i try to click on one of the images it always says "error 1003, direct ip access not allpwed" is something messed up or am i blocked or what. I can't even see most of these images,

Bug: -pool:0000 and -pool:name aren't working as expected
Expected behavior: -pool:0000 and -pool:name will exclude the pool from search results
Actual behavior: -pool:0000 and -pool:name will be included in search results. They also have the tendency to be duplicated 1-2 times, although I haven't been able to figure out what conditions make some give 2 duplicates (3 posts) while others only have 1 (2 posts).

The blacklist works as expected, but the number of results blacklisted doesn't account for the duplicates (e.g., 3 duplicates will only count as 1 blacklisted in the sidebar).

It's worth noting that trying to add -pool:0000 as a tag to remove it doesn't work. If done from the post page it results in a "NoMethodError in PostController#update" error and may be related to this issue.

Steps to duplicate:

blip said:

female x-ray femdom cum_in_pussy -pool:5639
female x-ray femdom cum_in_pussy -pool:testpool

The results are identical. Again, the output includes no exclusion and duplicate posts.

it doesn't look like aliases/implications are affecting these results.

Related discussion: forum #154527

Edit: This affects sets as well.

RocketSeason101 said:
Okay i can't browse freely roght now, because everytime i try to click on one of the images it always says "error 1003, direct ip access not allpwed" is something messed up or am i blocked or what. I can't even see most of these images,

This may be caused by a few different things. Potentially anything that affects the network and particularly DNS in any way (such as your ISP, software on your computer, DNS settings, proxies, network conditions, issues specific to cloudflare, etc.) may be affecting this.

Edit: If you happen to be using Dolphin browser on an Android phone/tablet, disable "Dolphin Jetpack" in the settings menu and see if the issue persists. Otherwise ignore this step.

• Do you experience this on any other websistes that you know of?
• How long has this been happening?
• Does this still happen if you restart your computer?
• Any recent upgrades, software updates, change in internet, a new modem, etc.?
• Do you know how to change the DNS settings for your computer/device? If not, what OS do you run? (Windows 8.1, OS X, Android, etc.)

Peekaboo said:
When flagging a post for deletion, putting the parent posts ID in the "This post is a repost" field still causes a crash.
It is possible to edit the to-be-deleted posts parent post in the normal edit menu and then flag it, but I thought you guys should know that this bug is still in effect.

I don't get it. But I have the same problem.

I am not able to flag any post.

Any time I try I get this error: http://i.imgur.com/rFD8soY.png

Sneaky said:
I am not able to flag any post.

Any time I try I get this error: http://i.imgur.com/rFD8soY.png

Adding the post number to the FFD screen is currently broken. The only way around that is to parent the post first, then flag it (you'll know you did it right because the post number will be automatically added to the FFD screen).

I discussed this with Dave and they are aware of the issue.

Oh, and I saw you were trying to flag post #616375 in favor of the larger post #620006, so I went ahead and deleted that.

parasprite said:
Adding the post number to the FFD screen is currently broken. The only way around that is to parent the post first, then flag it (you'll know you did it right because the post number will be automatically added to the FFD screen).

I discussed this with Dave and they are aware of the issue.

Oh, and I saw you were trying to flag post #616375 in favor of the larger post #620006, so I went ahead and deleted that.

Alright thanks, I'll try to remember to do that.

RocketSeason101 said:
Okay i can't browse freely roght now, because everytime i try to click on one of the images it always says "error 1003, direct ip access not allpwed" is something messed up or am i blocked or what. I can't even see most of these images,

This is also happening to me.

But only on the Dolphin Browser on Android.

Only reason I use it is Chrome dropped Flash support.

Wadxxx said:
This is also happening to me.

But only on the Dolphin Browser on Android.

Only reason I use it is Chrome dropped Flash support.

From NotMeNotYou:

There is a workaround, disable "Dolphin Jetpack" in the options, that will allow the images to load normally, but may increase page load slightly.

Okay, so I don't know if this is a bug or a fluke, but I had several tabs open and when I clicked on one of them, my account had been signed out. I didn't click the logout button and signing back in was a simple one-click thing, but still.

JoeX said:
Okay, so I don't know if this is a bug or a fluke, but I had several tabs open and when I clicked on one of them, my account had been signed out. I didn't click the logout button and signing back in was a simple one-click thing, but still.

• Were any of them in private browsing/incognito-type mode?
• Did you close the browser at one point and restore the tabs (session saving)?
• What browser are you using? Any addons?

parasprite said:

• Were any of them in private browsing/incognito-type mode?
• Did you close the browser at one point and restore the tabs (session saving)?
• What browser are you using? Any addons?

1. No
2. No
3. Internet Explorer, no addons

JoeX said:
1. No
2. No
3. Internet Explorer, no addons

Internet Explorer can be kinda wonky like that because of how it handles cookies. It's gotten better but apparently it's still not completely fixed (or at least reasonably similar to other browsers). If you ever find it to be a nuisance you can use the following workaround (detailed below), otherwise don't worry about it.

Workaround:

• Tools -> Options
• Click the Privacy tab and then Advanced
• From there enable override automatic cookie handling and then enable always allow session cookies at the bottom
• Click okay and restart browser

parasprite said:
Internet Explorer can be kinda wonky like that because of how it handles cookies. It's gotten better but apparently it's still not completely fixed (or at least reasonably similar to other browsers). If you ever find it to be a nuisance you can use the following workaround (detailed below), otherwise don't worry about it.

Workaround:

• Tools -> Options
• Click the Privacy tab and then Advanced
• From there enable override automatic cookie handling and then enable always allow session cookies at the bottom
• Click okay and restart browser

Thanks! I'll keep this in mind!

Bug: The client side blacklist is not applied to comments when comments below threshold is enabled. Note that this applies to user avatars that were not necessarily blacklisted themselves just activating the function on a page causes none of the avatars to be blacklisted.

Expected behavior: Blacklisting should apply to avatars when the "Apply blacklist to avatars" setting is enabled.

Actual behavior: When comments below threshold on a page is enabled nothing is blacklisted.

Steps to duplicate: With "Apply blacklist to avatars" enabled on a post with some comments below threshold and at least one user avatar invoking the blacklist, enable comments below threshold.

I get physically sick when I see gore so a fix for this would be really appreciated.

It seems the reason for this is because the blacklist is applied on page load and readded comments are applied as is without checking the blacklist.

This might not be a bug, but..
Searching for *: used to be handy for finding stray category tags (artist:, character: etc) with a single search. But now it finds tons of posts, and I can't figure out what it is matching.

Genjar said:
This might not be a bug, but..
Searching for *: used to be handy for finding stray category tags (artist:, character: etc) with a single search. But now it finds tons of posts, and I can't figure out what it is matching.

Maybe tags that were reverted with general:?

Genjar said:
This might not be a bug, but..
Searching for *: used to be handy for finding stray category tags (artist:, character: etc) with a single search. But now it finds tons of posts, and I can't figure out what it is matching.

*: -d:

parasprite said:
*: -d:

Well... Now it works.
But when I tried that earlier, it got about 800 pages of hits.

vvv Urgh. So many useless tags left on deleted posts. I think I'll clean that up a bit...

parasprite said:
*: -d:

Take your pick.

EsalRider said:
Take your pick.]

:character:kalahari:

http://i.imgur.com/aRWxhTT.jpg

mrnotsosafeforwork said:
Bug: adding -humor or -humour to blacklists blacklists ALL THE POSTS!

Expected behavior: tags with humor are exempt from blacklist

Actual behavior: literally every single post gets blacklisted

Steps to duplicate: add -humor to blacklist

Adding "-humor" to blacklist blacklists everything WITH0UT THE humor tag. What you want is to blacklist "humor". No dash.

Correct me if it doesn't work.

Is there a reason I'm getting this message...

"ActiveRecord::StatementInvalid in PostController#flag"

...when I'm trying to flag an image?

I've stumbled across a couple of images through my search of the final_fantasy tag that I feel should be flagged for deletion, because their inferior duplicates of newer posts.

GameManiac said:
Is there a reason I'm getting this message...

"ActiveRecord::StatementInvalid in PostController#flag"

...when I'm trying to flag an image?

I've stumbled across a couple of images through my search of the final_fantasy tag that I feel should be flagged for deletion, because their inferior duplicates of newer posts.

You need to edit in the parent id before you can flag. The problem is being worked on, iirc.

edidaf said:
You need to edit in the parent id before you can flag. The problem is being worked on, iirc.

I've been informed that there is a fix ready for this and it'll be pushed with the next update.

I don't have an official timeframe or anything, but my guess is within the next week or so. Either way, Tony will leave a comment in the Site Changelog whenever it does.

Bug: sending tickets goes twice on mobile (ios)Expected behavior: creating a ticket happens onceActual behavior: it creates it twice Steps to duplicate: i tried to change my name on my ipod 4, it succeeded, but there is now 2 exact copies of my ticket.note:this also happened when posting this comment

edit: its a bug on the os/app im using...

it still happening : [

Bug:the error 1003 still happen.

Expected behavior:Browse e621 funny

Actual behavior:Got Cloudflare error 1003

Steps to duplicate:Open it with Dolphin Browser (with Jetpack)

so what happen about cloudflare, can we know it?

I know disable Jetpack can fix that shit, but I think so many user hope can Browse it without any function need to disable.

Hope it can be fix.

If no, please tell us, any reason....... I will stop asking about that.

DOD said:
it still happening : [

Bug:the error 1003 still happen.

Expected behavior:Browse e621 funny

Actual behavior:Got Cloudflare error 1003

Steps to duplicate:Open it with Dolphin Browser (with Jetpack)

so what happen about cloudflare, can we know it?

I know disable Jetpack can fix that shit, but I think so many user hope can Browse it without any function need to disable.

Hope it can be fix.

If no, please tell us, any reason....... I will stop asking about that.

I don't want to sound like I am placing the blame on the developers of Jetpack, but there isn't much we can do about it. I'll tell you why, but I need to explain something first.

Dolphin uses a browser engine called WebKit (a browser engine is basically a complex bunch of stuff that is needed to render a webpage). WebKit is also used in a number of other browsers such as Safari, Chrome*, and Opera*. WebKit is also built into Android/iOS/OS X so that any browser can use all or only parts of it to render websites (after all, there's no need to reinvent the wheel if you don't have to). Using the built-in version also means that you, as a browser developer, can assume that the parts of WebKit installed on a Samsung S5 will be designed to run on a Samsung S5.

Jetpack however, is an addon that replaces pieces of WebKit with newer, custom versions designed with speed in mind. While this may improve performance in some cases, it can also cause bugs that other browsers don't have, or only with certain devices. The developers know that Jetpack still has bugs that need to be fixed and this is one of the reasons why it can be turned off. After all, if there were no drawbacks to using Jetpack, why would they include an option to turn it off?

I don't know the details about this specific error or why it is happening (possibly related to security? I'm not sure), but long story short, Jetpack doesn't play well with a lot of websites (including websites that use CloudFlare like this one). It's possible that CloudFlare might be able to fix something on their end, but it's more likely that it is Jetpack itself that is causing the issues and anything CloudFlare might be able to fix would really just be a workaround for buggy software.

*Side note: Technically, Chrome and Opera actually use an engine called "Blink", which is based off of Webkit. But for our purposes here it might as well be the same thing.

TLDR: Jetpack may improve performance but it's still buggy. There isn't much we can do on our end but wait for the Dolphin developers (and/or CloudFlare) to fix it.

parasprite said:
I don't want to sound like I am placing the blame on the developers of Jetpack, but there isn't much we can do about it. I'll tell you why, but I need to explain something first.

Dolphin uses a browser engine called WebKit (a browser engine is basically a complex bunch of stuff that is needed to render a webpage). WebKit is also used in a number of other browsers such as Safari, Chrome*, and Opera*. WebKit is also built into Android/iOS/OS X so that any browser can use all or only parts of it to render websites (after all, there's no need to reinvent the wheel if you don't have to). Using the built-in version also means that you, as a browser developer, can assume that the parts of WebKit installed on a Samsung S5 will be designed to run on a Samsung S5.

Jetpack however, is an addon that replaces pieces of WebKit with newer, custom versions designed with speed in mind. While this may improve performance in some cases, it can also cause bugs that other browsers don't have, or only with certain devices. The developers know that Jetpack still has bugs that need to be fixed and this is one of the reasons why it can be turned off. After all, if there were no drawbacks to using Jetpack, why would they include an option to turn it off?

I don't know the details about this specific error or why it is happening (possibly related to security? I'm not sure), but long story short, Jetpack doesn't play well with a lot of websites (including websites that use CloudFlare like this one). It's possible that CloudFlare might be able to fix something on their end, but it's more likely that it is Jetpack itself that is causing the issues and anything CloudFlare might be able to fix would really just be a workaround for buggy software.

*Side note: Technically, Chrome and Opera actually use an engine called "Blink", which is based off of Webkit. But for our purposes here it might as well be the same thing.

TLDR: Jetpack may improve performance but it's still buggy. There isn't much we can do on our end but wait for the Dolphin developers (and/or CloudFlare) to fix it.

thank for your respond
and I apology about my question and my bad english(I thought it make us have a little Misunderstand).
thanks again you let me know the issue
uh ... and have a nice weekend and I apology for my question again

the upload page gives me the Redis::CannotConnectError in PostController#upload error.
Completely screwed.

Peekaboo said:
the upload page gives me the Redis::CannotConnectError in PostController#upload error.
Completely screwed.

They are aware of the issue and are working for a fix. Post uploads and deletions are the main thing that are affected right now, but the rest of the site is mostly unaffected. As far as I've been able to figure out, there are no known workarounds, but I'll let you know if I find anything new.

Additional discussion: forum #156170

I can't upload images. Every time I try to, I get this:

Redis::CommandError in PostController#upload

ERR Client sent AUTH, but no password is set

RAILS_ROOT: /home/e621/e621-production/release-2014-06-08

Application Trace | Framework Trace | Full Trace
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:97:in call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:80:in connect'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:257:in with_reconnect' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:78:in connect'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:304:in ensure_connected' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:191:in process'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:270:in logging' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:190:in process'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:96:in call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:784:in get'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:37:in synchronize' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/1.8/monitor.rb:242:in mon_synchronize'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:37:in synchronize' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:783:in get'
/home/e621/e621-production/release-2014-06-08/app/models/post.rb:73:in disable_upload?' /home/e621/e621-production/release-2014-06-08/app/controllers/post_controller.rb:23:in upload'

BadAnon said:
I can't upload images. Every time I try to, I get this:

Redis::CommandError in PostController#upload

ERR Client sent AUTH, but no password is set

RAILS_ROOT: /home/e621/e621-production/release-2014-06-08

Application Trace | Framework Trace | Full Trace
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:97:in call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:80:in connect'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:257:in with_reconnect' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:78:in connect'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:304:in ensure_connected' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:191:in process'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:270:in logging' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:190:in process'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:96:in call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:784:in get'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:37:in synchronize' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/1.8/monitor.rb:242:in mon_synchronize'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:37:in synchronize' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:783:in get'
/home/e621/e621-production/release-2014-06-08/app/models/post.rb:73:in disable_upload?' /home/e621/e621-production/release-2014-06-08/app/controllers/post_controller.rb:23:in upload'

Wait, I didn't read the previous posts. Sorry.

I'm getting a bug with the image_resize_mode thing...

Drflash55 said:
I'm getting a bug with the image_resize_mode thing...

This is what it shows...

NoMethodError in Post#show

Showing app/views/post/show_partials/_status_notices.html.erb where line #1 raised:

undefined method image_resize_mode' for #<User:0x8e0da50> Extracted source (around line #1): 1: <% if ([email protected]_deleted? || current_user.is_janitor_or_higher?) && @post.use_sample?(current_user) && @post.can_be_seen_by?(current_user) %> 2: <div class="status-notice" style="display: none;" id="resized_notice"> 3: This image is displayed at <%= number_to_percentage @post.sample_percentage, :precision => 0 %> of its original size. <%= link_to_function "View original", "Post.highres()" %> 4: <% unless current_user.is_anonymous? || CONFIG["force_image_samples"] %> Trace of template inclusion: app/views/post/show.html.erb RAILS_ROOT: /home/e621/e621-production/release-2014-06-08 Application Trace | Framework Trace | Full Trace /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/attribute_methods.rb:275:in method_missing'
/home/e621/e621-production/release-2014-06-08/app/models/post/file_methods.rb:311:in use_sample?' /home/e621/e621-production/release-2014-06-08/app/views/post/show_partials/_status_notices.html.erb:1:in _run_erb_app47views47post47show_partials47_status_notices46html46erb_locals_object_status_notices'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/renderable.rb:34:in send' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/renderable.rb:34:in render'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/base.rb:306:in with_template' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/renderable.rb:30:in render'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/renderable_partial.rb:20:in render' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:30:in benchmark'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/renderable_partial.rb:19:in render' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/template.rb:205:in render_template'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/renderable_partial.rb:44:in render_partial' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/partials.rb:184:in render_partial'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/base.rb:267:in render' /home/e621/e621-production/release-2014-06-08/app/views/post/show.html.erb:5:in _run_erb_app47views47post47show46html46erb'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/renderable.rb:34:in send' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/renderable.rb:34:in render'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/base.rb:306:in with_template' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/renderable.rb:30:in render'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/template.rb:205:in render_template' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/base.rb:265:in render'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/base.rb:348:in _render_with_layout' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_view/base.rb:262:in render'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:1252:in render_for_file' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:936:in render_without_benchmark'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:51:in render' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/1.8/benchmark.rb:308:in realtime' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:51:in render' /home/e621/e621-production/release-2014-06-08/app/controllers/post_controller.rb:629:in show'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/mime_responds.rb:135:in call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/mime_responds.rb:135:in custom'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/mime_responds.rb:179:in call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/mime_responds.rb:179:in respond'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/mime_responds.rb:173:in each' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/mime_responds.rb:173:in respond'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/mime_responds.rb:107:in respond_to' /home/e621/e621-production/release-2014-06-08/app/controllers/post_controller.rb:624:in show'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in send' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in perform_action_without_filters'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/filters.rb:617:in call_filters' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/filters.rb:610:in perform_action_without_benchmark'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/1.8/benchmark.rb:308:in realtime' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/rescue.rb:160:in perform_action_without_flash'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/flash.rb:151:in perform_action' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in process_without_filters' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/filters.rb:606:in process'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:391:in process' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:386:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/routing/route_set.rb:438:in call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:87:in dispatch'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:121:in _call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:130:in build_middleware_stack'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:29:in call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:29:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in cache' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:9:in cache'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:28:in call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/string_coercion.rb:25:in call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/head.rb:9:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/methodoverride.rb:24:in call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/params_parser.rb:15:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/session/cookie_store.rb:99:in call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/cache/strategy/local_cache.rb:25:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/failsafe.rb:26:in call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/lock.rb:11:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/lock.rb:11:in synchronize' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/lock.rb:11:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:106:in call' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/urlmap.rb:47:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/urlmap.rb:41:in each' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/urlmap.rb:41:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/rack/thread_handler_extension.rb:61:in process_request' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler/thread_handler.rb:126:in accept_and_process_next_request'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler/thread_handler.rb:94:in main_loop' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler.rb:463:in start_threads'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler.rb:457:in initialize' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler.rb:457 Request Parameters: {"id"=>"630447"} Show session dump Response Headers: {"Cache-Control"=>"no-cache", "Set-Cookie"=>"blacklisted_tags=urine&peeing&fart&human&scat&penetration&sex_toy&pussy_juice&sex&masturbation&doggystyle&after_sex&cum&penis; path=/\nblacklist_avatars=true; path=/\nblacklist_users=true; path=/", "Content-Type"=>"text/html"}[/section] [/quote] Yea me to, and worst of all, it happens with every image

mrasly said:
Yea me to, and worst of all, it happens with every image

same here! even older ones that were uploaded before it started. i think its a server problem.

mrasly said:
Yea me to, and worst of all, it happens with every image

Drflash55 said:
I'm getting a bug with the image_resize_mode thing...

This is what it shows...

snip

They were just pushing some updates, but everything should be working now.

Same here. Ippiki tripped over the mainframe again! (Just kidding) :P

parasprite said:
They were just pushing some updates, but everything should be working now.

Yeah its working now :P

Bug: Tags in blacklist aren't blacklisted (chrome/flashfox for android)
Expected behavior: Posts with tags in blacklist are blacklisted
Actual behavior: Posts with tags in blacklist show.
Steps to duplicate:
Use either chrome or flashfox
Have tags in blacklist
Search for blacklisted tag OR browse normally. Please note I have only used these two browsers so it is entirely possible this bug occurs in other browsers.

Receiving an action controller error when viewing posts in e926...

While maybe not a bug report, I have been wondering how the site handles simultaneous tagging by different users (e.g. two users adding/removing different tags at the same time). I've heard that there have been some issues with this (e.g. by furrypickle and by NotMeNotYou in news 20150212) and I'm curious about what the status is concerning these issues?

I've currently been keeping my eyes on my tag history but due to aliases (e.g. gay -> male/male, straight -> male/female, oral_sex -> sex, etc.) it looks like I'm removing tags from every other post which makes it a little cumbersome (and boring) to keep track of changes. I generally try to follow my golden rule of less than three minutes between post request and tag update. Currently the only hurt I've stumbled across has been self inflicted. How much I should worry?