woob.browser.exceptions.ClientError: 403 Client Error: Forbidden

[GregAce]

I have this new error every time i start the script.
Maybe an issue with 2FA ?

[rbignon]

Hi,

What is the content of ~/.local/share/doctoshotgun/state.json? (you can obfuscate cookies)

Try to remove the file and run doctoshotgun again.

[GregAce]

Hi,
i removed the file, but it's not better.

state.json seems to be populated with the cookies:

{"cookies": "eJwlj1tT...bQvGTjTqWPoLk+9k6N/0dp+IJ2BsH+w5s/urajLmiomtcgbZ03KG0qS8Y6JpY15IfxEQIfTnokXnPX4wvjcEoa7i/gv1RYK+Pn8BcrBToI="}

[rbignon]

Can you run doctoshotgun with -d and paste all the output?

[GregAce]

here is the output :

2021-11-30 11:16:05,776:DEBUG:browser::browsers.py:1056:_load_cookies Reloaded cookies from storage
2021-11-30 11:16:05,786:DEBUG:urllib3.connectionpool::connectionpool.py:971:_new_conn Starting new HTTPS connection (1): www.doctolib.fr:443
2021-11-30 11:16:05,973:DEBUG:urllib3.connectionpool::connectionpool.py:452:_make_request https://www.doctolib.fr:443 "GET /sessions/new HTTP/1.1" 403 None
2021-11-30 11:16:06,021:INFO:browser::browsers.py:369:save_response Response saved to dc0ba7839d3146fea77171cef3631eaf
2021-11-30 11:16:06,023:DEBUG:browser::browsers.py:1095:dump_state Stored cookies into storage
Traceback (most recent call last):
File "G:\Users\Greg\Desktop\Script\doctoshotgun.py", line 908, in
sys.exit(Application().main())
File "G:\Users\Greg\Desktop\Script\doctoshotgun.py", line 726, in main
if not docto.do_login(args.code):
File "G:\Users\Greg\Desktop\Script\doctoshotgun.py", line 278, in do_login
self.open(self.BASEURL + '/sessions/new')
File "G:\Users\Greg\AppData\Local\Programs\Python\Python39\lib\site-packages\woob\browser\browsers.py", line 898, in open
return super(PagesBrowser, self).open(callback=internal_callback, *args, **kwargs)
File "G:\Users\Greg\AppData\Local\Programs\Python\Python39\lib\site-packages\woob\browser\browsers.py", line 790, in open
return super(DomainBrowser, self).open(req, *args, **kwargs)
File "G:\Users\Greg\AppData\Local\Programs\Python\Python39\lib\site-packages\woob\browser\browsers.py", line 531, in open
response = self.session.send(preq,
File "G:\Users\Greg\Desktop\Script\doctoshotgun.py", line 78, in send
return callback(self, resp)
File "G:\Users\Greg\AppData\Local\Programs\Python\Python39\lib\site-packages\woob\browser\browsers.py", line 527, in inner_callback
self.raise_for_status(response)
File "G:\Users\Greg\AppData\Local\Programs\Python\Python39\lib\site-packages\woob\browser\browsers.py", line 560, in raise_for_status
raise ClientError(http_error_msg, response=response)
woob.browser.exceptions.ClientError: 403 Client Error: Forbidden

[GregAce]

when connecting with a new browser on doctolib url, there is a puzzle captcha to access the site.

[rbignon]

wtf

[samuelguesnier]

I get the same error

├╴ Spécifiez votre situation: 1
│ 1 dose de rappel
│ 2 complétion du schéma vaccinal (personnes immunodéprimées uniquement)
├╴ Spécifiez votre situation: 1
An unexpected exception of type ClientError occurred. Arguments:
('403 Client Error: Forbidden',)

[samuelguesnier]

It just worked, maybe the cookie was not valid anymore

[GregAce]

Changing my @ip with a VPN, captcha is no more requested, and the script is working again. So I guess a captcha protection is activated when doing to much requests to doctolib.

[seranpion]

Hello. Commenting even after issue closure.

I am running in the same issue, except that I don't have a VPN at hand.
Removing the state.json cache file does not help.

Strangely, I can successfully log into the same account and use the doctolib web portal with a browser.
I only ran into a captcha verification once (was both using the script and the browser).

I hope this is just a temporary ban, and that the cooldown is not too long.

[rbignon]

Unfortunately I can't reproduce. I guess once you resolved the captcha, a cookie is set to prove you are not a bot.

What kind of captcha is it? If possible the best thing would be to redirect you in the browser when it occurs to let you resolve the captcha by hand, and enter a callback uri or something like that in doctoshotgun.

[GregAce]

I still have the captcha when opening doctolib in a new browser (even in the phone app). The protection seems to be activated on my @ip.
I agree with the workaround you propose.
Here is the captcha :

[GregAce]

Strangely, I can successfully log into the same account and use the doctolib web portal with a browser.
I only ran into a captcha verification once (was both using the script and the browser).

if you open doctolib in a new private browsing window, the captcha will be required each time.