Next, I configured it to https (SSL), setting the thumbprint of a self-signed certificate according to the documentation, etc.. After that, the error in the Event Viewer it this:
Category: Microsoft.Dynamics.Nav.Common.Http.AntiSSRFWrapper
EventId: 0
ConnectionId: 0HNC6ATF3RUGA
RequestId: 0HNC6ATF3RUGA:0000000C
RequestPath: /BC260W1/csh
TransportConnectionId: vm92RxGS4KcWa6hd8ekxpg
HttpMethod: GET
Uri: https://daxrobcdevdemo:7085/BC260W1/client/metadata/navigation
{OriginalFormat}: HTTP {HttpMethod} {Uri}
MemberName: LogSSRFException
FilePath: s:\repo\src\Platform\ClientServerShared\Prod.Common\Http\AntiSSRFWrapper.cs
LineNumber: 52
ExceptionType: System.Security.SecurityException
Exception:
System.Security.SecurityException: Non routable addressed detected: <mycomputername>
Error accessing Website BC260W1
Type: System.Security.SecurityException
Source: Microsoft.Dynamics.Nav.Common
HResult: -2146233078
StackTrace:
at Microsoft.Dynamics.Nav.Common.Http.AntiSSRFHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) in s:\repo\src\Platform\ClientServerShared\Prod.Common\Http\AntiSSRFHandler.cs:line 38
at Microsoft.Dynamics.Nav.Client.ConnectionExceptionHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) in s:\repo\src\Platform\Client\Shared\Prod.Client.ServiceConnection\RequestResponse\Handlers\ConnectionExceptionHandler.cs:line 24
at Microsoft.Extensions.Http.Logging.LoggingScopeHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, 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 Microsoft.Dynamics.Nav.Common.Http.HttpServiceClient.CallService[T](String requestUrl, HttpMethod method, Object content) in s:\repo\src\Platform\ClientServerShared\Prod.Common\Http\HttpServiceClient.cs:line 101
at Microsoft.Dynamics.Nav.Client.ConnectionStateManager.CallServer[T](Func`1 callServer, Nullable`1 options) in s:\repo\src\Platform\Client\Shared\Prod.Client.ServiceConnection\ConnectionStateManager.cs:line 50
After that, I tried BC 25.6 on-premise. I used the exact same configuration steps and settings, and the 25.6 web client works seamlessly, with and without SSL. Also verified, that the URLs and other settings do not have typos for 26.0. Finally I compared the web client folders of the 25.6 and 26.0 versions, and saw, that some DLLs have changed, and this fantastic AntiSSRFWrapper is a newcomer. Do you have any ideas, how can I make the 26.0 version work? Or any help regarding the configuration of the antiSSRF dll, or how to whitelist the BC service?
I have 2 restrictions (from customer): I must use on-prem BC, not cloud, and I cannot have 2 separate computers, in other works, I cannot separate the web client and the BC service to separate VMs.
Thanks in advance!
____________________________________________________________________________________________________________________________________________________________________________
Meanwhile I found a solution: in the navsettings.json, the "Server" tag/attribute must have "localhost" value, it does not like the explicit name of the computer.
