Cannot accept user to an organization using docker image

[ahaw]

When I try to approve the user I get the error message "An error has occurred.
An unexpected error has occurred.".
I was able to approve a single user but nothing after it.

I tried to check logs but nothing I don't see there anything relevant.

My docker compose file:

 bitwarden:
#  entrypoint: ["echo", "Service bitwarden disabled"]
  restart: always
  container_name: bitwarden
  image: bitwardenrs/server:alpine
  hostname: bitwarden
  volumes:
   - ./bitwarden/:/data/
  environment:
   - WEBSOCKET_ENABLED=false
   - SIGNUPS_ALLOWED=false
   - ADMIN_TOKEN=<token>
   - DOMAIN=https://mydomain.com/bw
   - LOG_LEVEL=trace
   - EXTENDED_LOGGING=true

Im also using envoy proxy to forward https traffic (no wss proxying as I thought it's unneded)

static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address:
        address: 0.0.0.0
        port_value: 10000
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          access_log:
          - name: envoy.access_loggers.file
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.access_loggers.file.v3.FileAccessLog
              path: /dev/stdout
          http_filters:
          - name: envoy.filters.http.router
          route_config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains: ["*"]
              routes:
              - match:
                  prefix: "/bw/"
                route:
                  host_rewrite_literal: bitwarden
#                  prefix_rewrite: "/"
                  cluster: bitwarden
      transport_socket:
        name: envoy.transport_sockets.tls
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.DownstreamTlsContext
          common_tls_context:
            tls_certificates:
              - certificate_chain:
                {
                  filename: "/certs/fullchain1.pem"
                }
                private_key:
                {
                  filename: "/certs/privkey1.pem"
                }
  clusters:
  - name: bitwarden
    connect_timeout: 30s
    type: LOGICAL_DNS
    dns_lookup_family: V4_ONLY
    load_assignment:
      cluster_name: bitwarden
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: bitwarden
                port_value: 80

[BlackDex]

Please provide some bitwarden logs from the tone during those errors

[ahaw]

Here is the link to the logs:
https://pastebin.pl/view/3c105d38
There is also log from browser
https://pastebin.pl/view/ce392f77
Strange is that it tries to connect to websocket

[BlackDex]

I do not see an attempt to approve a org user.
The only error's i see is that you do not have WebSockets enabled, which is valid.

Wee need the logs of the exact same time you get that error message in the web-interface.

[ahaw]

Here is the link: https://pastebin.ubuntu.com/p/7dVPS8W6jk/
Logs contains actions from opening dropdown to clicking cofirm in new window.

There is no call to bw server from browser and no logs when clicking the button

[BlackDex]

Then it will be hard for us to help since we only program the server backend.

The only place where i can think of there could be an issue is the reverse proxy. Since you are using a sub-psth. If there is something not configured correctly it could cause strange issues.

I'm not familiar with envoy, but could you post the config of that.

[ahaw]

@BlackDex
I updated first post and added envoy config. Ill try to use bithwarden_rs without reverse proxy

[ahaw]

I found the issue. If I dont restrict to collections it works correctly. I believe it's a bug afterall

[BlackDex]

So, the user you wanted to accept was restricted via the only selected collections, and you had no collections checked, correct?

[ahaw]

Nope, I tried different variants. All of them failed when I had checked collection. Hide password and readonly checkboxes were not important