Thanks @maliming, problem was solved. It was reletated to activate TLS protocols on the server.
hi @maliming yes, i can share my screen. I send you an email.
Hi maliming.
This is appsetting.json
from API
{
"App": {
"SelfUrl": "https://api.server.com:51114",
"ClientUrl": "https://front.server.com:51113",
"CorsOrigins": "https://.server.com,https://front.server.com:51113,https://api.server.com:51114"
},
"ConnectionStrings": {
"Default": "Data Source=XXXX-01;Initial Catalog=TicketsADB;Integrated Security=True"
},
"AuthServer": {
"Authority": "https://api.server.com:51114",
"RequireHttpsMetadata": "false"
},
"StringEncryption": {
"DefaultPassPhrase": "XXXXXX0frz1ifcLs"
},
"Settings": {
"Volo.Abp.LeptonTheme.Style": "Style1", / Options: Style1, Style2... Style6 /
"Volo.Abp.LeptonTheme.Layout.MenuPlacement": "Left", / Options: Left, Top /
"Volo.Abp.LeptonTheme.Layout.MenuStatus": "AlwaysOpened", / Options: AlwaysOpened, OpenOnHover /
"Volo.Abp.LeptonTheme.Layout.Boxed": "False", / Options: True, False */
"Abp.Mailing.Smtp.Host": "127.0.0.1",
"Abp.Mailing.Smtp.Port": "25",
"Abp.Mailing.Smtp.UserName": "",
"Abp.Mailing.Smtp.Password": "",
"Abp.Mailing.Smtp.Domain": "",
"Abp.Mailing.Smtp.EnableSsl": "false",
"Abp.Mailing.Smtp.UseDefaultCredentials": "true",
"Abp.Mailing.DefaultFromAddress": "noreply@abp.io",
"Abp.Mailing.DefaultFromDisplayName": "ABP application"
},
"AbpLicenseCode
This is appsetting.json
from MigratorDb
{
"ConnectionStrings": {
"Default": "Data Source=XXXX-01;Initial Catalog=TicketsADB;Integrated Security=True"
},
"IdentityServer": {
"Clients": {
"Tickets_Web": {
"ClientId": "Tickets_Web",
"RootUrl": "https://api.server.com:51114"
},
"Tickets_App": {
"ClientId": "Tickets_App",
"RootUrl": "https://front.server.com:51113"
},
"Tickets_Blazor": {
"ClientId": "Tickets_Blazor",
"RootUrl": "https://front.server.com:51113"
},
"Tickets_Swagger": {
"ClientId": "Tickets_Swagger",
"ClientSecret": "1q2w3e*",
"RootUrl": "https://api.server.com:51114"
}
}
},
We publish an empty app generate with ABP Suite. The deployment of the project is on IIS. API show me Swagger page and Angular Front app is runing but after make login i got this console error:
***Access to XMLHttpRequest at 'https://api.server.com:51114/.well-known/openid-configuration' from origin 'https://front.server.com:51113' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource***.
And the error promt is this:
***An error has occurred!
http failure response for https://api.server.com:51114/api/abp/application-configuration: 0 Unknown Error***
Checkig on the API's log file i found following code:
***[ERR] Connection ID "16717361818409893977", Request ID "8000005a-0000-e800-b63f-84710c7967bb": An unhandled exception was thrown by the application.
System.InvalidOperationException: IDX20803: Unable to obtain configuration from: 'https://api.server.com:51114/.well-known/openid-configuration'.
---> System.IO.IOException: IDX20804: Unable to retrieve document from: 'https://front.server.com:51114/.well-known/openid-configuration'.
---> System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host***
This is code that i have on the API
private void ConfigureAuthentication(ServiceConfigurationContext context, IConfiguration configuration)
{
context.Services.AddAuthentication()
.AddJwtBearer(options =>
{
options.Authority = configuration["AuthServer:Authority"];
options.RequireHttpsMetadata = Convert.ToBoolean(configuration["AuthServer:RequireHttpsMetadata"]); ;
options.Audience = "Tickets";
options.BackchannelHttpHandler = new HttpClientHandler()
{
ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator
};
});
}
***Google the error, someone says it's certificate error so we recreate a new certificate, but same error.***
Hi @christianharo You can bypass that error Clenning Browser cache history, Or Star the app in the browser private mode.
Hi, @nowayja
Another option you can do is this:
@alper Thanks for your help and suggets. I gonna probe that option.
I wan to make aditional comment We had been make a publish with ABP 3.3.1 on comunity version. And we don't get this errors. For Commercial ABP 4.0.0 with dot net 5, the numbers of files has incremented sifnificative, and is on this version when staring this errors.
@alper Thanks for your recomendations. I follow and make steps incate for you. Except rename Blazor Dll's No I get a vareity of error but Blazor App don't star. On Opera I get this conosole log message: Uncaught SyntaxError: Unexpected token '<' On Edge i get something like: Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR :51113/_framework/System.Numerics.dll:1 Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR 2galacweb.galac.com/:1 Uncaught (in promise) TypeError: Failed to fetch :51113/_framework/System.Reflection.Emit.ILGeneration.dll:1 Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR Do you have any suggest?
When I generate a Blazor Project (Using ABP4.0.0 stable) to Publish, compiler show me this error: System.Runtime.CompilerServices.SuppressIldasmAttribute.SuppressIldasmAttribute(): Error processing method 'System.Runtime.CompilerServices.SuppressIldasmAttribute.SuppressIldasmAttribute()' in assembly That's error doesn't appear when i compile to release or debug. Only show me that when i go to Publish Option. To avoid that i put Publish Trimmed option in false. <PublishTrimmed>false</PublishTrimmed> But when i deploy on testing server i got this console error. Failed to find a valid digest in the 'integrity' attribute for resource '<URL>' with computed SHA-256 integrity. When i run app on IDE Mode every thing it's Ok
I had a similar error: what I see the Blazorise nugget component you have referenced is wrong. You must use at least version 0.9.3-preview2; Since from that version it is compiled to MS Framework 5.0. You need to change the initialization in the Blazor project which changed as well.