KJHJason / Cultured-Downloader

A project to automate the process of downloading images and other attachment files from platforms like Fantia and more!
GNU General Public License v3.0
72 stars 7 forks source link

[Bug]: "FANBOX Cookie Not Found" or "Invalid" #271

Open teward opened 3 months ago

teward commented 3 months ago

Which program are you seeing this problem on?

Cultured Downloader (Windows Binary)

Program Version

5.1.0

Operating System

Windows 11 x64

What error code did you receive? (If any)

N/A

Steps to reproduce the bug

  1. Use instructions to obtain pixiv fanbox cookies in JSON or TXT file.
  2. Attempt to upload to the PIXIV FANBOX cookie section.
  3. Hard error about "Cookie not found".

Alternative reproduction

  1. Use INSPECT tool in Dev Tools to find the FANBOXSESSID cookie and copy the value into the box and hit "save".
  2. "Cookie not valid" response is received instantly.

Expected behaviour

The FANBOXSESSID cookie value would be detected in the JSON or TXT output from the local save.

OR

The value would be accepted as it's copied verbatim from Firefox

Relevant log output (If any)

No response

Screenshots (Optional)

No response

KJHJason commented 3 months ago

Works on my end, you could be detected as a bot or have a bad IP reputation #259

I'm currently working on adding a cf solver that usually works unless you have a bad IP reputation.

teward commented 1 month ago

Unfortunately there's no way to determine if we're detected as a bot (I'm a user of a static business grade connection).

You may want to also consider including a cf_clearance cookie option per site (including pixiv fanbox) because the CF passing cookie seems to be stored and available as well.

teward commented 1 month ago

@KJHJason actually, I think there's some changes on the Pixiv side that block things. What I'm seeing on other mechanisms is 403s.

Can't tell but https://github.com/hareku/fanbox-dl/issues/39#issuecomment-2201607424 suggests there's problems in the actual auth part and not just because of CF but because non-JP IPs are enforced. I can't debug/sniff what your client does though...