Nextcloud signaling server (HPB) high performance backend setup

Im setting up a Nextcloud High Performance Backend(HPB) on a docker swarm cluster behind traefik. ive been rackin my brain and fingers trying to troubleshoot the whole stack together. I think i've come to the last part of the stack. I am able to get it working using docker-compose.yaml and simple docker-compose up instance that uses nginx standalone- that seems to be working- i also have a docker swarm instance that i can't get working that is using traefik in the front- ive tried to fwd traffic through to HPB to an nginx instance container in the swarm stack to no avail and also directly to the spreedbackend container on spreedbackend:8080. before i get into my configs - id like to know how i should configure traefik to mirror/mimick the configuration of nginx or caddy in the HPB documentation- nextcloud-spreed-signaling/README.md at master · strukturag/nextcloud-spreed-signaling · GitHub - this is a snip re: the caddy config:

Caddy

v1

Caddy (v1) configuration:

myserver.domain.invalid {
  proxy /standalone-signaling/ http://127.0.0.1:8080 {
    without /standalone-signaling
    transparent
    websocket
  }
}

v2

Caddy (v2) configuration:

myserver.domain.invalid {
  route /standalone-signaling/* {
    uri strip_prefix /standalone-signaling
    reverse_proxy http://127.0.0.1:8080
  }
}

again, the nginx frontend to the backend in a non-swarm stack works but i use traefik for the swarm and would like to replace nginx completely if possible.

its seems quite simple but at this point i've lost confidence in my ability to troubleshoot this further- perhaps i'm missing some websocket / proxypass magic somewhere? Im super grateful for any guidance anyone can provide!

-chefboyrdave2.1 aka DaveK

See Nextcloud high performance backend with nginx proxy_pass - #7 by bluepuma77