Yesterday I got the following message box appear on my Windows machine.
“2024-10-06 17:10:26 + 11 -[Warning-
Duplicati.Library.Modules.Builtin.ReportHelper-
ReportSubmitError]: Failed to send message:
System.Net.WebException: The remote name could not be
resolved: ‘ingress.duplicati.com’ WebException: The remote
name could not be be resolved: ‘ingress.duplicati.com’”
What is the cause or resolution to this error?
Can you please list these errors in the manual?
WebException The operation has timed out sounds awfully similar. Answer there might apply, however the one here is the attempt to find the Internet address of ingress.duplicati.com.
Transport over the Internet is done by address. Names are looked up first to find where to go.
I can reproduce this issue if I have my computer disconnected from Internet at end of backup. Possibly your situation is different. Outages can occur beyond the local end of the connection.
If you click on the link you posted, and your browser can’t get there, Duplicati might not either.
Thank you ts678 for your reply.
I got that warning on 6 Oct 2024. On 10 Oct 2024 I got the same message. However this time it was a different backup script.
Immediately after the warning on 10 Oct 2024 I manually tried to go to the web address ‘ingress.duplicati.com’. My browser did so by resolving to https://duplicati.com
There are two thoughts regarding this warning.
Neither of the warnings got written to the log for the scripts. This is a concern.
Duplicati is probably calling home to notify home of the warning.
I have now turned off that option in Settings.
Please clarify which log.
Are you using scripts? They generally should run their own log if they want one, however
Where does script output go to (difference between BEFORE and AFTER?)
may help if you have a script that wants a log, but isn’t doing its own. Note timing matters:
Viewing the log files of a backup job refers to the backup itself. This log can be sent using
Reporting options
however I don’t thnk a transfer problem retrofits that log to indicate that it couldn’t be sent.
There is no queue/retry mechanism built in that I know of, which is why a lack of backup is reportable more reliably externally than by Duplicati itself. Its computer may even be down.
Are you writing CLI scripts using the GUI?
Scripting options exist either way, but basic GUI job is not a script. Please clarify your usage.
I don’t follow that, but there’s much here that needs clarification. Was there another warning?
Please clarify which option you have turned off. If you mean send-http-url, your usage with ingress.duplicati.com should always try to send. This allows detection of missed backups.
Unless there was some other warning you missed, the only loss was a mystery network outage (somewhat more assured because you spoke to the server admin on your other related issue).
Without that assurance, there’s a chance the server was down briefly, but even that would have difficulty taking DNS down (because DNS is spread more widely, throughout Internet services).
What OS is this? Some might cache DNS answers, which may help ride through some outages.
Are you backing up to a Storage Type that needs working Internet, or to something that’s local?
That is by design. The server that the report is going to does not contain any browse able content. To help people who see the hostname in logs, visiting the site redirects you to the parent site.
The fact that you can connect to the site with a browser, suggests that this is not a network issue. Most likely a firewall of sorts is preventing Duplicati from connecting. If the firewall is per-process, you will have no problems with a browser or a ping tool.
You see the warning, so clearly it is logged? Where did you expect it to be logged?
Duplicati has a usage reporter that sends anonymous usage stats back. You can see the data here:
https://usage-reporter.duplicati.com
However, this is NOT related to the ingress endpoint you mentioned. That endpoint is for the Duplicati console/portal that has a manual setup step.
Did this happen on every backup before you removed the option that sends it?
The description is not clear on whether it’s a sometimes or an always problem.
Firewall would probably be consistent. Network issues more likely intermittent.
What OS is this? Firewall behavior varies with different OS. For example Windows might say:
I decline the “Allow access” button (using “Cancel” instead. and outbound still runs just fine.
Windows Firewall overview says “default is allow all outgoing traffic, unless matching a rule”
I did give the OS in the first line of my first post. But here is the information from Duplicati:-
OSType : Windows (from About Duplicati, button ‘System Info’)
OS: Microsoft Windows NT 10.0.22631.0 (from system-info.txt)
Version name: “2.0.8.1_beta_2024-05-07” (2.0.8.1) (from system-info.txt)
The message has now come from two different GUI Jobs. Hopefully I am now using the correct terminology.
The error does not appear in the GUI Job log. The summary states:-
Warnings 0
Errors 0
I noticed that there is another log. From the GUI. Menu About. Button ‘Show log’. This gives Log data from the server. The error does not appear here.
Is this where the error should appear?
You would need a developer to comment. It appears in About → Show log → Live → Warning, however that’s not something you’d usually set up. Similar situation for a user optioned log-file.
The error appears for you on a big yellow popup at bottom of screen, right? Example from me:
There’s a known issue of the Show button using the job log, which is usually right, but not always. There’s not much about this one that isn’t already on the screen. Log file on disk has internal info:
2024-10-14 08:15:02 -04 - [Warning-Duplicati.Library.Modules.Builtin.ReportHelper-ReportSubmitError]: Failed to send message: System.Net.WebException: The remote name could not be resolved: 'ingress.duplicati.com'
System.Net.WebException: The remote name could not be resolved: 'ingress.duplicati.com'
at Duplicati.Library.Modules.Builtin.SendHttpMessage.SendMessage(String subject, String body)
at Duplicati.Library.Modules.Builtin.ReportHelper.OnFinish(Object result, Exception exception)
Live log is similar:
These all say that the report couldn’t be sent. Are you sure your network is OK at failure time?
Does this computer ever move? A WiFi or cellular laptop is likely to suffer intermittent outages.
Repeating (anything unclear?):
Repeating:
In the 2.0.8.1 there is limited logging around the backup report. I fixed this in the canary builds, so it should now show up like a “normal” warning in the way illustrated by @ts678
I showed the popup and the log-file. I would consider the most “normal” to be the job log.
2.0.9.108 still does the log-file, though interestingly the specific error here looks different:
2024-10-11 07:53:17 -04 - [Warning-Duplicati.Library.Modules.Builtin.SendHttpMessage-HttpResponseError]: HTTP Response request failed for: https://ingress.duplicati.com/backupreports/D9TDf_1NWuX2j_miRLi9e20c5x-iIM7UCuq51teAYrLxqIhziG_C6dfU4OIHGNDYBJSJID3Mmi5M1XEPI7fPm3X55oW1fJw4FinjuauqsP6CHk0kyem7ZvOroJW_roQsoBAHcAA8fTAhir-VmQGz23yy39p-vk524QRh9fTPM0A
System.Net.Http.HttpRequestException: No such host is known. (ingress.duplicati.com:443)
---> System.Net.Sockets.SocketException (11001): No such host is known.
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|285_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(QueueItem queueItem)
at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
at Duplicati.Library.Modules.Builtin.SendHttpMessage.SendMessage(HttpClient client, SendRequestType target, String subject, String body)
2024-10-11 07:53:17 -04 - [Warning-Duplicati.Library.Modules.Builtin.ReportHelper-ReportSubmitError]: Failed to send message: System.Net.Http.HttpRequestException: No such host is known. (ingress.duplicati.com:443)
--> System.Net.Sockets.SocketException: No such host is known.
System.Net.Http.HttpRequestException: No such host is known. (ingress.duplicati.com:443)
---> System.Net.Sockets.SocketException (11001): No such host is known.
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|285_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at Duplicati.Library.Modules.Builtin.SendHttpMessage.SendMessage(String subject, String body)
at Duplicati.Library.Modules.Builtin.ReportHelper.OnFinish(Object result, Exception exception)
Was job log supposed to pick it up in this Canary? Doesn’t seem to:
Complete log has
"Messages": null,
"Warnings": null,
"Errors": null,
If need be, I can test again in case I forgot what I did before, but which log should get this?
The server log didn’t either. IIRC, both 2.0.8.1 and 2.0.9.108 got the yellow popup. Clarify?
Thank you both for looking into this issue.
I look forward to the next release.
I see… It is a chicken-and-egg problem. The error happens when sending the report (meaning after the report was created), so the error cannot be inside the report.
In that case it is only reported in the server log or on the commandline.
Since this is getting further posts, I’ll note that DNS lookups are not done directly by Duplicati, therefore Duplicati cannot fix the code. It might not be in code anyway, but a network problem.
Ordinary web programs probably let Windows do the DNS lookup. Browsers can do their own.
DNS over HTTPS can let you look at your OS and browser to see which method might be bad. Router (especially if this is a home setup – is it?) often gets involved in traditional DNS lookup. Internet service provider may get involved. You can move that to another public DNS resolver.
Amidst all possible variation, your network being out can likely cause this and your other issue. Possibly with time you will find out if the problem is repeatable, how often, and with which jobs.