mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #3213] important bug #2580
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#2580
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @7054company on GitHub (Dec 15, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3213
Bug Description
In ssh random connecting
in which the frps assign frpc a random port
The client did't get info about random remort port assign in terminal
frpc Version
Lastest
frps Version
Lastest
System Architecture
linux
Configurations
Nothing
Logs
No
Steps to reproduce
...
Affected area
@7054company commented on GitHub (Dec 15, 2022):
FrpC logs
[root@15-206-145-28 f]# ./frpc -c ./c.ini
2022/12/15 06:10:19 [I] [service.go:357] [73ca9508a53185fa] login to
server success, get run id [73ca9508a53185fa], server udp port [7001]
2022/12/15 06:10:19 [I] [proxy_manager.go:142] [73ca9508a53185fa] pro
xy added: [ssh_random]
2022/12/15 06:10:19 [I] [service.go:162] admin server listen on 0.0.0
.0:7004
2022/12/15 06:10:19 [I] [control.go:177] [73ca9508a53185fa] [ssh_rand
om] start proxy success
In this i connect to frps server for ssh over random port but it connect but does not show info about the remote ssh port in logs
please help
@Becods commented on GitHub (Dec 20, 2022):
Check your configuration file.
@github-actions[bot] commented on GitHub (Jan 20, 2023):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
@7054company commented on GitHub (Jan 20, 2023):
Ya need enhancement in feature
On Fri, Jan 20, 2023, 06:04 github-actions[bot] @.***>
wrote:
@github-actions[bot] commented on GitHub (Feb 21, 2023):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.