middleware | core software that uses semantic matchmaking | Pub Sub library

So i have a 404 handler and a router file:

404 handler:

so im developing website using nodejs, and then deploying it to microsoft azure, and using Azure Database for mysql server to be exact, and importing my databse using mysql workbench, now the problem is in the CORS, everyhting going well i run it on chrome and firefox in the same pc works fine, but when i try to acces the website using another pc, i get the error says "Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:3000/data/price%20asc. (Reason: CORS request did not succeed)".

heres my nodejs code:

I am already making a restful API using nodejs on the backend, here is my folder structure :

I don't really know where the error is, for me, it's still a mystery. But I'm using Laravel 8 to produce a project, it was working perfectly and randomly started to return this error and all projects started to return this error too. I believe it's something with Redis, as I'm using it to store the system cache. When I go to access my endpoint in postman it returns the following error:

I've started a new project using .Net 5 (my previous was .Net Framework 4.7). I'm writing a web API project and I want all my controllers/action responses to be of a certain type. This allows me to put some info I want included in every response, such as the current user info (and more stuff too). My generic response looks like this (I've only left the relevant code):

i am using django default user model created UserExtended model for storing extra details of user so that I can store extra user data and call them when needed

here is the model

I am getting Request Failed error when I am tying to logging in through frontend:

But, I am able to, when I am entering emailID and password through thunder client:

I am entering correct ID and password here is my request:

but what I am getting in return is:

Here is my source code:

userAction.js

I have an OpenID Connect server (OpenIDdict) and an asp.net core webapp in containers behind a TLS termination proxy. In production, all communication between the webapp and the OIDC server can go through the 'outside', based on their public names. However, in development, I'm using self signed certificates that aren't trusted by the containers running the apps, only by my host pc. Because of that, in development, the webapp can redirect the browser to the OIDC server just fine, but when it, for instance, needs to call the token endpoint, it will fail, because the certificate isn't trusted.

A possible solution would be to have the server to server communication go through the internal container network, but I haven't been able to get that to work. Is there a way to make the asp.net core OpenID Connect middleware use a different url (and protocol) for server to server communication?

Another solution would be to install the self signed certificates in the containers, but because that's only needed in development, it seems bad practice to burden the images with that. Is that assessment correct?

I'm hoping I'm missing the most obvious solution. Any ideas?

My code doesn't work. I use Laravel framework. Error on the picture. I think maybe it's looping

config/app: