A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.

Overview

frp

Build Status GitHub release

README | 中文文档

What is frp?

frp is a fast reverse proxy to help you expose a local server behind a NAT or firewall to the Internet. As of now, it supports TCP and UDP, as well as HTTP and HTTPS protocols, where requests can be forwarded to internal services by domain name.

frp also has a P2P connect mode.

Table of Contents

Development Status

frp is under development. Try the latest release version in the master branch, or use the dev branch for the version in development.

The protocol might change at a release and we don't promise backwards compatibility. Please check the release log when upgrading the client and the server.

Architecture

architecture

Example Usage

Firstly, download the latest programs from Release page according to your operating system and architecture.

Put frps and frps.ini onto your server A with public IP.

Put frpc and frpc.ini onto your server B in LAN (that can't be connected from public Internet).

Access your computer in LAN by SSH

  1. Modify frps.ini on server A and set the bind_port to be connected to frp clients:
# frps.ini
[common]
bind_port = 7000
  1. Start frps on server A:

./frps -c ./frps.ini

  1. On server B, modify frpc.ini to put in your frps server public IP as server_addr field:
# frpc.ini
[common]
server_addr = x.x.x.x
server_port = 7000

[ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 22
remote_port = 6000

Note that local_port (listened on client) and remote_port (exposed on server) are for traffic goes in/out the frp system, whereas server_port is used between frps.

  1. Start frpc on server B:

./frpc -c ./frpc.ini

  1. From another machine, SSH to server B like this (assuming that username is test):

ssh -oPort=6000 [email protected]

Visit your web service in LAN by custom domains

Sometimes we want to expose a local web service behind a NAT network to others for testing with your own domain name and unfortunately we can't resolve a domain name to a local IP.

However, we can expose an HTTP(S) service using frp.

  1. Modify frps.ini, set the vhost HTTP port to 8080:
# frps.ini
[common]
bind_port = 7000
vhost_http_port = 8080
  1. Start frps:

./frps -c ./frps.ini

  1. Modify frpc.ini and set server_addr to the IP address of the remote frps server. The local_port is the port of your web service:
# frpc.ini
[common]
server_addr = x.x.x.x
server_port = 7000

[web]
type = http
local_port = 80
custom_domains = www.example.com
  1. Start frpc:

./frpc -c ./frpc.ini

  1. Resolve A record of www.example.com to the public IP of the remote frps server or CNAME record to your origin domain.

  2. Now visit your local web service using url http://www.example.com:8080.

Forward DNS query request

  1. Modify frps.ini:
# frps.ini
[common]
bind_port = 7000
  1. Start frps:

./frps -c ./frps.ini

  1. Modify frpc.ini and set server_addr to the IP address of the remote frps server, forward DNS query request to Google Public DNS server 8.8.8.8:53:
# frpc.ini
[common]
server_addr = x.x.x.x
server_port = 7000

[dns]
type = udp
local_ip = 8.8.8.8
local_port = 53
remote_port = 6000
  1. Start frpc:

./frpc -c ./frpc.ini

  1. Test DNS resolution using dig command:

dig @x.x.x.x -p 6000 www.google.com

Forward Unix domain socket

Expose a Unix domain socket (e.g. the Docker daemon socket) as TCP.

Configure frps same as above.

  1. Start frpc with configuration:
# frpc.ini
[common]
server_addr = x.x.x.x
server_port = 7000

[unix_domain_socket]
type = tcp
remote_port = 6000
plugin = unix_domain_socket
plugin_unix_path = /var/run/docker.sock
  1. Test: Get Docker version using curl:

curl http://x.x.x.x:6000/version

Expose a simple HTTP file server

Browser your files stored in the LAN, from public Internet.

Configure frps same as above.

  1. Start frpc with configuration:
# frpc.ini
[common]
server_addr = x.x.x.x
server_port = 7000

[test_static_file]
type = tcp
remote_port = 6000
plugin = static_file
plugin_local_path = /tmp/files
plugin_strip_prefix = static
plugin_http_user = abc
plugin_http_passwd = abc
  1. Visit http://x.x.x.x:6000/static/ from your browser and specify correct user and password to view files in /tmp/files on the frpc machine.

Enable HTTPS for local HTTP(S) service

You may substitute https2https for the plugin, and point the plugin_local_addr to a HTTPS endpoint.

  1. Start frpc with configuration:
# frpc.ini
[common]
server_addr = x.x.x.x
server_port = 7000

[test_https2http]
type = https
custom_domains = test.example.com

plugin = https2http
plugin_local_addr = 127.0.0.1:80
plugin_crt_path = ./server.crt
plugin_key_path = ./server.key
plugin_host_header_rewrite = 127.0.0.1
plugin_header_X-From-Where = frp
  1. Visit https://test.example.com.

Expose your service privately

Some services will be at risk if exposed directly to the public network. With STCP (secret TCP) mode, a preshared key is needed to access the service from another client.

Configure frps same as above.

  1. Start frpc on machine B with the following config. This example is for exposing the SSH service (port 22), and note the sk field for the preshared key, and that the remote_port field is removed here:
# frpc.ini
[common]
server_addr = x.x.x.x
server_port = 7000

[secret_ssh]
type = stcp
sk = abcdefg
local_ip = 127.0.0.1
local_port = 22
  1. Start another frpc (typically on another machine C) with the following config to access the SSH service with a security key (sk field):
# frpc.ini
[common]
server_addr = x.x.x.x
server_port = 7000

[secret_ssh_visitor]
type = stcp
role = visitor
server_name = secret_ssh
sk = abcdefg
bind_addr = 127.0.0.1
bind_port = 6000
  1. On machine C, connect to SSH on machine B, using this command:

ssh -oPort=6000 127.0.0.1

P2P Mode

xtcp is designed for transmitting large amounts of data directly between clients. A frps server is still needed, as P2P here only refers the actual data transmission.

Note it can't penetrate all types of NAT devices. You might want to fallback to stcp if xtcp doesn't work.

  1. In frps.ini configure a UDP port for xtcp:
# frps.ini
bind_udp_port = 7001
  1. Start frpc on machine B, expose the SSH port. Note that remote_port field is removed:
# frpc.ini
[common]
server_addr = x.x.x.x
server_port = 7000

[p2p_ssh]
type = xtcp
sk = abcdefg
local_ip = 127.0.0.1
local_port = 22
  1. Start another frpc (typically on another machine C) with the config to connect to SSH using P2P mode:
# frpc.ini
[common]
server_addr = x.x.x.x
server_port = 7000

[p2p_ssh_visitor]
type = xtcp
role = visitor
server_name = p2p_ssh
sk = abcdefg
bind_addr = 127.0.0.1
bind_port = 6000
  1. On machine C, connect to SSH on machine B, using this command:

ssh -oPort=6000 127.0.0.1

Features

Configuration Files

Read the full example configuration files to find out even more features not described here.

Full configuration file for frps (Server)

Full configuration file for frpc (Client)

Using Environment Variables

Environment variables can be referenced in the configuration file, using Go's standard format:

# frpc.ini
[common]
server_addr = {{ .Envs.FRP_SERVER_ADDR }}
server_port = 7000

[ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 22
remote_port = {{ .Envs.FRP_SSH_REMOTE_PORT }}

With the config above, variables can be passed into frpc program like this:

export FRP_SERVER_ADDR="x.x.x.x"
export FRP_SSH_REMOTE_PORT="6000"
./frpc -c ./frpc.ini

frpc will render configuration file template using OS environment variables. Remember to prefix your reference with .Envs.

Dashboard

Check frp's status and proxies' statistics information by Dashboard.

Configure a port for dashboard to enable this feature:

[common]
dashboard_port = 7500
# dashboard's username and password are both optional,if not set, default is admin.
dashboard_user = admin
dashboard_pwd = admin

Then visit http://[server_addr]:7500 to see the dashboard, with username and password both being admin by default.

dashboard

Admin UI

The Admin UI helps you check and manage frpc's configuration.

Configure an address for admin UI to enable this feature:

[common]
admin_addr = 127.0.0.1
admin_port = 7400
admin_user = admin
admin_pwd = admin

Then visit http://127.0.0.1:7400 to see admin UI, with username and password both being admin by default.

Monitor

When dashboard is enabled, frps will save monitor data in cache. It will be cleared after process restart.

Prometheus is also supported.

Prometheus

Enable dashboard first, then configure enable_prometheus = true in frps.ini.

http://{dashboard_addr}/metrics will provide prometheus monitor data.

Authenticating the Client

There are 2 authentication methods to authenticate frpc with frps.

You can decide which one to use by configuring authentication_method under [common] in frpc.ini and frps.ini.

Configuring authenticate_heartbeats = true under [common] will use the configured authentication method to add and validate authentication on every heartbeat between frpc and frps.

Configuring authenticate_new_work_conns = true under [common] will do the same for every new work connection between frpc and frps.

Token Authentication

When specifying authentication_method = token under [common] in frpc.ini and frps.ini - token based authentication will be used.

Make sure to specify the same token in the [common] section in frps.ini and frpc.ini for frpc to pass frps validation

OIDC Authentication

When specifying authentication_method = oidc under [common] in frpc.ini and frps.ini - OIDC based authentication will be used.

OIDC stands for OpenID Connect, and the flow used is called Client Credentials Grant.

To use this authentication type - configure frpc.ini and frps.ini as follows:

# frps.ini
[common]
authentication_method = oidc
oidc_issuer = https://example-oidc-issuer.com/
oidc_audience = https://oidc-audience.com/.default
# frpc.ini
[common]
authentication_method = oidc
oidc_client_id = 98692467-37de-409a-9fac-bb2585826f18 # Replace with OIDC client ID
oidc_client_secret = oidc_secret
oidc_audience = https://oidc-audience.com/.default
oidc_token_endpoint_url = https://example-oidc-endpoint.com/oauth2/v2.0/token

Encryption and Compression

The features are off by default. You can turn on encryption and/or compression:

# frpc.ini
[ssh]
type = tcp
local_port = 22
remote_port = 6000
use_encryption = true
use_compression = true

TLS

frp supports the TLS protocol between frpc and frps since v0.25.0.

For port multiplexing, frp sends a first byte 0x17 to dial a TLS connection.

Configure tls_enable = true in the [common] section to frpc.ini to enable this feature.

To enforce frps to only accept TLS connections - configure tls_only = true in the [common] section in frps.ini. This is optional.

frpc TLS settings (under the [common] section):

tls_enable = true
tls_cert_file = certificate.crt
tls_key_file = certificate.key
tls_trusted_ca_file = ca.crt

frps TLS settings (under the [common] section):

tls_only = true
tls_enable = true
tls_cert_file = certificate.crt
tls_key_file = certificate.key
tls_trusted_ca_file = ca.crt

You will need a root CA cert and at least one SSL/TLS certificate. It can be self-signed or regular (such as Let's Encrypt or another SSL/TLS certificate provider).

If you using frp via IP address and not hostname, make sure to set the appropriate IP address in the Subject Alternative Name (SAN) area when generating SSL/TLS Certificates.

Given an example:

  • Prepare openssl config file. It exists at /etc/pki/tls/openssl.cnf in Linux System and /System/Library/OpenSSL/openssl.cnf in MacOS, and you can copy it to current path, like cp /etc/pki/tls/openssl.cnf ./my-openssl.cnf. If not, you can build it by yourself, like:
cat > my-openssl.cnf << EOF
[ ca ]
default_ca = CA_default
[ CA_default ]
x509_extensions = usr_cert
[ req ]
default_bits        = 2048
default_md          = sha256
default_keyfile     = privkey.pem
distinguished_name  = req_distinguished_name
attributes          = req_attributes
x509_extensions     = v3_ca
string_mask         = utf8only
[ req_distinguished_name ]
[ req_attributes ]
[ usr_cert ]
basicConstraints       = CA:FALSE
nsComment              = "OpenSSL Generated Certificate"
subjectKeyIdentifier   = hash
authorityKeyIdentifier = keyid,issuer
[ v3_ca ]
subjectKeyIdentifier   = hash
authorityKeyIdentifier = keyid:always,issuer
basicConstraints       = CA:true
EOF
  • build ca certificates:
openssl genrsa -out ca.key 2048
openssl req -x509 -new -nodes -key ca.key -subj "/CN=example.ca.com" -days 5000 -out ca.crt
  • build frps certificates:
openssl genrsa -out server.key 2048

openssl req -new -sha256 -key server.key \
    -subj "/C=XX/ST=DEFAULT/L=DEFAULT/O=DEFAULT/CN=server.com" \
    -reqexts SAN \
    -config <(cat my-openssl.cnf <(printf "\n[SAN]\nsubjectAltName=DNS:localhost,IP:127.0.0.1,DNS:example.server.com")) \
    -out server.csr

openssl x509 -req -days 365 \
	-in server.csr -CA ca.crt -CAkey ca.key -CAcreateserial \
	-extfile <(printf "subjectAltName=DNS:localhost,IP:127.0.0.1,DNS:example.server.com") \
	-out server.crt
  • build frpc certificates:
openssl genrsa -out client.key 2048
openssl req -new -sha256 -key client.key \
    -subj "/C=XX/ST=DEFAULT/L=DEFAULT/O=DEFAULT/CN=client.com" \
    -reqexts SAN \
    -config <(cat my-openssl.cnf <(printf "\n[SAN]\nsubjectAltName=DNS:client.com,DNS:example.client.com")) \
    -out client.csr

openssl x509 -req -days 365 \
    -in client.csr -CA ca.crt -CAkey ca.key -CAcreateserial \
	-extfile <(printf "subjectAltName=DNS:client.com,DNS:example.client.com") \
	-out client.crt

Hot-Reloading frpc configuration

The admin_addr and admin_port fields are required for enabling HTTP API:

# frpc.ini
[common]
admin_addr = 127.0.0.1
admin_port = 7400

Then run command frpc reload -c ./frpc.ini and wait for about 10 seconds to let frpc create or update or delete proxies.

Note that parameters in [common] section won't be modified except 'start'.

Get proxy status from client

Use frpc status -c ./frpc.ini to get status of all proxies. The admin_addr and admin_port fields are required for enabling HTTP API.

Only allowing certain ports on the server

allow_ports in frps.ini is used to avoid abuse of ports:

# frps.ini
[common]
allow_ports = 2000-3000,3001,3003,4000-50000

allow_ports consists of specific ports or port ranges (lowest port number, dash -, highest port number), separated by comma ,.

Port Reuse

vhost_http_port and vhost_https_port in frps can use same port with bind_port. frps will detect the connection's protocol and handle it correspondingly.

We would like to try to allow multiple proxies bind a same remote port with different protocols in the future.

Bandwidth Limit

For Each Proxy

# frpc.ini
[ssh]
type = tcp
local_port = 22
remote_port = 6000
bandwidth_limit = 1MB

Set bandwidth_limit in each proxy's configure to enable this feature. Supported units are MB and KB.

TCP Stream Multiplexing

frp supports tcp stream multiplexing since v0.10.0 like HTTP2 Multiplexing, in which case all logic connections to the same frpc are multiplexed into the same TCP connection.

You can disable this feature by modify frps.ini and frpc.ini:

# frps.ini and frpc.ini, must be same
[common]
tcp_mux = false

Support KCP Protocol

KCP is a fast and reliable protocol that can achieve the transmission effect of a reduction of the average latency by 30% to 40% and reduction of the maximum delay by a factor of three, at the cost of 10% to 20% more bandwidth wasted than TCP.

KCP mode uses UDP as the underlying transport. Using KCP in frp:

  1. Enable KCP in frps:
# frps.ini
[common]
bind_port = 7000
# Specify a UDP port for KCP.
kcp_bind_port = 7000

The kcp_bind_port number can be the same number as bind_port, since bind_port field specifies a TCP port.

  1. Configure frpc.ini to use KCP to connect to frps:
# frpc.ini
[common]
server_addr = x.x.x.x
# Same as the 'kcp_bind_port' in frps.ini
server_port = 7000
protocol = kcp

Connection Pooling

By default, frps creates a new frpc connection to the backend service upon a user request. With connection pooling, frps keeps a certain number of pre-established connections, reducing the time needed to establish a connection.

This feature is suitable for a large number of short connections.

  1. Configure the limit of pool count each proxy can use in frps.ini:
# frps.ini
[common]
max_pool_count = 5
  1. Enable and specify the number of connection pool:
# frpc.ini
[common]
pool_count = 1

Load balancing

Load balancing is supported by group.

This feature is only available for types tcp and http now.

# frpc.ini
[test1]
type = tcp
local_port = 8080
remote_port = 80
group = web
group_key = 123

[test2]
type = tcp
local_port = 8081
remote_port = 80
group = web
group_key = 123

group_key is used for authentication.

Connections to port 80 will be dispatched to proxies in the same group randomly.

For type tcp, remote_port in the same group should be the same.

For type http, custom_domains, subdomain, locations should be the same.

Service Health Check

Health check feature can help you achieve high availability with load balancing.

Add health_check_type = tcp or health_check_type = http to enable health check.

With health check type tcp, the service port will be pinged (TCPing):

# frpc.ini
[test1]
type = tcp
local_port = 22
remote_port = 6000
# Enable TCP health check
health_check_type = tcp
# TCPing timeout seconds
health_check_timeout_s = 3
# If health check failed 3 times in a row, the proxy will be removed from frps
health_check_max_failed = 3
# A health check every 10 seconds
health_check_interval_s = 10

With health check type http, an HTTP request will be sent to the service and an HTTP 2xx OK response is expected:

# frpc.ini
[web]
type = http
local_ip = 127.0.0.1
local_port = 80
custom_domains = test.example.com
# Enable HTTP health check
health_check_type = http
# frpc will send a GET request to '/status'
# and expect an HTTP 2xx OK response
health_check_url = /status
health_check_timeout_s = 3
health_check_max_failed = 3
health_check_interval_s = 10

Rewriting the HTTP Host Header

By default frp does not modify the tunneled HTTP requests at all as it's a byte-for-byte copy.

However, speaking of web servers and HTTP requests, your web server might rely on the Host HTTP header to determine the website to be accessed. frp can rewrite the Host header when forwarding the HTTP requests, with the host_header_rewrite field:

# frpc.ini
[web]
type = http
local_port = 80
custom_domains = test.example.com
host_header_rewrite = dev.example.com

The HTTP request will have the the Host header rewritten to Host: dev.example.com when it reaches the actual web server, although the request from the browser probably has Host: test.example.com.

Setting other HTTP Headers

Similar to Host, You can override other HTTP request headers with proxy type http.

# frpc.ini
[web]
type = http
local_port = 80
custom_domains = test.example.com
host_header_rewrite = dev.example.com
header_X-From-Where = frp

Note that parameter(s) prefixed with header_ will be added to HTTP request headers.

In this example, it will set header X-From-Where: frp in the HTTP request.

Get Real IP

HTTP X-Forwarded-For

This feature is for http proxy only.

You can get user's real IP from HTTP request headers X-Forwarded-For and X-Real-IP.

Proxy Protocol

frp supports Proxy Protocol to send user's real IP to local services. It support all types except UDP.

Here is an example for https service:

# frpc.ini
[web]
type = https
local_port = 443
custom_domains = test.example.com

# now v1 and v2 are supported
proxy_protocol_version = v2

You can enable Proxy Protocol support in nginx to expose user's real IP in HTTP header X-Real-IP, and then read X-Real-IP header in your web service for the real IP.

Require HTTP Basic Auth (Password) for Web Services

Anyone who can guess your tunnel URL can access your local web server unless you protect it with a password.

This enforces HTTP Basic Auth on all requests with the username and password specified in frpc's configure file.

It can only be enabled when proxy type is http.

# frpc.ini
[web]
type = http
local_port = 80
custom_domains = test.example.com
http_user = abc
http_pwd = abc

Visit http://test.example.com in the browser and now you are prompted to enter the username and password.

Custom Subdomain Names

It is convenient to use subdomain configure for http and https types when many people share one frps server.

# frps.ini
subdomain_host = frps.com

Resolve *.frps.com to the frps server's IP. This is usually called a Wildcard DNS record.

# frpc.ini
[web]
type = http
local_port = 80
subdomain = test

Now you can visit your web service on test.frps.com.

Note that if subdomain_host is not empty, custom_domains should not be the subdomain of subdomain_host.

URL Routing

frp supports forwarding HTTP requests to different backend web services by url routing.

locations specifies the prefix of URL used for routing. frps first searches for the most specific prefix location given by literal strings regardless of the listed order.

# frpc.ini
[web01]
type = http
local_port = 80
custom_domains = web.example.com
locations = /

[web02]
type = http
local_port = 81
custom_domains = web.example.com
locations = /news,/about

HTTP requests with URL prefix /news or /about will be forwarded to web02 and other requests to web01.

TCP Port Multiplexing

frp supports receiving TCP sockets directed to different proxies on a single port on frps, similar to vhost_http_port and vhost_https_port.

The only supported TCP port multiplexing method available at the moment is httpconnect - HTTP CONNECT tunnel.

When setting tcpmux_httpconnect_port to anything other than 0 in frps under [common], frps will listen on this port for HTTP CONNECT requests.

The host of the HTTP CONNECT request will be used to match the proxy in frps. Proxy hosts can be configured in frpc by configuring custom_domain and / or subdomain under type = tcpmux proxies, when multiplexer = httpconnect.

For example:

# frps.ini
[common]
bind_port = 7000
tcpmux_httpconnect_port = 1337
# frpc.ini
[common]
server_addr = x.x.x.x
server_port = 7000

[proxy1]
type = tcpmux
multiplexer = httpconnect
custom_domains = test1

[proxy2]
type = tcpmux
multiplexer = httpconnect
custom_domains = test2

In the above configuration - frps can be contacted on port 1337 with a HTTP CONNECT header such as:

CONNECT test1 HTTP/1.1\r\n\r\n

and the connection will be routed to proxy1.

Connecting to frps via HTTP PROXY

frpc can connect to frps using HTTP proxy if you set OS environment variable HTTP_PROXY, or if http_proxy is set in frpc.ini file.

It only works when protocol is tcp.

# frpc.ini
[common]
server_addr = x.x.x.x
server_port = 7000
http_proxy = http://user:[email protected]:8080

Range ports mapping

Proxy with names that start with range: will support mapping range ports.

# frpc.ini
[range:test_tcp]
type = tcp
local_ip = 127.0.0.1
local_port = 6000-6006,6007
remote_port = 6000-6006,6007

frpc will generate 8 proxies like test_tcp_0, test_tcp_1, ..., test_tcp_7.

Client Plugins

frpc only forwards requests to local TCP or UDP ports by default.

Plugins are used for providing rich features. There are built-in plugins such as unix_domain_socket, http_proxy, socks5, static_file and you can see example usage.

Specify which plugin to use with the plugin parameter. Configuration parameters of plugin should be started with plugin_. local_ip and local_port are not used for plugin.

Using plugin http_proxy:

# frpc.ini
[http_proxy]
type = tcp
remote_port = 6000
plugin = http_proxy
plugin_http_user = abc
plugin_http_passwd = abc

plugin_http_user and plugin_http_passwd are configuration parameters used in http_proxy plugin.

Server Manage Plugins

Read the document.

Find more plugins in gofrp/plugin.

Development Plan

  • Log HTTP request information in frps.

Contributing

Interested in getting involved? We would like to help you!

  • Take a look at our issues list and consider sending a Pull Request to dev branch.
  • If you want to add a new feature, please create an issue first to describe the new feature, as well as the implementation approach. Once a proposal is accepted, create an implementation of the new features and submit it as a pull request.
  • Sorry for my poor English. Improvements for this document are welcome, even some typo fixes.
  • If you have great ideas, send an email to [email protected].

Note: We prefer you to give your advise in issues, so others with a same question can search it quickly and we don't need to answer them repeatedly.

Donation

If frp helps you a lot, you can support us by:

frp QQ group: 606194980

AliPay

donation-alipay

Wechat Pay

donation-wechatpay

PayPal

Donate money by PayPal to my account [email protected].

Issues
  • 无法开机启动

    无法开机启动

    添加到开机自启后 日志显示connection refused,但是直接执行却是正常的。

    question 
    opened by liwei19920307 29
  • Windows 20H2 report Atosev!ml & Presenoker

    Windows 20H2 report Atosev!ml & Presenoker

    [REQUIRED] hat version of frp are you using

    Version: 0.34 frpc

    [REQUIRED] What operating system and processor architecture are you using OS: Win CPU architecture: Intel X64

    [REQUIRED] description of errors Windows 20H2 report Atosev!ml & Presenoker

    confile

    NA log file

    NA

    Steps to reproduce the issue

    1. NA

    Supplementary information NA Can you guess what caused this issue NA

    Checklist:

    • [X] I included all information required in the sections above
    • [X] I made sure there are no duplicates of this report (Use Search)
    lifecycle/stale 
    opened by jonozw 26
  • 有一个双边加速软件,可参考提升frp的工作性能

    有一个双边加速软件,可参考提升frp的工作性能

    fatedier大哥,最近我发现了一个非常好的东西kcptun。 https://github.com/xtaci/kcptun 经过我简单测试之后,发现效果提升非常明显!不仅能降低延迟,而且传输速率等指标有显著地提升! 希望您能在以后的开发过程中融入此功能选择,集成在项目当中,最大优化本软件!

    proposal 
    opened by JimLee1996 24
  • 通过frp穿透内网web服务失败。frp服务端提示:http: proxy error: no such domain,

    通过frp穿透内网web服务失败。frp服务端提示:http: proxy error: no such domain,

    Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly. (为了节约时间,提高处理问题的效率,不按照格式填写的 issue 将会直接关闭。)

    Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST

    What version of frp are you using (./frpc -v or ./frps -v)? 0.19.0

    What operating system and processor architecture are you using (go env)? 服务端:centos 7 客户端: windows 10

    Configures you used:

    客户端

    [common] server_addr = 139.199.87.90 server_port = 7000 [web]type = http local_port = 8081 custom_domains = http://www.zhengcehuixiang.cn

    =================================================================

    服务端

    bind_port = 7000 vhost_http_port = 8181

    Steps to reproduce the issue: 1.在centos 7配置服务端文件frps.ini 2.在win10 配置了客户端的配置文件frpc.ini,开启本地web服务,端口为8081。该服务用Spring Boot开发。 3.frp的服务端和客户端显示连接成功,在本地可以访问web服务。

    Describe the results you received: 通过 http://www.zhengcehuixiang.cn:8181/user 访问报错,The page you visit not found. Sorry, the page you are looking for is currently unavailable. Please try again later.

    The server is powered by frp.

    Faithfully yours, frp.

    frp服务端提示: 2018/05/20 11:29:42 [W] [newhttp.go:190] http: proxy error: no such domain 2018/05/20 11:29:42 [W] [newhttp.go:190] http: proxy error: no such domain 2018/05/20 11:33:56 [W] [newhttp.go:190] http: proxy error: no such domain Describe the results you expected: 在web上显示字符串,hello,world。在本地通过localhost:8081/user是可以实现的。

    Additional information you deem important (e.g. issue happens only occasionally):

    Can you point out what caused this issue (optional) 我推测是配置文件没有填对,我是对着frp的官网文档,通过自定义域名访问部署于内网的 web 服务,填写的配置。请各位帮帮忙。衷心感谢。

    opened by AllstarVirgo 22
  • 服务端和客户端都正常连接,但穿透访问网站失败

    服务端和客户端都正常连接,但穿透访问网站失败

    Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly. (为了节约时间,提高处理问题的效率,不按照格式填写的 issue 将会直接关闭。)

    Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST

    What version of frp are you using (./frpc -v or ./frps -v)? Frps version 0.21.0 Frpc version 0.21.0

    What operating system and processor architecture are you using (go env)? CentOS Linux release 7.5.1804 (Core)

    Configures you used: frps.ini [common] bind_addr = 0.0.0.0 bind_port = 19000 kcp_bind_port = 19000 dashboard_port = 19001 dashboard_user = ****** dashboard_pwd = ****** vhost_http_port = 19080 vhost_https_port = 19443 log_file = ./frps.log log_level = info log_max_days = 3 #token = ****** max_pool_count = 50 tcp_mux = true subdomain_host = a***.ml

    frpc.ini [common] server_addr = a***.ml server_port = 19000 #token = ****** log_file = ./frpc.log log_level = info log_max_days = 3

    [http-test] type = http local_ip = 127.0.0.1 local_port = 80 #remote_port = 19080 subdomain = test

    Steps to reproduce the issue: 1.服务器日志和web控制面板(dashboard)可以看出已经连接上并建立透传规则; 2.附上服务端日志 frps.log 2018/11/14 00:06:53 [I] [service.go:130] frps tcp listen on 0.0.0.0:19000 2018/11/14 00:06:53 [I] [service.go:139] frps kcp listen on udp 0.0.0.0:19000 2018/11/14 00:06:53 [I] [service.go:172] http service listen on 0.0.0.0:19080 2018/11/14 00:06:53 [I] [service.go:193] https service listen on 0.0.0.0:19443 2018/11/14 00:06:53 [I] [service.go:216] Dashboard listen on 0.0.0.0:19001 2018/11/14 00:06:53 [I] [root.go:207] Start frps success 2018/11/14 00:29:18 [I] [service.go:319] client login info: ip [.236..*:26320] version [0.21.0] hostname [] os [linux] arch [amd64] 2018/11/14 00:29:18 [I] [proxy.go:291] [5e51079cf47442f5] [http-test] http proxy listen for host [test.a***.ml] location [] 2018/11/14 00:29:18 [I] [control.go:335] [5e51079cf47442f5] new proxy [http-test] success 2018/11/14 00:30:05 [I] [dashboard_api.go:67] Http request: [/api/serverinfo] 2018/11/14 00:30:05 [I] [dashboard_api.go:64] Http response [/api/serverinfo]: code [0] 2018/11/14 00:30:05 [I] [dashboard_api.go:178] Http request: [/api/proxy/http] 2018/11/14 00:30:05 [I] [dashboard_api.go:174] Http response [/api/proxy/http]: code [0] 2018/11/14 00:30:05 [I] [dashboard_api.go:175] /api/proxy/http 2018/11/14 00:30:05 [I] [dashboard_api.go:176] 2018/11/14 00:30:07 [I] [dashboard_api.go:309] Http request: [/api/traffic/http-test] 2018/11/14 00:30:07 [I] [dashboard_api.go:307] Http response [/api/traffic/http-test]: code [0] 3.附上客户端日志 2018/11/14 00:29:17 [I] [proxy_manager.go:300] proxy removed: [] 2018/11/14 00:29:17 [I] [proxy_manager.go:310] proxy added: [http-test] 2018/11/14 00:29:17 [I] [proxy_manager.go:333] visitor removed: [] 2018/11/14 00:29:17 [I] [proxy_manager.go:342] visitor added: [] 2018/11/14 00:29:18 [I] [control.go:246] [5e51079cf47442f5] login to server success, get run id [5e51079cf47442f5], server udp port [0] 2018/11/14 00:29:18 [I] [control.go:169] [5e51079cf47442f5] [http-test] start proxy success

    Describe the results you received: 用不同的浏览器打开http://test.a***.com报404错误,但直接用客户端的IP地址访问网站是正常的。

    Describe the results you expected: 用域名test.a***.com能直接访问客户端的网站

    Additional information you deem important (e.g. issue happens only occasionally):

    Can you point out what caused this issue (optional)

    opened by yflwz 22
  • Https 代理模式对证书的处理可能有问题

    Https 代理模式对证书的处理可能有问题

    Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly. (为了节约时间,提高处理问题的效率,不按照格式填写的 issue 将会直接关闭。)

    Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST

    What version of frp are you using (./frpc -v or ./frps -v)? 0.13.0

    What operating system and processor architecture are you using (go env)? CentOS 7 Server + Nginx 1.13.5 (built with OpenSSL 1.0.2l) / Debian 9 Client

    Configures you used:

    /frpc.ini

    [web01]
    type = tcp
    local_ip = 127.0.0.1
    local_port = 443
    use_encryption = false
    use_compression = false
    remote_port = 7443
    subdomain = web
    
    [web02]
    type = https
    local_ip = 127.0.0.1
    local_port = 443
    use_encryption = false
    use_compression = false 
    subdomain = web
    

    /frps.ini

    [common]
    bind_port = 7000
    kcp_bind_port = 7000
    
    vhost_http_port = 8080
    vhost_https_port = 8443
    
    privilege_token = xxxxx
    
    subdomain_host = xxx.com
    

    nginx vhost config

    server {
        listen       80;
        listen       443 ssl http2;
        server_name  web.xxx.com;
    
        ssl_certificate  /root/keys/xxx.crt;
        ssl_certificate_key  /root/keys/xxx.key;
    
        ssl_session_cache    shared:SSL:1m;
        ssl_session_timeout  5m;
        
        ssl_ciphers 'kEECDH+ECDSA+AES128 kEECDH+ECDSA+AES256 kEECDH+AES128 kEECDH+AES256 kEDH+AES128 kEDH+AES256 DES-CBC3-SHA +SHA !aNULL !eNULL !LOW !kECDH !DSS !MD5 !EXP !PSK !SRP !CAMELLIA !SEED';
        ssl_prefer_server_ciphers  on;
    
        if ( $ssl_protocol = "" ) {
            rewrite ^ https://$host$request_uri?;
        }
        location / {
            proxy_redirect off;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto  $scheme;
            proxy_pass https://127.0.0.1:8443;
        }
    }
    


    Steps to reproduce the issue:

    1. 使用以上配置 用 https://web.xxx.com 访问服务器端 Nginx会报 502 Bad Gateway
    2. 查阅 Nginx 的错误日志找到了以下内容: 2017/11/13 07:51:16 [error] 32703#32703: *6 peer closed connection in SSL handshake while SSL handshaking to upstream,
    3. 在服务器运行 openssl s_client -connect 127.0.0.1:8443 -tls1 的结果显示的证书信息是空的

    snipaste_2017-11-13-01

    PS: 浏览器直接访问 https://web.xxx.com:7443 和 https://web.xxx.com:8443 都是可以的 但是似乎使用https模式的 8443 端口 页面载入会稍慢一些

    Describe the results you received:proxy_pass 修改为 https://127.0.0.1:7443 就可以正常访问 https://web.xxx.com

    openssl s_client -connect 127.0.0.1:7443 -tls1 也可以返回正确信息 snipaste_2017-11-13_02 snipaste_2017-11-13_03

    Describe the results you expected: https 模式无法证书的话就只能使用 tcp 模式进行反代,这样的话 8443 端口无法复用,每次新增站点也要手动配置 nginx 很麻烦。

    Additional information you deem important (e.g. issue happens only occasionally):

    Can you point out what caused this issue (optional)

    opened by sxul 21
  • frp转发的内网wordpress博客, 一直正常使用,今天把frps做成了service, 注册开机自启, 然后博客页面无法访问

    frp转发的内网wordpress博客, 一直正常使用,今天把frps做成了service, 注册开机自启, 然后博客页面无法访问

    What version of frp are you using (./frpc -v or ./frps -v)? 0.29.1

    What operating system and processor architecture are you using (go env)? 服务端:搬瓦工VPS Debian9 amd64 客户端:树莓派 armv71

    Configures you used: 两端配置都是正常的, 之前一直在用,没有动过

    Steps to reproduce the issue: 今天因为VPS上装的V2ray从昨天开始突然连不上了,v2ray.service运行正常,就systemctl restart v2ray, 然后systemctl enable v2ray, 还是运行正常,但手机V2rayNG客户端就是连不上,显示contect exceeded sudo reboot重启VPS,V2ray自启成功,但是frps没有自启成功,之前用的nohup /frps -c /frps_full.ini后台启动的frps, 然后再次用这个命令启动frps, 然后启动成功。frps dashboard tcp 在线,http也在线,然后想看看这次重启frps会不会自启成功,又重启了VPS,v2ray自启成功,frps还是没自启,之前没出现过这个问题,就想着像frpc一样,把frps也做成service, 然后enable开机自启。移动frps和配置文件:cp /frps /usr/local/bin/frps,cp /frps_full.ini /etc/frps/frps_full.ini,然后创建frps.service文件:nano /usr/lib/systemd/system/frps.service 填入以下信息: 【Unit】 Description:frps Wants=network-online.target After=network-online.target network.target Requires=network-online.target

    【Service】 ExecStart=/usr/local/bin/frps -c /etc/frps/frps_full.ini ExecStop=/bin/kill $MAINPID Restart=always RestartSec=5 StartLimitInterval=0

    【Install】 WantedBy=multi-user.target

    然后保存,systemctl start frps, systemctl enable frps, 然后重启VPS,frps果然自启成功 然后frps dashboard tcp和http的线路都是通的在线状态

    然后我登陆frp转发的wordpress博客www.brucelog.club,页面不显示,仪表盘也登不上,重启树莓派线路是通的也没用。之前博客一直是正常显示,正常登陆的,因为之前已经把博客的站点URL改成了域名地址,所以输入本地IP也没用,试了VPS IP+/wordpress/wp-admin也不显示。 到底是怎么回事, 按理说转发的http线路是通的就是正常的,用来做博客服务器的树莓派的wordpress文件夹根本没动过,apache2和mariadb也是正常运行,只是把VPS服务端frps改成了service, 并且成功启动了下,线路也是通的,但是博客就突然页面不显示了,后台也不显示,不知道是什么原因? 难道服务端frps只能普通启动/frps -c /frps_full.ini或者nohup /frps -c /frps_full.ini不能做成service?

    哪位大神帮帮我?谢谢!本人不是程序员,只是看教程略懂些linux命令。

    WaitingForInfo 
    opened by bruceluo111 20
  • 希望能加入ChaCha20加密方式

    希望能加入ChaCha20加密方式

    我现在是用 openwrt 路由器跑 frp,功能都正常,但是现在加密方式对于路由器来说太重了, 希望

    1. 加入 ChaCha20 这样比较轻量的加密方式,对于低端设备会更好

    2. 希望发布 release 的时候增加 softfloat 版本 (go编译的时候可以选择),很多低端设备都不具备FPU,加密运算需要浮点计算,编译使用 softfloat 版本对低端设备效率更高 (尤其是 mips , mipsel 这种)

    enhancement 
    opened by qiang-yu 20
  • Configurable websocket PATH

    Configurable websocket PATH

    Create a new config record for websocket PATH when working in WS mode.

    New config record for server (frps), websocket_path = /myfrp ( require begin with "/" and no whitespace )

    New config record for client (frpc), when protocol = websocket websocket_path = /myfrp ( require begin with "/" and no whitespace )

    If this empty or not config, then use default path "/~!frp".

    opened by osnosn 0
  • no log file created

    no log file created

    [REQUIRED] hat version of frp are you using

    Version:0.36.1

    [REQUIRED] What operating system and processor architecture are you using OS:CentOS 7 CPU architecture:

    [REQUIRED] description of errors

    confile

    log file

    log_file = ./frps.log log_level = info log_max_days = 7 Steps to reproduce the issue

    1. frps start, no frps.log file created
    2. ./frps -c frps.ini , shows log in console, but not frps.log file created

    Supplementary information

    Can you guess what caused this issue

    Checklist:

    • [] I included all information required in the sections above
    • [] I made sure there are no duplicates of this report (Use Search)
    opened by towerbit 0
  • 使用 frpc 映射 v2ray 的 socks 代理异常

    使用 frpc 映射 v2ray 的 socks 代理异常

    [REQUIRED] hat version of frp are you using

    • Version: 0.37.0

    [REQUIRED] What operating system and processor architecture are you using

    • OS: window 7
    • CPU architecture: 64

    [REQUIRED] description of errors

    使用 frpc 映射 v2ray 的 socks 代理时,socks 服务报错:unknown Socks version: 67。

    confile

    frpc 配置:

    [xxx_v2ray]
    type = tcp
    local_ip = 10.1.x.x
    local_port = 1080
    remote_port = 1080
    

    v2ray 配置:

    {
          "inbounds": [
            {
                "port": 1080,
                "protocol": "socks",
                "settings":{
                    "auth": "noauth",
                    "userLevel":0
               }
            }
          ],
          "outbounds": [
            {
                "protocol": "freedom",
                "settings": {}
            }
          ]
    }
    

    log file

    frpc 日志:

    2021/07/21 21:57:17 [D] [proxy_wrapper.go:231] [f91111c97c2f4c0a] [xxx_v2ray] start a new work connection, localAddr: xxx:53699 remoteAddr: xx:xx
    2021/07/21 21:57:17 [T] [proxy.go:739] [f91111c97c2f4c0a] [xxx_v2ray] handle tcp work connection, use_encryption: false, use_compression: false
    2021/07/21 21:57:17 [D] [proxy.go:801] [f91111c97c2f4c0a] [xxx_v2ray] join connections, localConn(l[xxx:53702] r[xxx:1080]) workConn(l[xxx:53699] r[xxx:xxx])
    2021/07/21 21:57:17 [D] [proxy.go:809] [f91111c97c2f4c0a] [xxx_v2ray] join connections closed
    

    v2ray 日志:

    2021/07/21 21:54:10 tcp:xxx:53665 rejected  proxy/socks: unknown Socks version: 67
    2021/07/21 21:57:15 tcp:xxx:53702 rejected  proxy/socks: unknown Socks version: 67
    

    Supplementary information

    https://www.v2ray.com/chapter_00/faq.html#socks-unknown-socks-version-67

    Checklist:

    • [x] I included all information required in the sections above
    • [x] I made sure there are no duplicates of this report (Use Search)
    opened by liuweiGL 1
  • tls-only is always true if tls_trusted_ca_file is set

    tls-only is always true if tls_trusted_ca_file is set

    [REQUIRED] hat version of frp are you using

    Version: 0.37.0

    [REQUIRED] What operating system and processor architecture are you using OS: Windows, Linux CPU architecture: x86

    [REQUIRED] description of errors If tls_trusted_ca_file is set, server will reject non-TLS connections despite both tls_only and tls_enable are set to false.

    I want TLS to be optional. When setting tls_enable = true and tls_only = false on frps.ini, client should be able to connect with tls_enable is either true or false.

    confile

    server:

    [common]
    bind_addr = 0.0.0.0
    bind_port = 7000
    vhost_http_port = 8080
    log_level = trace
    
    tls_only = false
    
    tls_enable = false
    #tls_cert_file = certs-local/server.crt
    #tls_key_file = certs-local/server.key
    tls_trusted_ca_file = certs-local/ca.crt
    

    client:

    [common]
    server_addr = 127.0.0.1
    server_port = 7000
    log_level = debug
    protocol = tcp
    
    tls_enable = false
    
    [web]
    type = http
    local_ip = 127.0.0.1
    local_port = 80
    custom_domains = localhost
    

    log file

    server:

    D:\frp_0.37.0_windows_amd64>frps -c frps.ini
    2021/07/21 11:13:28 [I] [root.go:200] frps uses config file: frps.ini
    2021/07/21 11:13:28 [I] [service.go:192] frps tcp listen on 0.0.0.0:7000
    2021/07/21 11:13:28 [I] [service.go:235] http service listen on 0.0.0.0:8080
    2021/07/21 11:13:28 [I] [root.go:209] frps started successfully
    2021/07/21 11:13:32 [T] [service.go:396] start check TLS connection...
    2021/07/21 11:13:32 [W] [service.go:400] CheckAndEnableTLSServerConnWithTimeout error: non-TLS connection received on a TlsOnly server
    

    client:

    D:\frp_0.37.0_windows_amd64>frpc -c frpc.ini
    2021/07/21 11:17:58 [W] [service.go:104] login to server failed: EOF
    EOF
    

    Steps to reproduce the issue

    1. In frps.ini: set tls_trusted_ca_file value. Set tls_only and tls_enable to false.
    2. In frpc.ini set tls_enable: false.
    3. Start server and client. Server will reject non-tls connections.

    Supplementary information

    Can you guess what caused this issue

    Checklist:

    • [x] I included all information required in the sections above
    • [x] I made sure there are no duplicates of this report (Use Search)
    opened by trananhtuan 2
  • Support frps or frpc allow or black ip by some category

    Support frps or frpc allow or black ip by some category

    Hi,

    Maybe you can add a feature to allow some ip such as china ip or other countries to use or not frp service. It will improve the security of frp.

    opened by MikoyChinese 1
  • Exit if login fails while reconnecting

    Exit if login fails while reconnecting

    I would like an option to make frpc to exit when it fails to reconnect.

    • I thought that login_fail_exit would do this, but it does not.
    • I submitted a PR to make login_fail_exit do this, but what I want is not actually the intended behavior of login_fail_exit https://github.com/fatedier/frp/pull/2483

    I would add a new option (maybe reconnect_login_fail_exit?) that would make frpc exit when it fails to login while reconnecting.

    Application scenarios of this function

    We need to authenticate our frpc clients when they connect to frps. We cannot use a single shared token for this purpose, and we do not want to maintain the infrastructure needed to support OIDC authentication. Instead, we have implemented our own authentication system using a server plugin for Login.

    We have a script that generates a JWT and stores it in the environment, and then starts frpc. Our frpc.ini contains the following line:

    meta_jwt = {{ .Envs.JWT }}
    

    When the client tries to log in, the JWT is passed over to our server plugin, which validates it and allows the login to succeed.

    However, the JWT is only valid for a short time. When frpc attempts to reconnect, it uses the same JWT as when it was initially started. The JWT is now expired. Our server plugin rejects the login and our tunnel never comes back up, because frpc just keeps trying with the same expired token.

    Instead of retrying forever, we would like a way to make frpc exit when the login fails when reconnecting. Then our script can regenerate the JWT and restart frpc, and it will be able to connect again.

    proposal 
    opened by jordemort 6
  • frps是否支持proxy protocol

    frps是否支持proxy protocol

    为了做高可用的保障,现在的网络结构是某台公网服务器上装了haproxy和frps01,frps02。 客户端先连接到haproxy,然后再分通过本地(127.0.0.1)转frps01,frps02。在这种网络结构下,frps就无法感知客户端真实的ip。希望是haproxy可以启用proxy protocol,然后frps获取到客户端真实ip,是否可行?

    opened by luyaotang 5
  • Not starting TCP server for one tunel!

    Not starting TCP server for one tunel!

    Version:0.37.0

    [REQUIRED] What operating system and processor architecture are you using OS:Windows 8.1

    help to start a tkp server with a fixed port, kind people give detailed instructions, I can't figure it out myself! If possible, post instructions on YouTube and give a link. please respond! Screenshot_1

    opened by BBCLSD 0
  • is https://hub.docker.com/u/fatedier the official docker image publisher?

    is https://hub.docker.com/u/fatedier the official docker image publisher?

    The solution you want

    Alternatives considered

    How to implement this function

    Application scenarios of this function

    opened by bthulu 0
  • TCP端口映射无法正常访问到IIS的应用

    TCP端口映射无法正常访问到IIS的应用

    [REQUIRED] hat version of frp are you using

    Version: 0.37.0 [REQUIRED] What operating system and processor architecture are you using OS: Windows2012 CPU architecture: Xen Aliyun Ecs Server

    [REQUIRED] description of errors

    有一台服务器启动了IIS(监听20000端口),IIS 启动了多个网站,通过域名区分,所有网站都使用20000端口.

    FRPC映射本地20000端口到FRPS的20000端口. frpc.ini [webport] type = tcp local_ip = 127.0.0.1 local_port = 20000 remote_port = 20000

    frps 的ip为 1.1.1.1

    使用CDN,HTTPS 访问: https://www.abc.com( CDN) --- >http://1.1.1.1:20000
    问题: 网站400错误

    怀疑是使用了HTTPS访问再映射到http协议的时候出的问题. 以前一直这样用没有出问题,最近出问题的.好像是0.37.0开始有这个问题的.

    confile

    log file

    Steps to reproduce the issue 1. 2. 3.

    Supplementary information

    Can you guess what caused this issue

    Checklist:

    • [] I included all information required in the sections above
    • [] I made sure there are no duplicates of this report (Use Search)
    opened by zsinba 1
Releases(v0.37.0)
Owner
To be yourself.
null
A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.

frp README | 中文文档 What is frp? frp is a fast reverse proxy to help you expose a local server behind a NAT or firewall to the Internet. As of now, it s

null 47k Jul 22, 2021
An incredibly fast proxy checker & IP rotator with ease.

An incredibly fast proxy checker & IP rotator with ease.

Kitabisa 411 Jul 20, 2021
rconn is a multiplatform program for creating generic reverse connections. Lets you consume services that are behind firewall or NAT without opening ports or port-forwarding.

rconn (r[everse] conn[ection]) is a multiplatform program for creating reverse connections. It lets you consume services that are behind NAT and/or fi

Hikmat Jafarli 133 Jul 15, 2021
A fast port forwarding or reverse forwarding tool over HTTP1.0/HTTP1.1

gogw What's gogw ? gogw is a port forwarding/reverse forwarding tool over HTTP implements by golang. port forwarding/port reverse forwarding support T

xitongsys 39 Jul 4, 2021
Chisel is a fast TCP/UDP tunnel, transported over HTTP, secured via SSH.

Chisel is a fast TCP/UDP tunnel, transported over HTTP, secured via SSH. Single executable including both client and server. Written in Go (golang). Chisel is mainly useful for passing through firewalls, though it can also be used to provide a secure endpoint into your network.

Jaime Pillora 6.1k Jul 23, 2021
:alarm_clock: :fire: A TCP proxy to simulate network and system conditions for chaos and resiliency testing

Toxiproxy Toxiproxy is a framework for simulating network conditions. It's made specifically to work in testing, CI and development environments, supp

Shopify 5.6k Jul 20, 2021
netstat-nat - Display NAT entries on Linux systems

netstat-nat This is a reimplementation of the netstat-nat tool, written entirely in Go. It uses the same command line flags and almost the same output

Dominik Honnef 16 Apr 15, 2020
Modern network boot server.

bofied demo.mp4 Modern network boot server. Overview bofied is a network boot server. It provides everything you need to PXE boot a node, from a (prox

Felix Pojtinger 69 Jul 21, 2021
A CLI-based HTTP intercept and replay proxy

GLORP Glorp is an HTTP intercept proxy, allowing the inspection and replaying of HTTP requests. The layout and flow was designed to function similar t

DoI 196 Jul 15, 2021
Cloud Native Tunnel

inlets is a Cloud Native Tunnel written in Go Expose your local endpoints to the Internet or within a remote network, without touching firewalls. Foll

inlets 8.4k Jul 26, 2021
An experimental Tor-Proxy serivce written in Go using Go-proxy and Go-libtor.

tor-proxy An experimental standalone tor-proxy service built with Go, using go-proxy, go-libtor and bine. This is a simple replacement to Tor's origin

Narasimha Prasanna HN 28 Jul 21, 2021
Standalone client for proxies of Opera VPN

opera-proxy Standalone Opera VPN client. Younger brother of hola-proxy. Just run it and it'll start a plain HTTP proxy server forwarding traffic throu

null 199 Jul 18, 2021
Standalone client for proxies of Windscribe browser extension

windscribe-proxy Standalone Windscribe proxy client. Younger brother of opera-proxy. Just run it and it'll start a plain HTTP proxy server forwarding

null 12 Jul 17, 2021
Open Source HTTP Reverse Proxy Cache and Time Series Dashboard Accelerator

Trickster is an HTTP reverse proxy/cache for http applications and a dashboard query accelerator for time series databases. Learn more below, and chec

null 1.5k Jul 27, 2021