I am trying to access a token, but having trouble.
Error message
{"error":"invalid_grant","error_description":"Authentication failed."}
If I use --data-urlencode, I get an unsupported_grant_type error.
Resolution
You must use a SystemWeaver username and password to be able to get a token.
The Rest API's connection to the SystemWeaver server is unstable.
Error message
Connection to serverA:1111 failed. System.Exception: Unable to connect to server, name:serverA, port:1111, Message: No connection could be made because the target machine actively refused it 123.45.67.890:1111 ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
Resolution
Confirm that users can connect to the SystemWeaver server with a client application. Verify that there is no firewall stopping the Rest API server from connecting to the SystemWeaver server.
I am unable to reach the Rest API via the web.
Error message
ERR_SSL_PROTOCOL_ERROR
Resolution
This error relates to the set up of the certificate. It must be added to the correct port, etc. Check that the certificate is properly set up, e.g., in correct location, etc.
I am unable to reach the Rest API documentation via the web using Internet Explorer.
Resolution
The documentation doesn't load in Internet Explorer because support for it has been dropped in Swagger UI which is used for the documentation. Switch to another browser.
The Rest API is running as an executable with https enabled, but I am unable to reach it via the web.
Error message
User profile is available. Using 'C:\Users\john.doe\AppData\Local\ASP.NET\DataProtection-Keys' as key repository and Windows DPAPI to encrypt keys at rest.
Unhandled exception while processing 0HM6VPT1O95KC. System.ComponentModel.Win32Exception (0x8009030D): The credentials supplied to the package were not recognized
Resolution
Run the executable as Administrator.
The Rest API is running as an executable with https enabled, but I am unable to reach it via the web.
Error message
ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY
Resolution
AspNetCore is trying to use HTTP2 on a machine that doesn't support it without manual configuration (Windows Server 2012 R2/Windows 8.1 and below). This is a known bug that has been fixed in the master branch of AspNetCore, but the fix is not officially rolled out as of this writing (2021-03-05). The solution is to set "allowHttp2": false in the appsettings.json.