Is your problem fixed? if yes, how it was fixed?
@ugur did the @maliming's answer solve your problem? if yes could you please mark the answer as solution
could you tell us how did you solve your issue?
Ok I see the issue. @summeyye will check this issue
or try Rider to see if this is directly related to the ABP source-code
probably authentication server address or port is wrong. this one
what's your backend logs?
normally this happens when your startup project doesn't have AbpLicenseCode. There's a simple check if you properly include the license code config in your host project. run the following code, when AbpLicenseCode is not empty it'll not throw any exception.
var configuration = Microsoft
.Extensions
.DependencyInjection
.ServiceProviderServiceExtensions
.GetRequiredService<Microsoft.Extensions.Configuration.IConfiguration>(context.ServiceProvider);
var licenseCode = configuration["AbpLicenseCode"];
Also check this => https://abp.io/support/questions/8633/
In ABP, when you set AbpClockOptions.Kind to DateTimeKind.Utc and configure the Abp.Timing.TimeZone setting, the framework is designed to display times in the user's or application's configured time zone throughout the UI, including logs. But it writes in UTC format to the server.
The correct approach is to use both:
AbpClockOptions.Kind = DateTimeKind.Utc (to ensure all times are stored and handled as UTC)Npgsql.EnableLegacyTimestampBehavior (for PostgreSQL compatibility)If the audit logs page is not converting UTC times to the user's time zone, this can be bug . Other pages, such as the security logs, already use the time zone setting as expected.
You are configuring time zones correctly in your application. No further changes are needed to your settings. The issue is with the audit logs page not applying the time zone conversion, and this should be reported to the ABP team for correction.
Send us related screenshots.
thank you for the feedback
