Activities of "Sergei.Gorlovetsky"

Hello, I am trying to deploy the backend into an Azure App service (Linux) customer container—not a docker.

I am facing this startup failure issue related to ports.

I also have, put environment variables PORT, WEBSITES_PORT, ASPNETCORE_HTTP_PORTS with value such as 80,8000,8080 but nothing works.

How do I fix this, can I get some help please ?

2024-09-19T04:19:00.859Z INFO - docker run -d --expose=8080 --name econsent-staging-api_0_54294e83 -e WEBSITE_USE_DIAGNOSTIC_SERVER=true -e WEBSITES_PORT=8080 -e WEBSITE_SITE_NAME=econsent-staging-api -e WEBSITE_AUTH_ENABLED=False -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=econsent-staging-api-hhdzezc7h4gfabcn.canadacentral-01.azurewebsites.net -e WEBSITE_INSTANCE_ID=0d5668f121ac94cc42d5df8f8ef98a91f96d44ffa9020693b531b2188a4ede59 -e ASPNETCORE_HOSTINGSTARTUPASSEMBLIES=Microsoft.ApplicationInsights.StartupBootstrapper -e DOTNET_STARTUP_HOOKS=/agents/core/StartupHook/Microsoft.ApplicationInsights.StartupHook.dll appsvc/dotnetcore:8.0_20240819.2.tuxprod 2024-09-19T04:19:00.861Z INFO - Logging is not enabled for this container. Please use https://aka.ms/linux-diagnostics to enable logging to see container logs here. 2024-09-19T04:19:02.560Z INFO - Initiating warmup request to container econsent-staging-api_0_54294e83 for site econsent-staging-api 2024-09-19T04:19:13.995Z ERROR - Container econsent-staging-api_0_54294e83 for site econsent-staging-api has exited, failing site start 2024-09-19T04:19:14.013Z ERROR - Container econsent-staging-api_0_54294e83 didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging. 2024-09-19T04:19:14.025Z INFO - Stopping site econsent-staging-api because it failed during startup. 2024-09-19T04:26:07.480Z INFO - Starting container for site

I understand 401 means unauthorized. I just wanted to show a Text-based response with 401. But I think it won't be possible then.

You can close the ticket. Thanks

I am not using UI for this one. My UI is just for tenant management. I am sharing API to be used by other integrations(outside of this project).

• ABP Framework version: v8.0
• UI Type: Angularr
• Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes

I am creating API and using bearer token to authenticate the API requests.

I have used [Authorize] in my controller class and method. When I try to execute the API with the invalid token, in the logs I see the error message that says invalid token or token no longer valid.

But in the postman, I just see 401 unauthorized. However, I want to show a user-facing error message about an invalid token.

It returns 404 once I remove them from the wwwroot folder . Did I miss something here?

Yes indeed I am able to reach it with a get request locally, that is because i do have the files under the wwwroot folder which it is referencing to? In this case, I guess the solution is to commit these files into our repository

The thing is that the files are not able to be generated even though we already ran this command(both locally and on the pipeline). Let's say we run this command in our root folder, can it detect the module itself and install the corresponding library for them as well? If not where should we run the command for the modules? Any suggestion?

Seems like I added this line into my .gitignore file a while back, that's why those js files are never committed to my remote repository.

What do you recommend on this? Should I commit them? Or is there a command I can generate them instead

If you say they are removed in the newer version, does that mean these two pages are no longer available? Do you think we should upgrade our project abp version again?

Hi, after some testing, we figure out that we are not able to access to these two pages after commenting out those two lines

so these two files are sitting under here(this is my local env and i don't know how they are being generated)

I am pretty sure these files are generated by abp install-libs command right? but we are not able to run it in the Account.Pro project