search

wouterdebie / locast2tuner

Locast to Emby/Plex/Channels server
https://wouterdebie.github.io/locast2tuner/
MIT License
52 stars 8 forks source link

Login failed & 429 Too Many Requests trying to start Docker Container on 0.3.10 #100

Closed sumocomputers closed 3 years ago

sumocomputers commented 3 years ago

All my Docker Containers kept restarting over and over with the previous version of locast2tuner (0.2.x?).

I updated to 0.3.10, and still keeps trying to restart.

I am on macOS 11.5.2 & Docker 20.10.8.

I use a config file and haven't adjusted it to use the new location features, but figured it would be backwards compatible.

CONFIG FILE

username = "redacted@gmail.com"
password = "redacted"
override_zipcodes = ["90210"]
verbose = 3
multiplex = true
tuner_count = 4
days = 30
port = 6077

CONSOLE ERROR

Aug 27 16:25:28.571 INFO locast2tuner 0.3.10 on Linux 5.10.47-linuxkit (Docker) starting..

Aug 27 16:25:28.571 DEBG Main UUID: redacted

Aug 27 16:25:28.571 INFO Consider sponsoring this project at https://github.com/sponsors/wouterdebie!

Aug 27 16:25:28.571 DEBG Logging in with redacted@gmail.com

Aug 27 16:25:28.582 DEBG starting new connection: https://api.locastnet.org/

Aug 27 16:25:28.587 TRCE registering event source with poller: token=Token(1), interests=READABLE | WRITABLE

Aug 27 16:25:28.900 TRCE signal: Want

Aug 27 16:25:28.900 TRCE signal found waiting giver, notifying

Aug 27 16:25:28.900 TRCE poll_want: taker wants!

thread 'Aug 27 16:25:29.048 TRCE signal: Want

Aug 27 16:25:29.048 TRCE signal: Want

main' panicked at 'Login failed', src/credentials.rs:73:14

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Aug 27 16:25:29.048 DEBG response '429 Too Many Requests' for https://api.locastnet.org/api/user/login?client_id=redacted

thread 'main' panicked at 'slog-scope: No logger set. Use `slog_scope::set_global_logger` or `slog_scope::scope`.', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/slog-scope-4.4.0/lib.rs:125:13

stack backtrace:

   0:     0x7f9af929fbe0 - <unknown>

   1:     0x7f9af92e050c - <unknown>

   2:     0x7f9af9299835 - <unknown>

   3:     0x7f9af92a1c1b - <unknown>

   4:     0x7f9af92a16f1 - <unknown>

   5:     0x7f9af92a22e4 - <unknown>

   6:     0x7f9af8dc0944 - <unknown>

   7:     0x7f9af8dc07ec - <unknown>

   8:     0x7f9af8c8a13c - <unknown>

   9:     0x7f9af8dc04b9 - <unknown>

  10:     0x7f9af8dbfd58 - <unknown>

  11:     0x7f9af8dbfb80 - <unknown>

  12:     0x7f9af9287cf6 - <unknown>

  13:     0x7f9af8f9a2cf - <unknown>

  14:     0x7f9af8fb45a6 - <unknown>

  15:     0x7f9af8fbdf97 - <unknown>

  16:     0x7f9af904833f - <unknown>

  17:     0x7f9af9048c3c - <unknown>

  18:     0x7f9af9011dfb - <unknown>

  19:     0x7f9af8f93bbd - <unknown>

  20:     0x7f9af8fcad6f - <unknown>

  21:     0x7f9af8fda880 - <unknown>

  22:     0x7f9af8d30ba2 - <unknown>

  23:     0x7f9af8d0c6a1 - <unknown>

  24:     0x7f9af8cbe50c - <unknown>

  25:     0x7f9af8cbf268 - <unknown>

  26:     0x7f9af8ccaef8 - <unknown>

  27:     0x7f9af8cb924a - <unknown>

  28:     0x7f9af8cf0a32 - <unknown>

  29:     0x7f9af92a2859 - <unknown>

  30:     0x7f9af8ccaf32 - <unknown>

thread panicked while panicking. aborting.

/app/run.sh: line 13:     9 Illegal instruction     /app/locast2tuner -b 0.0.0.0 $config
eiddor commented 3 years ago

It almost looks like Locast is throttling you. Are you able to login via web browser?

sumocomputers commented 3 years ago

I just tried that and I get a "Rate Limit" on Locast.org.

I am thinking that locast2tuner kept trying to login over the last several hours or days, and they froze my account.

Not sure if this will be lifted eventually or not...

wouterdebie commented 3 years ago

https://helpcenter.locast.org/portal/en/kb/articles/max-streams#:~:text=Users%20can%20stream%20Locast%20on,on%20to%20the%20next%20channel.

sumocomputers commented 3 years ago

Thanks, I’ll wait an hour…

mister2d commented 3 years ago

Users can stream Locast on up to 4 devices simultaneously. Channel surfing will cause users to receive this error. We recommend remaining on each channel for at least 30 seconds before moving on to the next channel.

It's pretty sad that Locast causes an issue when you're channel surfing. This is new to me but old news.