Unable to configure SSO on self-hosted environment

I am having trouble configuring SSO on our self-hosted Bitwarden environment.
When trying to authenticate I am getting the following error message: Error pre-validating SSO authentication.
I am getting the exact same error message when using OIDC or SAMLv2.

Exception from the identity pod:

fail: Bit.Identity.Controllers.AccountController[0] ││ => SpanId:93dcecde9806bd46, TraceId:f66f63c43ff69d46a0621238937437b1, ParentId:0000000000000000 => ConnectionId:0HMCVJLO4N5H2 => RequestPath:/account/prevalidate RequestId:0HMCVJLO4N5H2:00000002 => B ││ Error pre-validating against SSO service ││ System.Net.Http.HttpRequestException: Name or service not known (sso:5000) ││ —> System.Net.Sockets.SocketException (0xFFFDFFFF): Name or service not known ││ at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken) ││ at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token) ││ at System.Net.Sockets.Socket.g__WaitForConnectWithCancellation|283_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken) ││ at System.Net.Http.HttpConnectionPool.DefaultConnectAsync(SocketsHttpConnectionContext context, CancellationToken cancellationToken) ││ at System.Net.Http.ConnectHelper.ConnectAsync(Func3 callback, DnsEndPoint endPoint, HttpRequestMessage requestMessage, CancellationToken cancellationToken) ││ --- End of inner exception stack trace --- ││ at System.Net.Http.ConnectHelper.ConnectAsync(Func3 callback, DnsEndPoint endPoint, HttpRequestMessage requestMessage, CancellationToken cancellationToken) ││ at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) ││ at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) ││ at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) ││ at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken) ││ at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) ││ at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) ││ at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ││ at Microsoft.Extensions.Http.Logging.LoggingScopeHttpMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ││ at System.Net.Http.HttpClient.SendAsyncCore(HttpRequestMessage request, HttpCompletionOption completionOption, Boolean async, Boolean emitTelemetryStartStop, CancellationToken cancellationToken) ││ at Bit.Identity.Controllers.AccountController.PreValidate(String domainHint) in /home/runner/work/server/server/src/Identity/Controllers/AccountController.cs:line 68

Does someone have any clue what could be the cause of this issue?

Let me know if there’s any other information required.