[GH-ISSUE #3502] everything seems ok,but don't work

gitea-mirror commented

2026-05-05 13:48:32 -06:00

Owner

Copy link

Originally created by @milkpeanut on GitHub (Jun 27, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3502

Bug Description

I build fprs in my router (Asus RT-AC86U)
build frpc in windows docker(WSL2) images : snowdreamtech/frps

The frpc logs show success.
And I can see the https proxy is on line in server dashboard.
But I cann't visit the web https://[asusddns domain]:9996
even I cann't visit the frpc local web. 127.0.0.1:39999

frpc Version

0.49

frps Version

0.49

System Architecture

windows/amd64,linux/amd64

Configurations

frps.ini
[common]
bind_port = 9998
vhost_http_port = 9997
vhost_https_port = 9996
token = xxx
dashboard_port = 9999
dashboard_user = admin
dashboard_pwd = xxxx

frpc.ini
[common]
server_addr = [asusddns domain]
server_port = 9998
token = xxx
admin_addr = 127.0.0.1
admin_port = 39999
admin_user = admin
admin_pwd = xxxx

[vaultwarden]
type = https
local_port = 8889
custom_domains = [asusddns domain]

Logs

frpc logs:
[service.go:295] [bf69acdca81370c0] login to server success, get run id [bf69acdca81370c0]
[proxy_manager.go:152] [bf69acdca81370c0] proxy added: [vaultwarden]
[service.go:161] admin server listen on 127.0.0.1:39999
[control.go:172] [bf69acdca81370c0] [vaultwarden] start proxy success

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 @milkpeanut on GitHub (Jun 27, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3502 ### Bug Description I build fprs in my router (Asus RT-AC86U) build frpc in windows docker(WSL2) images : snowdreamtech/frps The frpc logs show success. And I can see the https proxy is on line in server dashboard. But I cann't visit the web https://[asusddns domain]:9996 even I cann't visit the frpc local web. 127.0.0.1:39999 ### frpc Version 0.49 ### frps Version 0.49 ### System Architecture windows/amd64,linux/amd64 ### Configurations frps.ini [common] bind_port = 9998 vhost_http_port = 9997 vhost_https_port = 9996 token = xxx dashboard_port = 9999 dashboard_user = admin dashboard_pwd = xxxx frpc.ini [common] server_addr = [asusddns domain] server_port = 9998 token = xxx admin_addr = 127.0.0.1 admin_port = 39999 admin_user = admin admin_pwd = xxxx [vaultwarden] type = https local_port = 8889 custom_domains = [asusddns domain] ### Logs frpc logs: [service.go:295] [bf69acdca81370c0] login to server success, get run id [bf69acdca81370c0] [proxy_manager.go:152] [bf69acdca81370c0] proxy added: [vaultwarden] [service.go:161] admin server listen on 127.0.0.1:39999 [control.go:172] [bf69acdca81370c0] [vaultwarden] start proxy success ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:48:32 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:48:35 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jul 28, 2023):

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

@github-actions[bot] commented on GitHub (Jul 28, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified