Can't register to system, receives 404

**Describe the bug**
After installing the deepfence-console chaert (v1.4.7) and modifying it's value so it'll feet our needs, the register function returns code 404 both when trying to access port-forwarding and when trying to access from the registered domain name.

**To Reproduce**
Steps to reproduce the behavior:
1. Set the TLS map in the values.yaml file to use an existing certificate secret
2. Deploy the chart to the kubernetes cluster
3. Set port-forwarding to to the deepfence-ui service on port 4042
4. Try to register
5. See the error

**Expected behaviour**
Expected behaviour is to be registered and being able to log in

**Screenshots**

**Components/Services affected**

- [ ] UI/Frontend
- [ ] API/Backend

**Additional context**
I don't see anyone else is experiencing this issue.
I also tried to deploy an older version (v1.4.0) with no success.

I have a Traefik IngressRoute facing the deepfence-ui service and it's exposed fine.

When I tried to access the following path: "deepfence/v1.5/users/register" under the deepfence-api service I received a response, is it possible there's a problem with the internal-router service?

Also, no logs are produced in the deepfence ui when I'm accessing it, though the UI under path "/" is reachable.