XML snippet server thing

Dunewarrior

Getting the following error trying to update a configh subscription

The underlying connection was close: an unexpected error occured during a send. 

Followed by

The XML Settings file may be corrupt or  unusable.

Resulting  in no import of the subscription content. 

As far as i know there have been no changes on the subscription server side. And doing a "view in browser" does show the snippets just fine.

Any idea what could be causing that?

Dune

EQAditu

I assume you're saying you have a URL added to the XML Config Subscriptions page and something like Query URL or Update Checked fails in this way?

Would you mind PMing me the subscription URL to see if see if I can determine anything?

EQAditu

So, there are two invisible things that are happening with that URL you sent me.  One is that it is sending a 301 redirect from an HTTP address to an HTTPS address.  Two is that HTTPS address has depreciated/disabled TLS1.0 and an encryption scheme can't be agreed upon by both parties.

ACT is still targeting .NET Framework 4.0, which has never heard of TLS1.2 and only tries 1.0 by default.  Your server will only accept TLS 1.1 and 1.2.

The proposed solution is a .NET configuration change which will tell ACT to use your system's defaults for encryption instead of the antiquated defaults of .NET 4.0.

If you go to your ACT installation folder and change "Advanced Combat Tracker.exe.config" to the following, it should work:

<?xml version="1.0"?>
<configuration>
	<runtime>
		<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
			<dependentAssembly>
				<assemblyIdentity name="Advanced Combat Tracker" publicKeyToken="a946b61e93d97868" culture="neutral"/>
				<bindingRedirect oldVersion="2.5.0.0-3.65535.65535.65535" newVersion="3.3.1.256"/>
			</dependentAssembly>
		</assemblyBinding>
		<AppContextSwitchOverrides value="Switch.System.Net.DontEnableSchUseStrongCrypto=false"/>
	</runtime>
	<startup>
		<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0,Profile=Client"/>
	</startup>
</configuration>

The important change here is the AppContextSwitchOverrides line.

This is also something I can eventually roll out in an update and I don't think it will break anything.  But it may not work in all situations and I may have to target a higher version of the .NET Framework.

Dunewarrior

Okay the update of act would absolutely be brilliiant as i got a whole raid force that would need to change that manually while its not an issue for me, im very certain that alot of the raiders simply wont be able to do that (got some who are rather technofobic) Guess i could make a PS script that will do it for them however .... yeah

Any idea if you will consider upgrading the .NET framework in the foreseeable future ? as that would solve it once and for all, however i can imagine its a rather large task to make sure all plugins etc will continue to work etc.