phamleduy04 / texas-dps-scheduler

Texas DPS/DMV Automatic Scheduler
MIT License
281 stars 128 forks source link

ERROR 403 #142

Closed SSPlusUltra closed 3 months ago

SSPlusUltra commented 3 months ago

config yml - texas-dps-scheduler - Visual Studio Code  Administrator  29-07-2024 09_48_12 (1)

I think its getting blocked when its trying to book the appointment after finding it. So it works till it finds the appointment and then we get this error

rickmania382 commented 3 months ago

Fails after 3 attempts. It was a good run bois. Thanks captain Duy Pham Le!

SSPlusUltra commented 3 months ago

@rickmania382 I just got an appointment lol, still works but cant go as long as before

thitganuong commented 3 months ago

I run just a little bit and got the same error, retry but not work

Shahomie commented 3 months ago

I'm also getting the same error

phamleduy04 commented 3 months ago

are you using v3.1.0?

Shahomie commented 3 months ago

are you using v3.1.0?

Yes, I ran the git pull, npm install, and npm update commands. After doing so, I ran npm run start. The code will run for a few seconds and then the error will keep coming up until it stops all together after 3 times.

SharvaParalkar commented 3 months ago

image

same thing happening, using 3.1.0

phamleduy04 commented 3 months ago

i got that error randomly, sometimes the request passing got stuck with 403

rickmania382 commented 3 months ago

FYI. The app has no issues with booking the appointment once found. It is not hitting "/api/AvailableLocation" after three attempts. Yesterday's update did something.

phamleduy04 commented 3 months ago

The error like @SSPlusUltra got I think that he got IP banned, try to use a VPN to see if it works.

phamleduy04 commented 3 months ago

@rickmania382 ty. I think they implement some kind of rate limit

rickmania382 commented 3 months ago

Yeah. Now, we just gotta find a workaround. Leave that to me, boss.

SharvaParalkar commented 3 months ago

increased interval from 10000 to 30000 it's running for longer now and hasn't stopped working yet

phamleduy04 commented 3 months ago

just implement some kind of workaround for the rate limit. Will need to find permanent fix

zerowebcorp commented 3 months ago

DPS web team is getting smarter.

Shahomie commented 3 months ago

Yea, I just did a git pull for 3.1.1, currently getting the 403 status error and got rate limited image

Shahomie commented 3 months ago

DPS web team is getting smarter.

Instead making things harder for people, they should start hiring more and fix the backlog of months of no appointment

Shahomie commented 3 months ago

I was able to get an appointment even though the error codes are coming up image

sumanthdaruvuri commented 3 months ago

@Shahomie Garland Mega Center doesn't even come on my location list despite me putting it's zipcode.

I narrowed down the filters to one location, same day and I am not getting rate limited now. But that also narrows down my chances of getting an appointment

AryanPillai2007 commented 3 months ago

@phamleduy04 thank you so much for your help, I managed to get a spot! CleanShot 2024-07-29 at 12 46 51@2x

phamleduy04 commented 3 months ago

great to see the app work again :). Will try to find a fix for those rate limit, maybe better queue management something

thitganuong commented 3 months ago

I think this error happened when you scan over 2 persons/request in the same time.

AsadMoulviDev commented 3 months ago

Hey, I keep getting rate-limited has anyone tried with a VPN ?

itsmateen commented 3 months ago

Hey anyone getting the following error since morning.

[07/31/2024 1:35:40] Requesting Available Location.... /home/runner/texas-dps-scheduler/src/Client/index.ts:152 log.error(No Available location found! Nearest location is ${response[0].Distance} miles away! Please change your config and try again!); ^ TypeError: Cannot read properties of undefined (reading 'Distance') at TexasScheduler.requestAvailableLocation (/home/runner/texas-dps-scheduler/src/Client/index.ts:152:87) at processTicksAndRejections (node:internal/process/task_queues:95:5) at async TexasScheduler.run (/home/runner/texas-dps-scheduler/src/Client/index.ts:63:9)

itsmateen commented 3 months ago

Hey, I keep getting rate-limited has anyone tried with a VPN ?

Untill last night it was working good with me even without VPN

Tvu239 commented 3 months ago

I keep getting 403 status code and rate limit now and I cant even log into the website anymore. Screenshot 2024-07-31 084953

itsmateen commented 3 months ago

I keep getting 403 status code and rate limit now and I cant even log into the website anymore. Screenshot 2024-07-31 084953

yea they have implemented the IP banned soo give it 5 mins and try again it would work. i tried this way and it worked with me

Tvu239 commented 3 months ago

I keep getting 403 status code and rate limit now and I cant even log into the website anymore. Screenshot 2024-07-31 084953

yea they have implemented the IP banned soo give it 5 mins and try again it would work. i tried this way and it worked with me

Its been like this since yesterday, should I give it more time or am I cooked

itsmateen commented 3 months ago

No you are good just give sometime

santiago-brent commented 3 months ago

I am also getting rate-limited 403 errors, VPN results in same thing. Did we get caught? XD

aphyio commented 3 months ago

still getting rate limited 403 errors, vpn aswell does nothing

shahvaibhavutd commented 3 months ago

I tried running raw request via Postman and that looks to be working fine, just fyi

santiago-brent commented 3 months ago

I tried running raw request via Postman and that looks to be working fine, just fyi

Could you walk us through the setup process? Sorry, I'm a hardware guy.

shahvaibhavutd commented 3 months ago

@santiago-brent It very manual process where you have to make every single request one at a time, I wouldn't recommend it since this solution works well (given when your IP is not perm banned).

phamleduy04 commented 3 months ago

track this issue at #156