[GH-ISSUE #35] Adding tpc router ignores ip, port and tls selection #33

New issue

Closed

opened 2026-05-06 12:22:51 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-06 12:22:51 +02:00

Owner

Originally created by @mentalsoup on GitHub (May 4, 2026).
Original GitHub issue: https://github.com/chr0nzz/traefik-manager/issues/35

Originally assigned to: @chr0nzz on GitHub.

Traefik Manager version

v1.0.0

How are you running Traefik Manager?

Docker

Traefik version

v3.6.15

What happened?

Created a new tcp route saving to unique file but the the ip, port and tls options selected did not match my choices after saving.

Steps to reproduce

click button "add route"
use new file option, set name
select tcp protocol
enter name, sni, ip, port (use 443), entry point (websecure)
do not select enable tls
save

What did you expect to happen?

I expected the file output to appear as follows:

tcp:
  routers:
    test:
      rule: HostSNIRegexp(`test.domain.com`) || HostSNIRegexp(`{subdomain:[a-z]+}.test.domain.com`)
      entryPoints:
        - websecure
      tls:
        passthrough: true
      service: test-service
  services:
    test-service:
      loadBalancer:
        servers:
          - address: "192.168.*.***:443"

Actual output:

tcp:
  routers:
    test:
      rule: HostSNIRegexp(`test.domain.com`) || HostSNIRegexp(`{subdomain:[a-z]+}.test.domain.com`)
      entryPoints:
        - websecure
      tls:
        certResolver: letsencrypt
      service: test-service
  services:
    test-service:
      loadBalancer:
        servers:
          - address: ':'

Relevant logs or screenshots

No indication of any problem in the console output of the tm container.

Relevant configuration

Originally created by @mentalsoup on GitHub (May 4, 2026). Original GitHub issue: https://github.com/chr0nzz/traefik-manager/issues/35 Originally assigned to: @chr0nzz on GitHub. ### Traefik Manager version v1.0.0 ### How are you running Traefik Manager? Docker ### Traefik version v3.6.15 ### What happened? Created a new tcp route saving to unique file but the the ip, port and tls options selected did not match my choices after saving. ### Steps to reproduce 1. click button "add route" 2. use new file option, set name 3. select tcp protocol 4. enter name, sni, ip, port (use 443), entry point (websecure) 5. do not select enable tls 6. save ### What did you expect to happen? I expected the file output to appear as follows: ``` tcp: routers: test: rule: HostSNIRegexp(`test.domain.com`) || HostSNIRegexp(`{subdomain:[a-z]+}.test.domain.com`) entryPoints: - websecure tls: passthrough: true service: test-service services: test-service: loadBalancer: servers: - address: "192.168.*.***:443" ``` Actual output: ``` tcp: routers: test: rule: HostSNIRegexp(`test.domain.com`) || HostSNIRegexp(`{subdomain:[a-z]+}.test.domain.com`) entryPoints: - websecure tls: certResolver: letsencrypt service: test-service services: test-service: loadBalancer: servers: - address: ':' ``` ### Relevant logs or screenshots ```shell No indication of any problem in the console output of the tm container. ``` ### Relevant configuration ```yaml ```

BreizhHardware

2026-05-06 12:22:51 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-06 12:22:52 +02:00

Author

Owner

@chr0nzz commented on GitHub (May 4, 2026):

thanks for the bug report, fix is been pushed please update

docker compose pull && docker compose up -d

@chr0nzz commented on GitHub (May 4, 2026): thanks for the bug report, fix is been pushed please update `docker compose pull && docker compose up -d`

BreizhHardware commented

2026-05-06 12:22:52 +02:00

Author

Owner

@mentalsoup commented on GitHub (May 5, 2026):

updated to v1.0.2. fix confirmed. thanks for the swift resolution!

@mentalsoup commented on GitHub (May 5, 2026): updated to v1.0.2. fix confirmed. thanks for the swift resolution!

BreizhHardware commented

2026-05-06 12:22:53 +02:00

Author

Owner

@chr0nzz commented on GitHub (May 5, 2026):

my pleasure bud, happy its working. if you come across any more bugs please open a new issue thanks

@chr0nzz commented on GitHub (May 5, 2026): my pleasure bud, happy its working. if you come across any more bugs please open a new issue thanks