Open WilliamMayor opened 6 years ago
Unfortunately I've been seeing the same. I have raised that through my contacts at HMRC, but I haven't heard anything back.
I should add that I don't see this everywhere, which leads me to wonder whether the problem is that the machines that do show that problem are talking over IPv6 instead of IPv4. I haven't found the time to test that, mind. It's either that, or someone is watching the service logs and blocking anything they don't recognise.
To test the IPv6 theory I disabled it on my virtual machine and tried again. I got the same error. Unless virtual box is monkeying around with the connections in a way that I don't understand, I think this is unrelated to the IP version.
What a pain. Is there a terms and conditions of use of the VIES service?
It isn't VIES that does this — it's VRWS (the VAT Rate Web Service) — and no, there aren't any Ts & Cs, nor is it actually mentioned anywhere on the EU's website. I was given the URL by one of the member states' VAT officials.
As I say, I have asked about this, but haven't heard back yet.
Last I checked (quite some time ago now), it doesn't appear to be blocked from every IP address, which makes it more annoying because it implies that someone either did this deliberately or that they've got some kind of automated system that's misconfigured somehow.
FWIW, I've also just emailed the address in the block message to ask about it. We'll see if they have anything to say.
Hey @al45tair any news on this?
Sorry, no responses at all from the EU side.
It's June already and I see the same error as well. As a workaround, could this package supply a static list of VAT rates for all countries as fallback in case the webservice is unavailable? Hopefully someone still has this data... ;-)
Hi, I think this might be the same error as you mentioned in a BitBucket issue, but I thought I'd raise it here too.
I'm getting 502 - Bad Gateway error when I try to call
get_rates
, the body of the response is this:I see this error when running my local dev version inside a virtual machine.
Should I contact them myself? Or is this something the library needs to adapt to?
Thanks!