-
Notifications
You must be signed in to change notification settings - Fork 47
Turn off IPv6 support
#2278
-
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月06日T21:04:49.881095Z WARN ThreadId(01) trustd::db: Setting up managed DB; not suitable for production use!
2026年03月06日T21:04:49.990612Z INFO ThreadId(01) trustd::db: PostgreSQL installed in "/tmp/f/.trustify/postgres"
2026年03月06日T21:04:49.990651Z INFO ThreadId(01) trustd::db: Running on port 36189
2026年03月06日T21:04:50.297715Z INFO ThreadId(01) migrate: sqlx::postgres::notice: relation "seaql_migrations" already exists, skipping
2026年03月06日T21:04:50.297786Z INFO ThreadId(01) migrate: sea_orm_migration::migrator: Applying all pending migrations
2026年03月06日T21:04:50.297969Z INFO ThreadId(01) migrate: sqlx::postgres::notice: relation "seaql_migrations" already exists, skipping
2026年03月06日T21:04:50.298107Z INFO ThreadId(01) migrate: sqlx::postgres::notice: relation "seaql_migrations" already exists, skipping
2026年03月06日T21:04:50.298289Z INFO ThreadId(01) migrate: sqlx::postgres::notice: relation "seaql_migrations" already exists, skipping
2026年03月06日T21:04:50.300277Z INFO ThreadId(01) migrate: sea_orm_migration::migrator: No pending migrations
2026年03月06日T21:04:50.301336Z INFO ThreadId(01) trustify_infrastructure::infra: OTEL_EXPORTER_OTLP_ENDPOINT = None
2026年03月06日T21: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月06日T21:04:50.301438Z INFO ThreadId(01) trustify_infrastructure::infra: OTEL_EXPORTER_OTLP_ENDPOINT = None
2026年03月06日T21:04:50.303002Z INFO ThreadId(02) trustify_server::embedded_oidc: Running server loop
2026年03月06日T21: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
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 1 comment
-
IIRC you can control this by the bind address. Which is defaulting to ::1, meaning (local-loopback IPv6) and should bind to both v4 and v6.
You can use HTTP_SERVER_BIND_ADDR or --http-server-bind-address to override this. Setting it to 127.0.0.1 should bind this to "IPv4 localhost".
Btw, you can also use :: (IPv6 any) and 0.0.0.0 (IPv4 any).
Beta Was this translation helpful? Give feedback.
All reactions
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment