[GH-ISSUE #4815] tcpmux error

gitea-mirror commented

2026-05-05 14:25:56 -06:00

Owner

Copy link

Originally created by @yzdiyu on GitHub (May 26, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4815

Bug Description

frpc Version

0.62.1

frps Version

0.62.1

System Architecture

linux/amd64

Configurations

proxies
name = "ssh1"
type = "tcpmux"
multiplexer = "httpconnect"
customDomains = ["machine-a.example.com"]
localIP = "127.0.0.1"
localPort = 22

frps.toml----
bindAddr = "0.0.0.0"
bindPort = 7000
tcpmuxHTTPConnectPort = 7900

Logs

No response

Steps to reproduce

...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @yzdiyu on GitHub (May 26, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4815 ### Bug Description <html> <body>  ssh1 | tcpmux | 127.0.0.1:22 | | | start error | tcpmux with multiplexer httpconnect not supported because this feature is not enabled in server  </body> </html> ### frpc Version 0.62.1 ### frps Version 0.62.1 ### System Architecture linux/amd64 ### Configurations [[proxies]] name = "ssh1" type = "tcpmux" multiplexer = "httpconnect" customDomains = ["machine-a.example.com"] localIP = "127.0.0.1" localPort = 22 frps.toml---- bindAddr = "0.0.0.0" bindPort = 7000 tcpmuxHTTPConnectPort = 7900 ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:25:56 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:25:59 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (May 27, 2025):

The error 'tcpmux with multiplexer httpconnect not supported because this feature is not enabled in server' occurs when the frps server hasn't enabled the tcpmuxHTTPConnectPort. Your frps.toml correctly specifies tcpmuxHTTPConnectPort = 7900, and your frpc.toml is also set up correctly for this.

The most likely reason for the error is that your frps instance is not actually loading this specific configuration file, or it wasn't restarted after the change was made.

Here’s what you can do to fix this:

Verify frps Startup Command: Make sure you are starting frps with the -c flag pointing to your frps.toml file. For example: ./frps -c /path/to/your/frps.toml
Check frps Logs: When frps starts, it should log which configuration file it's using and on which ports it's listening. Look for messages confirming it's using your intended frps.toml and listening on port 7000 (for bindPort) and 7900 (for tcpmuxHTTPConnectPort).

@fatedier commented on GitHub (May 27, 2025): The error 'tcpmux with multiplexer httpconnect not supported because this feature is not enabled in server' occurs when the frps server hasn't enabled the tcpmuxHTTPConnectPort. Your frps.toml correctly specifies tcpmuxHTTPConnectPort = 7900, and your frpc.toml is also set up correctly for this. The most likely reason for the error is that your frps instance is not actually loading this specific configuration file, or it wasn't restarted after the change was made. Here’s what you can do to fix this: * Verify frps Startup Command: Make sure you are starting frps with the -c flag pointing to your frps.toml file. For example: ./frps -c /path/to/your/frps.toml * Check frps Logs: When frps starts, it should log which configuration file it's using and on which ports it's listening. Look for messages confirming it's using your intended frps.toml and listening on port 7000 (for bindPort) and 7900 (for tcpmuxHTTPConnectPort).

gitea-mirror commented

2026-05-05 14:26:00 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jun 11, 2025):

Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Jun 11, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

No Branch/Tag specified