0 free - 0 reserved

[danwie]

Not sure why this is happening. But after a while I get "0 free - 0 reserved" all the time. No error message.

[20:58:04] [verbose]    Sthlm City (2022-05-02) 0 free - 0 reserved
[20:58:04] [verbose]    Nacka (2022-04-04) 0 free - 0 reserved
[20:58:04] [verbose]    Norrtälje (2022-05-16) 0 free - 0 reserved
[20:58:04] [verbose]    Järva (2022-04-04) 0 free - 0 reserved
[20:58:05] [verbose]    Sthlm City (2022-05-09) 0 free - 0 reserved
[20:58:05] [verbose]    Nacka (2022-04-11) 0 free - 0 reserved
[20:58:05] [verbose]    Nacka (2022-03-28) 0 free - 0 reserved
[20:58:05] [verbose]    Järva (2022-04-11) 0 free - 0 reserved
[20:58:06] [verbose]    Sthlm City (2022-05-16) 0 free - 0 reserved
[20:58:06] [verbose]    Nacka (2022-04-18) 0 free - 0 reserved
[20:58:06] [verbose]    Nacka (2022-04-04) 0 free - 0 reserved
[20:58:06] [verbose]    Järva (2022-04-18) 0 free - 0 reserved
[20:58:06] [verbose]    Flemingsberg (2022-03-28) 0 free - 0 reserved
[20:58:06] [verbose]    Nacka (2022-04-25) 0 free - 0 reserved
[20:58:06] [verbose]    Nacka (2022-04-11) 0 free - 0 reserved
[20:58:07] [verbose]    Järva (2022-04-25) 0 free - 0 reserved
[20:58:07] [verbose]    Flemingsberg (2022-04-04) 0 free - 0 reserved
[20:58:07] [verbose]    Nacka (2022-05-02) 0 free - 0 reserved
[20:58:07] [verbose]    Nacka (2022-04-18) 0 free - 0 reserved
[20:58:07] [verbose]    Järva (2022-05-02) 0 free - 0 reserved
[20:58:07] [verbose]    Flemingsberg (2022-04-11) 0 free - 0 reserved
[20:58:07] [verbose]    Nacka (2022-05-09) 0 free - 0 reserved
[20:58:08] [verbose]    Nacka (2022-04-25) 0 free - 0 reserved
[20:58:08] [verbose]    Järva (2022-05-09) 0 free - 0 reserved
[20:58:08] [verbose]    Flemingsberg (2022-04-18) 0 free - 0 reserved

[kalkih]

Since you seem to be running multiple sessions and all seem to have the same issue, you could be temporarily IP blocked, wait a bit and try to play around with a higher throttle setting.

[raukisola]

I get the same "0 free - 0 reserved". If I alter the lastdate to 2023-01-01 I still get 0 free but when I check manually there is free slots in november. Could it be IP blocking?

[geekteq]

I get the same "0 free - 0 reserved". If I alter the lastdate to 2023-01-01 I still get 0 free but when I check manually there is free slots in november. Could it be IP blocking?

Yes. I get the same. switch IP (VPN) and run again - no issues anymore..

[MartinHage]

I still seem to get this "0 free - 0 reserved" with a VPN since the last pr.

[qubanga]

Also getting the same behaviour with latest release - 3.3.1 solved socket hang up error but getting "0 free - 0 reserved" with no errors in the log. This happens directly after CAPTCHA input.

PS C:\temp> .\passport-appointment-bot-win-x64.exe [09:29:07] [info] Validating configuration... [09:29:07] [success] Configuration is valid [09:29:07] [info] Validating configured region... [09:29:07] [success] Valid region Östergötland [09:29:07] [info] Validating configured locations... [09:29:07] [success] Valid locations Linköping [09:29:07] [info] Starting booking session... [09:29:07] [verbose] Started captcha webserver on port 60690 [09:29:07] [success] Started booking session for 1 person(s) [09:29:07] [warn] Manual captcha verification required [09:29:07] [verbose] Opening captcha page... [09:29:08] [info] Waiting for captcha input... [09:29:17] [verbose] Got new verified captcha token [09:29:17] [success] Accepted booking terms [09:29:17] [success] Residency set [09:29:17] [verbose] Linköping (2022-04-04) 0 free - 0 reserved [09:29:21] [verbose] Linköping (2022-04-11) 0 free - 0 reserved [09:29:24] [verbose] Linköping (2022-04-18) 0 free - 0 reserved

[alesja1986]

Have same problem. After CAPTCHA input search starts but shows always 0 free - 0 reserved.... But need to say really good job guys who made this bot, we fixed passport to my hubby last week :)

[rypto]

Yes, same problem here. Shows always 0 free - 0 reserved no matter what Throttle value I choose in config.json

[svenbox]

Same problem here

[kalkih]

Seems to have been introduced with #28, where the fetchCookie instance wasn't persisted, hence the booking session didn't exist when trying to check for times.

I've pushed a fix, will create a new release in a bit as well