Skip to content

Turn off IPv6 support #2277

Description

@duckunix

Is there a way to disable the need for IPv6 when running trustd-pm? My test environment has a restriction against running IPv6, and it errors out on start up. Error below:

 ./trustd-pm 
RUST_LOG is unset, using default: 'info'
2026-03-06T21:04:49.881095Z  WARN ThreadId(01) trustd::db: Setting up managed DB; not suitable for production use!
2026-03-06T21:04:49.990612Z  INFO ThreadId(01) trustd::db: PostgreSQL installed in "/tmp/f/.trustify/postgres"
2026-03-06T21:04:49.990651Z  INFO ThreadId(01) trustd::db: Running on port 36189
2026-03-06T21:04:50.297715Z  INFO ThreadId(01) migrate: sqlx::postgres::notice: relation "seaql_migrations" already exists, skipping
2026-03-06T21:04:50.297786Z  INFO ThreadId(01) migrate: sea_orm_migration::migrator: Applying all pending migrations
2026-03-06T21:04:50.297969Z  INFO ThreadId(01) migrate: sqlx::postgres::notice: relation "seaql_migrations" already exists, skipping
2026-03-06T21:04:50.298107Z  INFO ThreadId(01) migrate: sqlx::postgres::notice: relation "seaql_migrations" already exists, skipping
2026-03-06T21:04:50.298289Z  INFO ThreadId(01) migrate: sqlx::postgres::notice: relation "seaql_migrations" already exists, skipping
2026-03-06T21:04:50.300277Z  INFO ThreadId(01) migrate: sea_orm_migration::migrator: No pending migrations
2026-03-06T21:04:50.301336Z  INFO ThreadId(01) trustify_infrastructure::infra: OTEL_EXPORTER_OTLP_ENDPOINT = None
2026-03-06T21:04:50.301412Z  WARN ThreadId(01) trustify_server::embedded_oidc: Running embedded OIDC server. This is not secure and should only be used for demos!
2026-03-06T21:04:50.301438Z  INFO ThreadId(01) trustify_infrastructure::infra: OTEL_EXPORTER_OTLP_ENDPOINT = None
2026-03-06T21:04:50.303002Z  INFO ThreadId(02) trustify_server::embedded_oidc: Running server loop
2026-03-06T21:04:50.303098Z ERROR ThreadId(02) trustify_server::embedded_oidc: Embedded OIDC server terminated: Address family not supported by protocol (os error 97)
Error: waiting for embedded OIDC server to start
Caused by:
        channel closed

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions