[GH-ISSUE #1114] FRP not connecting to upstream server #873

New issue

Closed

opened 2026-05-05 12:33:13 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 12:33:13 -06:00

Owner

Originally created by @jobs-git on GitHub (Mar 7, 2019).
Original GitHub issue: https://github.com/fatedier/frp/issues/1114

I used the default configuration frps_full for frps then used frpc_full for frpc. I modified it a bit to help me expose my upstream server:

[web]
type = http
local_ip = 127.0.0.2
local_port = 4567

use_encryption = false
use_compression = false
#subdomain = web01
custom_domains = testing.com

However, I dont seem to connect to my upstream. What is the proper way of configuring w/ upstream server?

Originally created by @jobs-git on GitHub (Mar 7, 2019). Original GitHub issue: https://github.com/fatedier/frp/issues/1114 I used the default configuration frps_full for frps then used frpc_full for frpc. I modified it a bit to help me expose my upstream server: ```bash [web] type = http local_ip = 127.0.0.2 local_port = 4567 use_encryption = false use_compression = false #subdomain = web01 custom_domains = testing.com ``` However, I dont seem to connect to my upstream. What is the proper way of configuring w/ upstream server?

gitea-mirror closed this issue

2026-05-05 12:33:14 -06:00

gitea-mirror commented

2026-05-05 12:33:16 -06:00

Author

Owner

@fatedier commented on GitHub (Mar 8, 2019):

Do not use frps_full.ini and frpc_full.ini. They are only example files to show supported params.

Read document first https://github.com/fatedier/frp#visit-your-web-service-in-lan-by-custom-domains .

@fatedier commented on GitHub (Mar 8, 2019): Do not use frps_full.ini and frpc_full.ini. They are only example files to show supported params. Read document first https://github.com/fatedier/frp#visit-your-web-service-in-lan-by-custom-domains .

gitea-mirror commented

2026-05-05 12:33:16 -06:00

Author

Owner

@jobs-git commented on GitHub (Mar 8, 2019):

You were right! Thank man!

@jobs-git commented on GitHub (Mar 8, 2019): You were right! Thank man!

gitea-mirror referenced this issue

2026-05-05 14:38:47 -06:00

[PR #873] [CLOSED] websocket protocol #4266