Danbooru 2 Issues Topic

Yeah, for whatever reason, it's got you with a member-level API permissions... This'll have to be investigated, since your levels should match mine...

Edit:

For kuuderes_shadow, just FYI, every time you use the Tag Script, even if it fails, counts as a write. That's why it doesn't stop at 2700 and is instead somewhere below it.

@evazion @kuuderes_shadow @albert @Type-kun

I believe the error here occurs because of the following bit of code in the users model. If a user doesn't have an API key, it defaults to 300.

def api_hourly_limit(idempotent = true)
  base = if is_platinum? && api_key.present?
    2000
  elsif is_gold? && api_key.present?
    1000
  else
    300
end

For kuuderes_shadow, a short-term solution would be to go to your profile page and use the Generate Key for the API Key (under subscriptions). Once it gets created, it should revert your API levels back to what they should be.

Beat me to it! I just realized that too.

g3gen said:

Ok, don't have a problem using Hijiribe or Sonohara since the certificate mismatch isn't a problem.

Seems those subdomains are slow loading as well. Since other image boards are moving along on my 6 Mbps connection, I think that rules out anything on my end, unless it is my ISP. I'll have to wait for it to somehow get resolved.

I did not have to wait long. Thanks to the Danbooru admins, my #1 image board is running smooth and fast.

g3gen

Get permanent Failboorus when I try uploading from Danbooru and Danbooru and Sonohara are very slow. Hijiribe works fine, though.

Yeah, I noticed the same...

Pinging all three seems okay, occasional packet losses aside. Last time, only sonohara was working. Wonder what's going on.

Edit: Main Danbooru server is now working for me for some reason.

Safebooru is also going slowly.

Sonohara, Danbooru, and Safebooru are going slowly. Hijiribe is the one that works fine.

http://sonohara.donmai.us and http://hijiribe.donmai.us are the two real servers. danbooru.donmai.us just chooses randomly between the two. Also Sonohara seems back up as of a few moments ago.

Might be better now? I am seeing a lot of traffic from Googlebot and other web crawlers so they may be the cause. I noticed 1-2 nginx processes were getting most of the excess traffic so I've increased the worker count for now.

Just noticed that collection pool titles aren't automatically updated after an artist is aliased to a new name, perhaps someone could conjure up a script to check?
Example: pool #11396

Hmm... wouldn't recommend making this as an automated update function as part of aliases updating though since Pool titles, including the artist qualifier, aren't necessarily standardized.

Also, in addition to the titles, the pool descriptions need to be checked as well for Artist links to update.

Any idea what is broken(?) right now.
Sonohara and Hijiribe are moving very slow.

Provence said:

Any idea what is broken(?) right now.
Sonohara and Hijiribe are moving very slow.

This feels a bit like a DOS attack as there appears to be more requests than normal, and it only began about 22 hours ago with a few respites here and there b

I haven't experienced any slowdown in the last few days, though I'm not here 24/7.

Same here, ( in Britain ).

It was going crazily slowly for an hour or so up until shortly after Provence made the post. I haven't had any issues since then, although I've not been on here much in the time since either.

Am I the only one here that experiences error on bookmarklet? It always failed to upload the preview image.

What are you trying to upload? Post a link.

I have problems with the bookmarklet from Nicoseiga:
I did always work perfectly, so I don't know why it does this all over a sudden.
If I take this link, I get an "about:blank" and therefore no image anymore
http://lohas.nicoseiga.jp/o/441961b870f7c4ed366fb1a340b0598ff1bdbd7c/1477776958/6214896
If I take this link, it works perfect:
http://seiga.nicovideo.jp/seiga/im6214896

Like I said, earlier both links worked for the bookmarklet.
But this isn't everything: I just tried it again and this time, both links did work. So I'm a bit confused, since the error apparantly isn't in the system. But I don't know why it sometimes works and sometimes not.