Suddenly getting "Unknown location" from wttr.in, was working fine before

[Nicobgn]

I've been using wttr.in to get weather data for my area for a few weeks, and it had been working perfectly. However, today I suddenly started getting this message instead of the usual weather output:

"Unknown location; please try ~[latitude],[longitude]"

I'm using this script, which I found on the Waybar wiki. It used to show the weather just fine, but now it's completely broken — no weather data is returned at all, just that error message.

I’ve always used the City+Country format (e.g., Rosario+Argentina) to avoid ambiguity, and even tested it directly in a browser when I first set it up. I tried again today both with the city name and with an approximate latitude/longitude, but nothing seems to work — the site still returns the same error.

Is anyone else facing this issue? Has the API or location format changed recently?

[Nicobgn]

After researching some more time, I found this, and I'm in the same case that @alexeygumirov, @chubin said:

The second problem may occur again, when wttr.in goes beyond its daily queries capacity.
We doubled the capacity recently (it will be effectively increased since 1 March 2021),
and so the problem should not occur so often.

So, it means that today's queries were done before I tried to do mine. I hope to have a better luck tomorrow.