-
-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
403 error even when using capsolver #180
Comments
+1 |
Got this Error
[12/26/2024 4:17:13] Texas Scheduler v5.0.0 is starting... 403 ForbiddenMicrosoft-Azure-Application-Gateway/v2 |
It just works again for me . |
[12/26/2024 10:14:59] Captcha token received successfully 403 ForbiddenMicrosoft-Azure-Application-Gateway/v2 { |
okay ill keep trying |
started working for me with no changes aswell. |
sometime capsolver didnt get confident score high enough. I got that issue too |
I am also getting this error. I am not using the paid solution. I am trying to use the manual token. I still have to put this part like this. "Browser" isn't working. @phamleduy04 |
@TracyZhou619 where are you running this? Github codespaces or localhost? |
Oh i know what you mean now, will fix on next release |
Github codespace @phamleduy04 |
Github codespace isn't supported broswer mode as mentioned on the wiki |
Just comment out switch case for |
I am doing the manual token way - getting the token every 15/20 minutes from the website inspection manually. This method has worked in Github codespace before. But I had to put strategy: solver and solver service: capslover to make it work before. |
How do I fix this 403 error if I would like to use Github codespace and the manual token way? |
You can try delete your codespace and create a new one to get a new IP. If you spam too much api requests the DPS will "ban" your IP temporarily. |
|
@buddyluvisin are you using capsolver? |
It might be the capsolver dont get high enough score. You can try to contact them |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
I took the credits in Capsolver and followed the steps mentioned but I am getting the below error
<title>403 Forbidden</title>ERROR:
403 Forbidden
Microsoft-Azure-Application-Gateway/v2
The text was updated successfully, but these errors were encountered: