Skip to content
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

[BUG] Rate limited and 403 status code error #189

Open
mdabdulmusavvir opened this issue Jan 11, 2025 · 16 comments
Open

[BUG] Rate limited and 403 status code error #189

mdabdulmusavvir opened this issue Jan 11, 2025 · 16 comments
Assignees

Comments

@mdabdulmusavvir
Copy link

@mdabdulmusavvir ➜ /workspaces/texas-dps-scheduler (main) $ npm run start

texas-dps-scheduler@5.0.2 start
ts-node --transpile-only src/index.ts

[01/11/2025 1:19:03] Texas Scheduler v5.0.2 is starting...
[01/11/2025 1:19:03] Requesting Available Location....
[01/11/2025 1:19:04] Waiting for captcha token from task fd7b431e-8699-40f0-9600-d97d0d722f21...
[01/11/2025 1:19:06] Captcha token received successfully
[01/11/2025 1:19:07] WARNING -> Got 403 status code
[01/11/2025 1:19:07] Endpoint: /api/Auth
[01/11/2025 1:19:07] ERROR:

<title>403 Forbidden</title>

403 Forbidden


Microsoft-Azure-Application-Gateway/v2

{
'Content-Type': 'application/json;charset=UTF-8',
Origin: 'https://public.txdpsscheduler.com',
Referer: 'https://public.txdpsscheduler.com'
}
[01/11/2025 1:19:07] WARNING -> Got rate limited, sleep for 10s...
[01/11/2025 1:19:17] WARNING -> Got 403 status code

Copy link

@mdabdulmusavvir
Copy link
Author

I am using codespace, bought Capsolver, yesterday it was working great but it failed with the above error and it is happening frequently.

@Chill7Times
Copy link

I am having the same issue

@phamleduy04
Copy link
Owner

let me test and let you guys know

@phamleduy04
Copy link
Owner

i can't reproduce error.

But I got a lot of headers timeout error that means the offical scheduler api is unstable.

image

@Chill7Times
Copy link

I was able to get it resolved by running the program locally in Visual Studio. > i can't reproduce error.

But I got a lot of headers timeout error that means the offical scheduler api is unstable.

image

@cmosguy
Copy link

cmosguy commented Jan 13, 2025

@phamleduy04 i am seeing this:

image

i also paid for the capsolver, so not sure what is going on.

@cmosguy
Copy link

cmosguy commented Jan 13, 2025

@phamleduy04 confirmed that it only happens on the codespaces, when I ran locally it worked just fine.

Thanks so much for donating your time to this project, it saved me a friggin ton of time 🔥

@Sreeharsha397
Copy link

How did you run this locally on vscode?

@cmosguy
Copy link

cmosguy commented Jan 16, 2025

How did you run this locally on vscode?

@Sreeharsha397 you have to have a linux/window system and do the npm install locally on your computer. I would suggest to read the install locally section in the wiki install locally

@SufBit
Copy link

SufBit commented Jan 17, 2025

Image

Happened twice when found an appointment, seems to be a problem with the api/HoldSlot endpoint

@phamleduy04
Copy link
Owner

@SufBit what strategy are you using

@SufBit
Copy link

SufBit commented Jan 21, 2025

@phamleduy04 Running it locally

@phamleduy04
Copy link
Owner

will be fix on next release

@ice4prince
Copy link

I have the same issue.
I would like to know when trying to run locally, what dependencies I should install after clone the repo?

Ensure you installed [node.js](https://nodejs.org/en/) on your computer.
Clone the repo
Install dependencies
Copy example.config.yml to config.yml and edit it to your preference.
npm install
npm run start

@phamleduy04
Copy link
Owner

I have the same issue. I would like to know when trying to run locally, what dependencies I should install after clone the repo?

Ensure you installed [node.js](https://nodejs.org/en/) on your computer.
Clone the repo
Install dependencies
Copy example.config.yml to config.yml and edit it to your preference.
npm install
npm run start

Have you tried the latest release?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants