Traefik Proxy settings

Traefik Traefik v2
1

I am currently working on setting up a Traefik proxy for my services, including a Wiremock service, and I have encountered an issue that I can't seem to resolve on my own. . Below is my api.yml file:

http:
  routers:
    api:
      entryPoints:
      - web
      service: api
      rule: "PathPrefix(`/`)"
      priority: 1
    
    wiremock:
      entryPoints:
      - web
      service: wiremock
      rule: "PathPrefix(`/wiremock`)"
      middlewares:
      - strip-wiremock-prefix
      priority: 2
    
    wiremock-admin:
      entryPoints:
      - web
      service: wiremock-admin
      rule: "PathPrefix(`/wiremock/__admin`)"
      middlewares:
      - strip-wiremock-admin-prefix
      priority: 3
    
  services:
    api:
      loadBalancer:
        servers:
        - url: http://api.default.local:8000
        passHostHeader: true
    
    wiremock:
      loadBalancer:
        servers:
        - url: http://worker-wiremock.default.local:9090
        passHostHeader: true
    
    wiremock-admin:
      loadBalancer:
        servers:
        - url: http://worker-wiremock.default.local:9090
        passHostHeader: true

  middlewares:
    strip-wiremock-prefix:
      stripPrefix:
        prefixes:
        - /wiremock

traefik.yml -

ping: {}

providers:
  # ecs:
  #   autoDiscoverClusters: false
  #   exposedByDefault: false
  file:
    # directory: /etc/traefik-providers
    filename: /etc/traefik-providers/api.yml

entryPoints:
  web:
    address: ":80"

log:
  level: DEBUG
  filePath: "/etc/traefik/traefik.log"


accessLog:
  filePath: "/etc/traefik/access.log"

the pages for api service are loading well but for wiremock either it is displaying 403 forbidden error or redirecting to single page for all sub pages.
I would greatly appreciate any guidance or assistance you can provide, let me know if you need more details.

2

Is wiremock a web GUI app?

You can not just place a web GUI app under a path, even when removing the path prefix.

The initial page will usually include links and scripts with absolute paths (like /static/script.js), so can’t be loaded that way.

You can only use a path prefix when the web app supports setting some kind of "base path".

That’s why sub-domains are best practice.