Not proceed after /initialize method called on FQDN and TLS

[letusfly85]

Checklist

• I could not find a solution in the existing issues or docs.
• I agree to follow this project's Code of Conduct.

Describe the bug

Hi, thank you for great solution.

We're now trying hosting this service on our AWS.
For the first step, we tried serving frontend/examples/react by using docker-compose.

Especially, we want to try webauthn processes.

But when we service processes by using docker-compose.yml and Let's Encrypt and several reverse proxies,
we cannot proceed to some steps after /initialize POST method called, the method returns 200OK, but it doesn't proceed to next steps..

On localhost, it works perfectly.
But on FQDN and TLS environment, it doesn't work.

Is there any way to proceed...? or should we create our own frontend processes from scratch..?

Reproducing the bug

1. replace hostnames on yml

cat -p deploy/docker-compose/config.yaml

database:
  user: hanko
  password: hanko
  host: postgresd
  port: 5432
  dialect: postgres
passcode:
  email:
    from_address: [email protected]
  smtp:
    host: "mailslurper"
    port: "2500"
secrets:
  keys:
    - **************************
service:
  name: Hanko Authentication Service
server:
  public:
    cors:
      enabled: true
      allow_credentials: true
      allow_origins:
        - '*'
webauthn:
  relying_party:
    origin: "https://MY_HOST_NAME"
session:
  cookie:
    secure: false

2. run processes

docker compose -f deploy/docker-compose/quickstart.yaml  -p "hanko-quickstart" up --build

Logs

There are no logs on Chrome/Safari inspectors after `/initialize` method.`

Configuration

No response

Hanko Version

0fca4c0

OS

Linux

OS Version

Ubuntu 20.04 TLS

Browser Version

Chrome 112.0.5615.49（Official Build） （x86_64）

Environment

Docker Compose

Additional Context

No response

[like-a-bause]

Hi there,
we can't quite figure out what is going wrong on your side.
On which OS/Browser is the client running?
Are there any backend logs that indicate what is going on?