Activities of "mmaldonado@emscltd.com"

Deploy docker infrastructure

• ABP Framework version: 4.3.3
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): Identity Server Separated
• Template: Microservices
• Problem: I am facing problems to deploy the infrastructure required, could you help me with a Documentation about how to deploy Microservice Infrastucture using Docker to a Azure VM Linux/Windows server, starting from zero please. Also if you can include your recommendation about which OS should I use, I think Linux is going to be better due to cost and features that I have to enable on Azure VM Windows Server.

thank you very much, I found an image on azure market place, that helped a lot, Docker Compose OS linux, on that VM machine docker run without errors, it is working now, thanks

• ABP Framework version: 5.3.0
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): Microservices
• Exception message and stack trace:
• Steps to reproduce the issue:"Create a new empty solution using as template Microservices, then run publish, and then try to publish to IIS, is imposible to make the solution run under iis"

Did you face this error before? Do you know how to deploy microservices solution to IIS?

if I run the publish folder on console using dotnet dll path it works, so I am not sure where the problem is

Chrome says: "ERR_HTTP2_PROTOCOL_ERROR" Firefox says: Secure connection failed

My environment

ABP Framework version: v5.3.0
UI type: angular
DB provider: EF Core
Identity Server Separated (Angular): yes

same problem on my end, please let me know if you get this working please. S I have this configuration over Ports:

WebGateway: https: 44325 AuthServer: https: 44322 IdentityService: https: 44388 ProductService: https: 44361 NewService: https: 44752

AngularClient: http: 4200 ReactClient: http: 5200

CORS: WebGateway: "http://localhost:4200,http://localhost:5200,https://localhost:44307,https://localhost:44325,https://localhost:44353,https://localhost:44367,https://localhost:44388,https://localhost:44381,https://localhost:44361" AuthServer: "http://localhost:4200,http://localhost:5200,https://localhost:44307,https://localhost:44325,https://localhost:44353,https://localhost:44367,https://localhost:44388,https://localhost:44381,https://localhost:44361", IdentityService: "http://localhost:4200,http://localhost:5200,https://localhost:44307,https://localhost:44325,https://localhost:44353,https://localhost:44367,https://localhost:44388,https://localhost:44381,https://localhost:44361" ProductService: "https://localhost:44325,https://localhost:44353" NewService: "http://localhost:4200,http://localhost:5200,https://localhost:44307,https://localhost:44325,https://localhost:44353,https://localhost:44367,https://localhost:44388,https://localhost:44381,https://localhost:44361"

Result:

NewService: Swagger is working, and openApi definition is working ProductService: Swagger is working, and openApi definition is working

WebGateway: works over all old services, but when I try to switch to NewService Api definition from WebGateway it gives me a CORS error, if I pick ProductService it works, that not makes sense to me, it has be something else in between

I found on AuthService logs this line,

2022-06-29 14:48:42.714 -05:00 [DBG] CORS request made for path: /swagger/v1/swagger.json from origin: https://localhost:44325 but was ignored because path was not for an allowed IdentityServer CORS endpoint 2022-06-29 14:48:42.714 -05:00 [INF] No CORS policy found for the specified request. 2022-06-29 14:48:42.977 -05:00 [INF] Request finished HTTP/2 GET https://localhost:44322/swagger/v1/swagger.json - - - 200 - application/json;charset=utf-8 2675.0220ms

After fixing this, that related to ocelot, I forgot to update the up and down stream to the new server address I face this line on AuthServer related to CORS,

2022-06-29 14:48:42.714 -05:00 [DBG] CORS request made for path: /swagger/v1/swagger.json from origin: https://localhost:44325 but was ignored because path was not for an allowed IdentityServer CORS endpoint 2022-06-29 14:48:42.714 -05:00 [INF] No CORS policy found for the specified request. 2022-06-29 14:48:42.977 -05:00 [INF] Request finished HTTP/2 GET https://localhost:44322/swagger/v1/swagger.json - - - 200 - application/json;charset=utf-8 2675.0220ms

My environment

ABP Framework version: v5.3.0 UI type: angular DB provider: EF Core Identity Server Separated (Angular): yes

