Duplicaty crashes after 30 seconds

Support
1

After successfully using duplicaty at home, I have recently installed version 2.0.1.53 at my office computer.
Unfortunately it crashes after about 30 seconds. It shows a Message-Box window saying "Duplicati.GUI.TrayIcon funktioniert nicht mehr. Ein Problem hat die richtige Ausführung verhinder. Schließen sie das Program."
I would translate this roughly with “Duplicati.GUI.TrayIcon does not work properly. A problem occoured. Please close the program”

After starting duplicati again, I managed to have a quick look into the web-interface to gather some information from the log.

There is several times the same entry that the usage reporter faild. Translation of the WebException is “the remote server returned an error (407) proxy authentication required”

This is reasonable, as my company routes all traffic through a proxy. However proxy settings in windows are done properly - means starting IE I can access websites through the proxy.

Is there any special place in duplicaty to enter the proxy credentials ? Or any way to disable the usage reporter ? Further suggestions to deal with this situation ?

-------------------------snip----------------------------------------
Jan 9, 2018 9:25 PM: UsageReporter failed
{“ClassName”:“System.Net.WebException”,“Message”:“Der Remoteserver hat einen Fehler zurückgegeben: (407) Proxyauthentifizierung erforderlich.”,“Data”:null,“InnerException”:null,“HelpURL”:null,“StackTraceString”:" bei Duplicati.Library.Utility.AsyncHttpRequest.AsyncWrapper.GetResponseOrStream()\r\n bei Duplicati.Library.Utility.AsyncHttpRequest.GetRequestStream()\r\n bei Duplicati.Library.UsageReporter.ReportSetUploader.c__async1.MoveNext()",“RemoteStackTraceString”:null,“RemoteStackIndex”:0,“ExceptionMethod”:“8\nGetResponseOrStream\nDuplicati.Library.Utility, Version=2.0.1.53, Culture=neutral, PublicKeyToken=8bfe994a39631a7b\nDuplicati.Library.Utility.AsyncHttpRequest+AsyncWrapper\nSystem.Object GetResponseOrStream()”,“HResult”:-2146233079,“Source”:“Duplicati.Library.Utility”,“WatsonBuckets”:null}
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:25 PM: UsageReporter failed
Jan 9, 2018 9:24 PM: Server gestartet und hört auf 127.0.0.1, Port 8200
-------------------------snip----------------------------------------

2

Hi @umbilo, welcome to the forum!

I’m glad to hear Duplicati is working OK for you at home, but not so happy to hear about the proxy issues at work.

If you can get into the main menu Settings page you can scroll down to “Usage Statistics” and set “Anonymous usage reports” to none/disabled which should stop the attempted usage report.

Let us know if you can’t get into the GUI as there’s probably a way to manually edit the config files directly - but I’d have to research how to do it.

I’ll also try to replicate the issue you’re having to verify it really is a proxy problem. Hopefully we can replicate the issue - we may not be able to fix it (such as adding proxy server support) but it certainly shouldn’t crash in this scenario!