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

Unable to schedule backup to S3 #5114

Open
kirangowda29 opened this issue Mar 7, 2024 · 5 comments
Open

Unable to schedule backup to S3 #5114

kirangowda29 opened this issue Mar 7, 2024 · 5 comments

Comments

@kirangowda29
Copy link

We are facing error in scheduling backup to S3.

The error is:
Amazon.Runtime.AmazonServiceException: A WebException with status NameResolutionFailure was thrown. ---> System.Net.WebException: Error: NameResolutionFailure
image

@kenkendk
Copy link
Member

kenkendk commented Mar 7, 2024

It looks like a network error? The machine in question cannot make a DNS lookup for the AWS S3 hostname you are using.

If this is a new S3 bucket, there is sometimes a delay in the registration of DNS records.

@kirangowda29
Copy link
Author

This is not not new S3 bucket, the same configuration was working in earlier version of Duplicati. We configured this new version recently and its not working.

@ts678
Copy link
Collaborator

ts678 commented Mar 7, 2024

working in earlier version of Duplicati. We configured this new version

What is the new version? Do you know old one? About --> System info will show both, if you updated via Duplicati updater.

What OS? Does Test connection work? If Docker, where is image from?

@kirangowda29
Copy link
Author

What is the new version? --> 2.0.7.1
Do you know old one? --> Don't exactly remember the old one as we deleted the server, may be 2.0.2
What OS? --> Oracle Linux
Test connect result:
image

Docker image --> https://github.com/linuxserver/docker-duplicati

@ts678
Copy link
Collaborator

ts678 commented Mar 8, 2024

So someone else's image, not by Duplicati project. I don't have Docker, but can you resolve the name inside the container, maybe using a docker exec and nslookup or ping or whatever is available? I don't know why Duplicati would resolve any differently.

we deleted the server

Did you export the Duplicati config and use that to set up the new Duplicati? If not, possibly the Server name was entered wrong. What's in that field is what's looked up, so you also don't want to be adding additional prefixes to it (e.g. https) to make it a URI.

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

3 participants