same problem on my end, please let me know if you get this working please. S I have this configuration over Ports:

WebGateway: https: 44325 AuthServer: https: 44322 IdentityService: https: 44388 ProductService: https: 44361 NewService: https: 44752

AngularClient: http: 4200 ReactClient: http: 5200

CORS: WebGateway: "http://localhost:4200,http://localhost:5200,https://localhost:44307,https://localhost:44325,https://localhost:44353,https://localhost:44367,https://localhost:44388,https://localhost:44381,https://localhost:44361" AuthServer: "http://localhost:4200,http://localhost:5200,https://localhost:44307,https://localhost:44325,https://localhost:44353,https://localhost:44367,https://localhost:44388,https://localhost:44381,https://localhost:44361", IdentityService: "http://localhost:4200,http://localhost:5200,https://localhost:44307,https://localhost:44325,https://localhost:44353,https://localhost:44367,https://localhost:44388,https://localhost:44381,https://localhost:44361" ProductService: "https://localhost:44325,https://localhost:44353" NewService: "http://localhost:4200,http://localhost:5200,https://localhost:44307,https://localhost:44325,https://localhost:44353,https://localhost:44367,https://localhost:44388,https://localhost:44381,https://localhost:44361"

Result:

NewService: Swagger is working, and openApi definition is working ProductService: Swagger is working, and openApi definition is working

WebGateway: works over all old services, but when I try to switch to NewService Api definition from WebGateway it gives me a CORS error, if I pick ProductService it works, that not makes sense to me, it has be something else in between

ABP Framework version: v5.3.0 UI type: angular DB provider: EF Core Identity Server Separated (Angular): yes

2022-06-29 14:48:42.714 -05:00 [INF] No CORS policy found for the specified request. 2022-06-29 14:48:42.977 -05:00 [INF] Request finished HTTP/2 GET https://localhost:44322/swagger/v1/swagger.json - - - 200 - application/json;charset=utf-8 2675.0220ms

My environment

I have this configuration over Ports:

WebGateway: https: 44325 AuthServer: https: 44322 IdentityService: https: 44388 ProductService: https: 44361 NewService: https: 44752

AngularClient: http: 4200 ReactClient: http: 5200

CORS: WebGateway: "http://localhost:4200,http://localhost:5200,https://localhost:44307,https://localhost:44325,https://localhost:44353,https://localhost:44367,https://localhost:44388,https://localhost:44381,https://localhost:44361" AuthServer: "http://localhost:4200,http://localhost:5200,https://localhost:44307,https://localhost:44325,https://localhost:44353,https://localhost:44367,https://localhost:44388,https://localhost:44381,https://localhost:44361", IdentityService: "http://localhost:4200,http://localhost:5200,https://localhost:44307,https://localhost:44325,https://localhost:44353,https://localhost:44367,https://localhost:44388,https://localhost:44381,https://localhost:44361" ProductService: "https://localhost:44325,https://localhost:44353" NewService: "http://localhost:4200,http://localhost:5200,https://localhost:44307,https://localhost:44325,https://localhost:44353,https://localhost:44367,https://localhost:44388,https://localhost:44381,https://localhost:44361"

Result:

NewService: Swagger is working, and openApi definition is working ProductService: Swagger is working, and openApi definition is working

WebGateway: works over all old services, but when I try to switch to NewService Api definition from WebGateway it gives me a CORS error, if I pick ProductService it works, that not makes sense to me, it has be something else in between

thanks a lot app.UseCors was the fix

just to confirm based on your experience, could you write me which should be the CORS on each piece?

for example : on AuthServer => what should we have? Gateways, Services, SwaggerClients and other Clients? on IdentityService => what should we have? on NewServices => what should we have? on Gateways => what should we have?

• ABP Framework version: 5.3.0
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): Microservices
• Steps to reproduce the issue:"After create the new service and solve the CORS, I was trying to create a new tenant with isolated databases, not using the shared ones, I saw the connection string for ProductService, and all the template services, but not the new service"

How do I enable the new service to use an isolated database on microservice template?

Angular => NewTenant => ConnectionStrings => DropDown [... ProductService ]