Bug: Fresh Ubuntu 20.04 Install, Error: [X] The search backend threw an exception=[Errno -3] Temporary failure in name resolution:
See original GitHub issueDescribe the bug
Clean docker-compose install on Ubuntu 20.04, running
docker-compose run archivebox add 'https://example.com'
results in the following error:
[X] The search backend threw an exception=[Errno -3] Temporary failure in name resolution:
DNS works fine and no errors are reported in ‘archivebox --version’. Error occurs on all URL’s; there is nothing ‘temporary’ about it.
Screenshots or log output
ArchiveBox version
Latest v0.5.6
Any ideas on what could be causing this? Thank you!
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
How to Resolve the "Temporary failure in name resolution" Error
The "Temporary failure in name resolution" error appears due to bad system configuration. This article shows how to troubleshoot and fix it.
Read more >Ubuntu 20.04 Temporary failure in name resolution
I have downloaded Ubuntu 20.04 cloud image for OpenStack, and I can lunch ... I get the following error: "Temporary failure in name...
Read more >Ubuntu 20.04 temporary failure in name resolution for wired
If you're getting this error "cat: /var/run/systemd/resolve/resolve.conf: No such file or directory", then it means you dont have any DNS server ...
Read more >How to Resolve "Temporary failure in name resolution" Issue
In this article, we will look at some of the causes of the 'temporary failure in name resolution' error and solutions to this...
Read more >Temporary failure resolving error on Ubuntu 20.04 Focal ...
The following tutorial will provide you with simple to follow steps on how to resolve the Temporary failure resolving error on Ubuntu 20.04...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I followed those steps, created a folder called “sonic” inside the ./data folder, and it still didn’t work…so then I removed the sonic docker container (docker rm xx) so it was recreated at next run and now it appears to be working. Thanks!!
Awesome. Thanks so much!