Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

```relation "networks" already exists (SQLSTATE 42P07)
error executing migrations/20150101000001000000_networks.postgres.up.sql, sql: -- Migration generated by the command below; DO NOT EDIT.```

you're probably using same database for both Hydra and Kratos. so unlike usually, where a `hydra_` prefix is used, hydra introduced `networks` table which is pretty much same table as in kratos. you can temporarily rename kratos's table, then run your migrations, then copy nid data from kratos's networks over to hydra's networks, then fix all the foreign keys in kratos tables to reflect the change, but then it still will not work, because ory expects network to contain only a single nid record.

this is messed up.