[GH-ISSUE #3726] frpc.exe -c frpc.toml Not using native proxy #2965

Closed
opened 2026-05-05 13:54:57 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @lijingpan on GitHub (Oct 27, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3726

Bug Description

login to server failed: parse "127.0.0.1:10809": first path segment in URL cannot contain colon

Turn off the agent and prompt an error

How do I need to set up the local proxy?

frpc Version

0.52.1

frps Version

0.52.1

System Architecture

windows/amd64

Configurations

serverAddr = "x.x.x.x"
serverPort = 7001
auth.token = xxxxxx

proxies
name = "ssh"
type = "tcp"
localIP = "192.168.1.99"
localPort = 3389
remotePort = 4001

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 @lijingpan on GitHub (Oct 27, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3726 ### Bug Description login to server failed: parse "127.0.0.1:10809": first path segment in URL cannot contain colon Turn off the agent and prompt an error How do I need to set up the local proxy? ### frpc Version 0.52.1 ### frps Version 0.52.1 ### System Architecture windows/amd64 ### Configurations serverAddr = "x.x.x.x" serverPort = 7001 auth.token = xxxxxx [[proxies]] name = "ssh" type = "tcp" localIP = "192.168.1.99" localPort = 3389 remotePort = 4001 ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [X] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 13:54:57 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Nov 27, 2023):

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

<!-- gh-comment-id:1826962605 --> @github-actions[bot] commented on GitHub (Nov 27, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#2965
No description provided.