I’m getting these errors which I don’t understand given I’m a ‘pro’ subscriber and these are dedicated endpoints. What can I do to either diagnose or work with these errors appropriately?
1 Like
I’ve heard that this tends to happen in IPv6 environments, but I think it’s basically a bad error. Paid service issue. @meganariley
Thanks for those references; the piece that has me scratching my head is that all the similar messages I’ve found similar to those are either using free accounts/access or not on the dedicated endpoints. In my case these are dedicated endpoints that I’ve set up and I’m on a “pro” account, both used in the attempt to not hit any errors like these.
I’m not seeing any way to reach out to “pro” account support to see if these are bad errors or accurate ones…not sure what to do.
1 Like
I’ve been working on these endpoints for different functional reasons and with noticed the 429 dissipated quite a bit while tuning and tweaking. Now that they’re functioning as expected, the errors are back. Is there really no way to get some support or attention to what’s causing these?
I’m a paying customer/subscriber with dedicated endpoints (so paying for those as well) so this is frustrating…I’ve introduced some random wait times and am trying other hacky things to somehow work around these opaque problems.
Is there any guidance from anyone at HF to try?
1 Like
If you use Hugging Face’s paid service, I think it’s best to use Expert Support as well. I haven’t been told anything in particular. I’m just a user.