You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our users use the OwnTracks app to send location data in to our system, and it's worked brilliantly so far. But one of our Android users, whose location had been received via the API no problem, suddenly started getting error notifications. The first error he received was:
"Error: java.net.UnknownHostException: Unable to resolve host "[host name]": No address associated with hostname"
We confirmed that his URL endpoint was set correctly, and no other users are having this issue.
He has rebooted his phone, and that error disappeared, but was replaced by one which simply read "Error"
Nothing is coming through from his OwnTracks to us since these error notifications started.
Advice gratefully received!
The text was updated successfully, but these errors were encountered:
Unable to resolve host "[host name]": No address associated with hostname" is definitely a host resolution (i.e. DNS) issue; the app wasn't able, at that point in time, to have look up the address of the URL you specified in the app.
replaced by one which simply read "Error"
I am not aware where in our code it would say that, and i very much doubt it actually is a message from OwnTracks.
Our users use the OwnTracks app to send location data in to our system, and it's worked brilliantly so far. But one of our Android users, whose location had been received via the API no problem, suddenly started getting error notifications. The first error he received was:
"Error: java.net.UnknownHostException: Unable to resolve host "[host name]": No address associated with hostname"
We confirmed that his URL endpoint was set correctly, and no other users are having this issue.
He has rebooted his phone, and that error disappeared, but was replaced by one which simply read "Error"
Nothing is coming through from his OwnTracks to us since these error notifications started.
Advice gratefully received!
The text was updated successfully, but these errors were encountered: