[Bug]: Cannot login into an instance with the provided login credentials

[jaishsphereops]

Deployment Type / 部署类型

Self-hosted (Docker)

Bug Description / Bug 描述

I want to login after deploying super magic with the official guide (via docker) but it doesn't login with either of the provided credentials.

Steps to Reproduce / 复现步骤

1. Clone the repo and cd into it.
2. Copy the config files from their example counterparts.
3. Change the port for caddy in docker-compose.yaml (because it was conflicting) to 5000
4. Run ./bin/magic.sh start to initialize and choose English and Local.
5. Open server-ip:5000 to access the login page in the browser.
6. Enter 13912345678 or 13812345678 for phone number and letsmagic.ai for password.
7. Press Login (and it doesn't work)

Logs and Additional Context / 日志和额外的上下文

No response

[jaishsphereops]

When I look up in the network tab

{
"redirect": "http://37.27.181.0:5000/login?redirect=http%3A%2F%2F37.27.181.0%3A5000%2F",
"state_code": "+86",
"phone": "86413141242",
"password": "sgdhgjfjfj",
"device": {
"id": "f15455f642f033113106adf18e3d0db9d78e058cb4eac993c0a9442bbff9a794",
"name": "Chrome 139.0.0.0",
"os": "Windows",
"os_version": "10"
},
"type": "phone_password"
}

for sessions with a return code of 404 and CORS

[jaishsphereops]

Console

Access to fetch at 'http://37.27.181.0/api/v1/sessions' from origin 'http://magic.sphereops.org:5000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

[Rock-520]

You can remove the "Access-Control-Allow-Origin" restriction by modifying the configuration of the caddy server.

[jaishsphereops]

You can remove the "Access-Control-Allow-Origin" restriction by modifying the configuration of the caddy server.

It's already set to "*"... What do I do now? Would really appreciate help