[ taxy ] A reverse proxy server with built-in WebUI
Re: [ taxy ] A reverse proxy server with built-in WebUI
TOS6 version is updated to latest version 0.3.35
Re: [ taxy ] A reverse proxy server with built-in WebUI
/taxy: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by ./taxy)
ERROR!
taxy is stopped.
Autostart on boot is Enabled
installed version is 0.3.35.0
Using 0.3.34.0 just flashes after the login screen terra terra and goes back to the login screen. If I inspect the page, I get
taxy-webui-8999a689fcba2446.js:372
GET http://192.168.8.200:46492/api/ports 401 (Unauthorized)
Thanks in advance.
ERROR!
taxy is stopped.
Autostart on boot is Enabled
installed version is 0.3.35.0
Using 0.3.34.0 just flashes after the login screen terra terra and goes back to the login screen. If I inspect the page, I get
taxy-webui-8999a689fcba2446.js:372
GET http://192.168.8.200:46492/api/ports 401 (Unauthorized)
Thanks in advance.
- Terrariaria
- Posts: 18
- Joined: 12 Jun 2025, 20:02

Re: [ taxy ] A reverse proxy server with built-in WebUI
thread 'main' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/taxy-0.3.35/src/admin/mod.rs:141:10:
Path segments must not start with `:`. For capture groups, use `{capture}`. If you meant to literally match a segment starting with a colon, call `without_v07_checks` on the router.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
ERROR!
Path segments must not start with `:`. For capture groups, use `{capture}`. If you meant to literally match a segment starting with a colon, call `without_v07_checks` on the router.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
ERROR!
- EthanBerg97
- Posts: 14
- Joined: 20 Feb 2025, 19:06

Re: [ taxy ] A reverse proxy server with built-in WebUI
Unbelievably helpful and clear - learned tons! I can't thank you enough... MASSIVE THANK YOU!!
Re: [ taxy ] A reverse proxy server with built-in WebUI
Hi, I have the exact same issue here! My TOS version is: 6.0.794 Did you find any information / solutions or tips to get over this?Terrariaria wrote: ↑22 Jun 2025, 08:35 thread 'main' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/taxy-0.3.35/src/admin/mod.rs:141:10:
Path segments must not start with `:`. For capture groups, use `{capture}`. If you meant to literally match a segment starting with a colon, call `without_v07_checks` on the router.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
ERROR!
Best regards

