Activities of "liangshiwei"

Hi,

The problem was fixed: https://github.com/abpframework/abp/issues/13023

You can try upgrading to the latest version(abp 7.0.2 & themex 2.0.2)

Hi.

Can you share the error log? thanks.

HI,

I guess it's an invalid certificate.

However, you can try this to ignore the error:

public override void PreConfigureServices(ServiceConfigurationContext context)
{
    PreConfigure<AbpHttpClientBuilderOptions>(options =>
    {
        options.ProxyClientBuildActions.Add((_, clientBuilder) =>
        {
            var client = new HttpClientHandler 
            { 
                    ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator 
            };) 
            clientBuilder.ConfigurePrimaryHttpMessageHandler(client);
        });
    });
}

Hi,

Could you share the full steps to reproduce the problem? thanks.

Hi,

Please share the full logs(blazor, httpapi.host, authserver)

Hi,

Yes, the abp suite doesn't support it, you should configure it manualy

Is it possible to deploy abp to azure with openiddict without the need to have self signed certificates?

I think there is this way, but we don't recommend you to do it in production

ok

inequivalent arg 'x-dead-letter-exchange' for queue 'AppV3_AdministrationService' in vhost '/': received none but current is the value 'AppV3_dead_letter' of type 'longstr''

That means that you have a AppV3_AdministrationService queue on the broker already and it is without an 'x-dead-letter-exchange' argument. Probably you have created it before with that state.

You can remove all RabbitMQ queues and try again.

Hi,

Ok, please. shiwei.liang@volosoft.com