Nope no proxy, but I just managed to figure out what was happening though.
For one reason or another, the Yahoo API stopped working for us (we're fairly low-level utilisers so I'm not sure what happened), thus I swapped us over to using the Google API (with a Key). What I didn't realise is that Google's Geocoding API is disabled by default when you get one of these keys, enabling it in the Google Dev Console has sorted out the issue.
The data between the Google API and Yahoo API is a bit inconsistent, deleting all rows from the devices_locations table seems to have forced a refresh on the geocoding data for all devices so now it's all based off the Google API - happy days.
Thanks for your help Peter
Jacob Bisby
-----Original Message----- From: observium [mailto:observium-bounces@observium.org] On Behalf Of Peter.Hine@familycourt.gov.au Sent: Thursday, 18 February 2016 8:37 AM To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Unknown Locations in Device > Locations menu [SEC=UNCLASSIFIED]
are you running thru a proxy ? my last fault (28thJan) was the exact same thing (new servers were unkown) but it was the proxy filters setting "http://maps.googleapis.com"" as a search site so got blocked for the observium server.
thanks
Peter Hine Senior Technical Support Engineer (Servers) FCoA ITS peter.hine@familycourt.gov.au
********************************************************************** The information contained in this e-mail (including any attachments) is for the exclusive use of the addressee. If you are not the intended recipient please notify the sender immediately and delete this e-mail. It is noted that legal privilege is not waived because you have read this e-mail. **********************************************************************
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium