v1.6.1

New Features

• TCP middlewares on TCP routes - the TCP route form now has a Middlewares chip selector (like HTTP routes) offering the TCP middlewares from your config; selections are written to the TCP router. Existing middlewares are preserved when a route is edited from a client without the new field. Works for the Host and remote agents.
• TCP middlewares in the Add/Edit Middleware modal - a new HTTP / TCP protocol switcher (like the route modal) writes TCP middlewares to tcp.middlewares. TCP mode is YAML-only (Traefik supports ipAllowList and inFlightConn for TCP) and the body is validated. Editing can move a middleware between protocols, and deleting now works for both. Pasting a full http:/tcp: config block as a middleware body is rejected with a clear error instead of writing broken config. Works for the Host and remote agents.

Bug Fixes

• Fixed the CrowdSec Unban button silently failing (fixes #90) - the delete handler referenced a non-existent CSRF helper, so the request never left the browser. The CSRF token was already attached automatically; the broken manual header is removed and unban works again for the Host and remote agents.
• Fixed TCP middlewares not appearing on the Middlewares tab - middlewares defined under tcp.middlewares are now collected and shown with the TCP badge and filter. Thanks @adrianrp1988 (#91).
• Fixed middlewares attached to TCP routes not being shown on the route cards or returned by the routes API. Thanks @adrianrp1988 (#92).
• Fixed TCP route middlewares missing from the route details panel and from disabled TCP routes (host and agent). Thanks @adrianrp1988 (#94).
• Fixed "+ New file..." in the route and middleware modals being preselected by default in directory mode, which hid the file name input and silently saved to dynamic.yml. The first config file is now preselected, and explicitly choosing "+ New file..." shows the name input. Applies to the Host and remote agents.
• Fixed the broken UI on Linux service (systemd) installs (fixes #93) - setup-assets.sh compiled Tailwind relative to the caller's working directory, so installs via the setup script produced a stylesheet with no utility classes. The script now runs from the repo root regardless of where it is invoked, no longer needs sudo (the tailwindcss binary falls back to a temp location), and fails loudly if the compiled CSS is empty. Existing broken installs are fixed by cd /opt/traefik-manager && bash scripts/setup-assets.sh && sudo systemctl restart traefik-manager.