Credentials getting banned super fast

[eborges-git]

the code that reproduces this issue or a replay of the bug

Apparently there was an update on MJ's side and my credentials are getting banned super fast.

It used to last around 3000 generations and 2 weeks, now it's getting banned in less than 24 hours with 10 generations only.

(I'm already using separate proxies & websockets, cards, time of the day, etc)

So I was wondering if this could be related to the lack of headers on the API call.

If we run /imagine straight on the browser, like a real human, the Header has: accept, accept-language, authorization, content-type, origin, referer, sec..., user-agent, x....

But this script only uses autorization and content-type, right?

Describe the bug

error log

[njho]

+1

[codert-tanjingyu]

the code that reproduces this issue or a replay of the bug

Apparently there was an update on MJ's side and my credentials are getting banned super fast.

It used to last around 3000 generations and 2 weeks, now it's getting banned in less than 24 hours with 10 generations only.

(I'm already using separate proxies & websockets, cards, time of the day, etc)

So I was wondering if this could be related to the lack of headers on the API call.

If we run /imagine straight on the browser, like a real human, the Header has: accept, accept-language, authorization, content-type, origin, referer, sec..., user-agent, x....

But this script only uses autorization and content-type, right?

Describe the bug

error log

I have also encountered the same problem and question. Have you found a solution?

[morganfuchs]

Do you think Midjourney analyses requests made on Discord?