Activities of "gterdem"

Thanks but it's not the identityserver that's not starting now. It's another service. We will deal with getting identityserver a certificate later

The error you have shared is from AuthServer.

You can also check AuthServer deployment on Kubernetes guide to check if it is working for you.

@ronaksbhavsar,

I am sorry, I have no experience or expertise in the problem you are having in your production environment.

Seems @chris.tune also had the same problem and he resolved it after upgrading to v5.1.3.

I would suggest trying to same by taking migration guides into consideration

AuthServer PreConfiguration for X509 certificate is for signing the tokens, not SSL communication between services.

You can check here for more information.

See [answer #2283](https://support.abp.io/QA/Questions/2283/Logging-out-of-External-Provider-Azure-AD-OpenId-Connect#answer-81067dd9-c1b7-b783-cbc0-3a00da3ddd36).

Yout template version?

Hi,

i know eshopOnAbp.. the question is if there is a reason, why the abp cli doesn't support the - db mongodb parameter with the microservice template ?

Hi @hakan.uskaner,

We thought about that and decided to create a sample (in eShopOnAbp) about how to do it instead of adding it. Mainly because as an initial template, It would be an extra bunch of files confusing developers when they won't be using most likely.

However, generating templates with different db-providers is a bit more complicated process and we have it on backlog however we have not decided scheduled milestone for implementation.

Probably Redis is not running and Redis is a pre-requirement for tiered (separate identity-server) solutions.

You can check Why and when we must use (install) redis ?

We have reproduced this problem. As a workaround, you can set default api URL to productService in environment.ts when generating proxy like:

export const environment = {
  ...
  apis: {
    default: {
      url: 'https://localhost:44361',
      rootNamespace: 'MyMicroApp',
    },
    AbpAccountPublic: {
      url: oAuthConfig.issuer,
      rootNamespace: 'AbpAccountPublic',
    },
    ProductService: {
      url: 'https://localhost:44325',
      rootNamespace: 'MyMicroApp',
    },
  },
} as Environment;

Note: Don't forget to revert back to web-gateway.

I have refunded your question.

Thank you for your report.

[00:46:46 ERR] An unhandled exception has occurred while executing the request. System.InvalidOperationException: IDX20803: Unable to obtain configuration from: 'System.String'. ---> System.IO.IOException: IDX20804: Unable to retrieve document from: 'System.String'. ---> System.Net.Http.HttpRequestException: Connection refused (auth.fa.cn:80)

You application can not reach IdentityServer at auth.fa.cn:80. If you want to use cluster service names, you can set Public Origin. Please check IdentityServer deployment on Kubernetes guide.

If you want to build your image locally, see my answer for dockerfile.

dotnet dev-certs https -v -ep /app/identityserver.pfx -p 2D7AA457-5D33-48D6-936F-C48E5EF468ED

This doesn't work for production, it only generates certificate for localhost.

If you are publishing to Azure, you can use free azure HTTPS certificates. Or you can generate a self-signed certificate for your application. You can check how to generate self-signed certificate using openssl.

If you are publishing IdentityServer, you can check IdentityServer Deployment docs.