The app could not be installed - still

Questions
1

Hi, I’m having the exact same problem as this thread. The difference is that regardless of what I try, I get the exact same error message. I’ve looked at every similar thread in the forum, but none could solve the issue.

So far I’ve tried:

  • Using a clean docker-compose.yaml file from the docs
  • Only defining dnsresolver together with the DirectPay app in docker compose
  • Changing the dnsresolver ip from 192.168.65.5 to 192.168.65.7 as per the docs
  • Tried with both localtest.me and localhost domains
  • Upgrading docker desktop
  • Using the latest cytopia/bind
  • Upgrading and downgrading the DirectPayment app
  • Re-trusted the dev cert and re-exported it
  • Deleted data folder and restarted/rebuilt the containers
  • Checked the database for conflicting apps

Same problem with DirectShipment.
Not sure what else to try. I get this exception, inside both apps:

2023-02-27 14:37:21.1907 [App:01] [17cd347a052675e692455f687365154e] [ERROR] [.NET ThreadPool Worker] Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler - Exception occurred while processing message. System.InvalidOperationException: IDX20803: Unable to obtain configuration from: 'System.String'.
   at Microsoft.IdentityModel.Protocols.ConfigurationManager`1.GetConfigurationAsync(CancellationToken cancel)
   at Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler.HandleAuthenticateAsync()
2023-02-27 14:37:21.1907 [App:01] [17cd347a052675e692455f687365154e] [ERROR] [.NET ThreadPool Worker] Microsoft.AspNetCore.Server.Kestrel - Connection id "0HMOOQ0BI43VU", Request id "0HMOOQ0BI43VU:00000003": An unhandled exception was thrown by the application. System.InvalidOperationException: IDX20803: Unable to obtain configuration from: 'System.String'.
   at Microsoft.IdentityModel.Protocols.ConfigurationManager`1.GetConfigurationAsync(CancellationToken cancel)
   at Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler.HandleAuthenticateAsync()
   at Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler.HandleAuthenticateAsync()
   at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1.AuthenticateAsync()
   at Microsoft.AspNetCore.Authentication.AuthenticationService.AuthenticateAsync(HttpContext context, String scheme)
   at Microsoft.AspNetCore.Authorization.Policy.PolicyEvaluator.AuthenticateAsync(AuthorizationPolicy policy, HttpContext context)
   at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)

Litium version: 8.7.2

2

Maybe solved? Not sure if this was the actual solution but we had a port binding in appsettings, for the current project:

"Kestrel": {
    "Endpoints": {
      "https": {
        "Url": "https://customer.localtest.me:9999"
      }
    }
  },

When I removed the port, it worked (At least I think that was the solution. I’ve tried a lot :slight_smile:)

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.