- 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
3 Answer(s)
-
0
It seems to be related to HTTPS certificates.
We have a sample running configuration on Kubernetes Helm and docker-compose at https://github.com/abpframework/eShopOnAbp/tree/main/etc.
-
0
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
-
0
I have answered at https://support.abp.io/QA/Questions/3310#answer-084e1ddb-1b93-8b19-d5be-3a04c64322e3
