VisualStudio Error on startup (Linux, LinuxRemoteDebugTargetsProvider )

I was getting an error in Visual Studio 2017, when opening a project.

LimitedFunctionality
System.AggregateException: One or more errors occurred. --- System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Build.Linux.Shared.RemoteTargetUtils.ProcessorArchToPlatform(String remoteArchitecture)
at Microsoft.Build.Linux.Shared.RemoteTargetUtils.ConnectionToDisplayNameShort(StoredConnectionInfo storedConnectionInfo)
at Microsoft.VisualStudio.Linux.ProjectSystem.v2.LinuxRemoteDebugTargetsProvider.[GetEnumeratorEnumValuesAsync]d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Linux.ProjectSystem.v2.LinuxRemoteDebugTargetsProvider.]]c__DisplayClass25_0.[[Initialize]b__1]d.MoveNext()
--- End of inner exception stack trace ---
--- (Inner Exception #0) System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Build.Linux.Shared.RemoteTargetUtils.ProcessorArchToPlatform(String remoteArchitecture)
at Microsoft.Build.Linux.Shared.RemoteTargetUtils.ConnectionToDisplayNameShort(StoredConnectionInfo storedConnectionInfo)
at Microsoft.VisualStudio.Linux.ProjectSystem.v2.LinuxRemoteDebugTargetsProvider.[GetEnumeratorEnumValuesAsync]d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Linux.ProjectSystem.v2.LinuxRemoteDebugTargetsProvider.[]c__DisplayClass25_0.[[Initialize]b__1]d.MoveNext()---

Fix:
To fix/hack this problem go to Tools-Options-Cross Platform-Connection Manager and delete the default connection (I only had one, but you might need to delete all) and restart VS and then you can remake the connection and the problem is fixed