Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get error "Error resolving address" only sometimes #259

Open
DeepHorizons opened this issue May 9, 2019 · 2 comments
Open

Get error "Error resolving address" only sometimes #259

DeepHorizons opened this issue May 9, 2019 · 2 comments
Assignees

Comments

@DeepHorizons
Copy link

We are running into an issue with this library. We have created a application that uses this library. Sometimes when we run the application it works as expected, but sometimes an exception is thrown with this message:

Error resolving address

If it doesn't work, it never resolves itself unless the application is restarted (and when it starts back up its a coin toss if it works or not). Looking over the code it seems this message comes from the cpprest/Casablanca library here but we have not been able to find out anything past that on the library end.

Things we have tested:

  • Tested with (libazure: 5.0.0, cpprest: 2.8) and (libazure: 6.0.0, cpprest: 2.10.13) on Ubuntu 16.04
  • Time is set right
  • Doing a packet capture shows that when it doesn't work there are no packets being sent (as determined by tcpdump)
  • We can connect to the internet and dig returns a response for the address being requested

Running with a debug build doesn't give us any more information. Is there something else we can do? Any ideas to try?

@EmmaZhu
Copy link
Member

EmmaZhu commented May 10, 2019

Hi @DeepHorizons,

From the error message, seems it's because the request cannot successfully connect to the server endpoint.
Could you share the protocol you were using (HTTP or HTTPS), and whether there's any proxy when you met this issue?

Thanks
Emma

@DeepHorizons
Copy link
Author

DeepHorizons commented May 10, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants