how do I check my key?

[Rowkahh]

how do I check my key?

Web retrieval of check key failed!

[maxi344]

i have the same problem y i cant find the solution, any one know what to do?

[GetarnteKadse]

you can get key by going to fansly main page under Network, search for key, look out for snippet.js and under that there should be request URL on the top which contains the key.

[swiftypaws]

I have the same problem and do not see a snippet.js

[GetarnteKadse]

Here is what i did:
i opened Dev tools and typed "key" in the search bar under network
then i went to fansly and there was a entry that started with "snippet.js?key="

or maybe just search for key and look for a section that contains a few "-"

[dgtlabs]

This is what worked for me to fix this on the latest v0.9.7.

Based on the error message saying to check for "this.checkKey" in the main.js of the fansly homepage, I first logged out and back in (may or may not be relevant), then press F12, go to the Sources tab, then look for Top>fansly.com>main.[somevalue].js (I imagine the [somevalue] will be different for everyone).

Once the main.js is displayed, press Ctrl+F and enter "this.checkKey" and look for a statement that says something along the lines of this.checkKey_ = ["value1", "value2"].reverse().join("-") + "-value3", where value1, 2, and 3 are the different segments of your check key.

Looking at my old check key and my rough guess at what this statement evaluates to, I determined that it reverses value1 and value2, and then adds value3 to the end, so I changed my check key to "value2-value1-value3".

I was able to continue with that value without any further auth errors and have had no issues scrapping 4 accounts so far.

I'm no expert on this but in the config.ini the check_key_pattern logic is set to "this.checkKey_\s*=\s*"'["']", which I think may need to be changed from what I found, because I'm not sure that pattern would match the statement I found in the main.js, but I'm not familiar with how the search patterns work so I'm not sure what to set it to and I could be wrong about this.

Be sure to also check for a new authorization_token if you relogged at the beginning like me, as it changes. Hope this helps.

[prof79]

@dgtlabs Thanks a lot for your efforts. Please all see #34 all relevant info is there.

In short:

• snippet-something has nothing to do with it,
• you do not need to guess but can just copy-paste "["value1", "value2"].reverse().join("-") + "-value3"" in Console in dev tools and it will spit out the correct key in the clear :-) (but omit the double quotes)
• the pattern (code) may change in the future - worst part would be Fansly totally scrambling it/changing the logic/putting it elsewhere

[InformalMoose]

@dgtlabs big props, this fixed my issue. i appreciate it, thank you.

[Valour549]

I have followed the above instructions very carefully, and obtained the check_key from the console (it looks something like oybZy8-fySzis-bubayf) and then pasted it into the correct section of the config.ini, along with my authorization_token and user_agent

Nevertheless, every time I open the exe, it still says "Web retrieval of check key failed!" and tells me to check the checkKey expression is correct. Could you kindly point me in the right direction?

[ZOMGsheikh]

I have followed the above instructions very carefully, and obtained the check_key from the console (it looks something like oybZy8-fySzis-bubayf) and then pasted it into the correct section of the config.ini, along with my authorization_token and user_agent

Nevertheless, every time I open the exe, it still says "Web retrieval of check key failed!" and tells me to check the checkKey expression is correct. Could you kindly point me in the right direction?

Were you able to solve this?

[Valour549]

Were you able to solve this?
No.

[ZOMGsheikh]

Were you able to solve this?
No.

Got it WORKING!!!!!!

so was doing this first over a Linux system, but there were some ffmpeg issues, so I switched to Windows, using the Binary (.exe) version v0.9.7, for my ease of use, i went with 0.9.7 as 0.9.9 ( latest) was not even downloading images but this did over linux, so that is why I went with older ver. but you can try latest in Windows too. Once your config. is prepared, replacing the auth and user agent, then there is check key which you must be entering. Along with entering the correct value, at bottom, you need to change the syntax of check_key_pattern to: check_key_pattern = this\.checkKey_\s*=(\s*(\+?\[[^\]]+\]|\.[a-z]+\([^\)]*\)|\+?\"[^\"]*\")+\s*)+(?=,)

Make sure to confirm your auth token and user agent again with updated values, save and run.

[Alexo88]

He seguido las instrucciones anteriores con mucho cuidado y obtuve la check_key de la consola (parece algo como oybZy8-fySzis-bubayf) y luego la pegué en la sección correcta del config.ini, junto con mi authorization_token y user_agent.

Sin embargo, cada vez que abro el archivo ejecutable, sigue apareciendo el mensaje "¡Error en la recuperación web de la clave de verificación!" y me indica que compruebe que la expresión checkKey sea correcta. ¿Podría indicarme la dirección correcta?

yo lo use en este orden y me funciono mas o menos.

check_key = fySzis-oybZy8-bubayf

[Jetanroth]

This is what worked for me to fix this on the latest v0.9.7.

Based on the error message saying to check for "this.checkKey" in the main.js of the fansly homepage, I first logged out and back in (may or may not be relevant), then press F12, go to the Sources tab, then look for Top>fansly.com>main.[somevalue].js (I imagine the [somevalue] will be different for everyone).

Once the main.js is displayed, press Ctrl+F and enter "this.checkKey" and look for a statement that says something along the lines of this.checkKey_ = ["value1", "value2"].reverse().join("-") + "-value3", where value1, 2, and 3 are the different segments of your check key.

Looking at my old check key and my rough guess at what this statement evaluates to, I determined that it reverses value1 and value2, and then adds value3 to the end, so I changed my check key to "value2-value1-value3".

I was able to continue with that value without any further auth errors and have had no issues scrapping 4 accounts so far.

I'm no expert on this but in the config.ini the check_key_pattern logic is set to "this.checkKey_\s*=\s*"'["']", which I think may need to be changed from what I found, because I'm not sure that pattern would match the statement I found in the main.js, but I'm not familiar with how the search patterns work so I'm not sure what to set it to and I could be wrong about this.

Be sure to also check for a new authorization_token if you relogged at the beginning like me, as it changes. Hope this helps.

I was able to get the check key with your instructions but I still get this error: