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
  • frpc.exe detected as virus

    frpc.exe detected as virus

    I am using frpc as a proxy for RDP (port 3389/TCP) on windows, using stcp. Works beautifully, but Windows Defender, the default anti-virus, wrongly reports the executable frpc.exe as a virus and blocks/removes the file immediately. Kaspersky anti-virus does it too. This is totally annoying and makes the use of the program a pain, if not impossible, in my corporate environment that has to have anti-virus software installed by (terrible and dumb) laws and regulations: in some machines the anti-virus program can't be disabled at all. Is there a way to circumvent this issue ?

    question 
    opened by Wyk72 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
  • Something wrong with frpc . when i type

    Something wrong with frpc . when i type "./frpc -c ./frpc.ini " , log shows that "2021/11/28 04:00:04 [W] [service.go:104] login to server failed: session shutdown"

    Bug Description

    frpc Version

    0.38.0

    frps Version

    0.38.0

    System Architecture

    linux/amd64

    Configurations

    [common] server_addr = xxx.xxx.xxx.xxx server_port = 7000 tls_enable = true [ssh] type = tcp local_ip = 127.0.0.1 local_port = 22 remote_port = 6000 ~

    Logs

    2021/11/28 04:00:04 [W] [service.go:104] login to server failed: session shutdown

    Steps to reproduce

    1. open frps
    2. open frpc
    3. log shows ...

    Affected area

    • [ ] Docs
    • [ ] Installation
    • [ ] Performance and Scalability
    • [ ] Security
    • [ ] User Experience
    • [ ] Test and Release
    • [ ] Developer Infrastructure
    • [X] Client Plugin
    • [X] Server Plugin
    • [ ] Extensions
    • [ ] Others
    opened by sesameman 1
  • [Question] How to use UDP on port 25565(Minecraft server)

    [Question] How to use UDP on port 25565(Minecraft server)

    Describe the feature request

    Uh.. Ahm....

    Describe alternatives you've considered

    No response

    Affected area

    • [ ] Docs
    • [ ] Installation
    • [ ] Performance and Scalability
    • [ ] Security
    • [ ] User Experience
    • [ ] Test and Release
    • [ ] Developer Infrastructure
    • [ ] Client Plugin
    • [ ] Server Plugin
    • [ ] Extensions
    • [X] Others
    opened by Timtaran 0
  • 容器中 bridge模式,UDP转发无效

    容器中 bridge模式,UDP转发无效

    Bug Description

    frps 部署在docker中时,网络使用host模式,udp转发才能生效,使用bridge模式,udp转发无效,TCP正常

    frpc Version

    0.38.1

    frps Version

    0.38.1

    System Architecture

    linux docker

    Configurations

    Logs

    No response

    Steps to reproduce

    ...

    Affected area

    • [ ] Docs
    • [ ] Installation
    • [X] Performance and Scalability
    • [ ] Security
    • [ ] User Experience
    • [ ] Test and Release
    • [ ] Developer Infrastructure
    • [ ] Client Plugin
    • [ ] Server Plugin
    • [ ] Extensions
    • [ ] Others
    opened by lynzhai 0
  • fix/spelling

    fix/spelling

    error spelling should not be capitalized(go statistic)

    opened by ChristLZS 0
  • do http proxy request error: no such domain: 8.xxx.xxx.105

    do http proxy request error: no such domain: 8.xxx.xxx.105

    Bug Description

    出现这个问题:do http proxy request error: no such domain: 8.xxx.xxx.105 /

    防火墙也放行了那些端口。

    如果 domain 必须要是域名的话,还得域名备案完后才行,不能直接用 ip 吗? 还是其他地方配置有问题,找了好久没找到。

    frpc Version

    frp_0.38.0_windows_amd64

    frps Version

    frp_0.38.0_linux_amd64

    System Architecture

    linux/amd64, windows/x64

    Configurations

    客户端配置:

    [common]
    server_addr = 8.xxx.xxx.105
    server_port = 7000
    
    [test_https2http]
    type = https
    custom_domains = 8.xxx.xxx.105:8888
    plugin = https2http
    plugin_local_addr = 127.0.0.1:9999
    plugin_crt_path = my_crt.crt
    plugin_key_path =my_key.key
    plugin_host_header_rewrite = 127.0.0.1
    plugin_header_X-From-Where = frp
    

    阿里云服务器 tocmat 服务端配置:

    [common]
    bind_port = 7000
    vhost_http_port = 7777
    vhost_https_port = 8888
    

    Logs

    阿里云服务器 tocmat 服务端异常输出:

    Nov 24 00:58:14 iZ7xv76g9qv6sxh6iptadrZ frps[2025]: 2021/11/24 00:58:14 [I] [https.go:51] [991f512dab2799a3] [test_https2http] https proxy listen for host [8.xxx.xxx.105:8888]
    Nov 24 00:58:14 iZ7xv76g9qv6sxh6iptadrZ frps[2025]: 2021/11/24 00:58:14 [I] [control.go:444] [991f512dab2799a3] new proxy [test_https2http] success
    Nov 24 00:58:15 iZ7xv76g9qv6sxh6iptadrZ frps[2025]: 2021/11/24 00:58:15 [W] [http.go:92] do http proxy request error: no such domain: 8.xxx.xxx.105 /
    Nov 24 01:07:12 iZ7xv76g9qv6sxh6iptadrZ frps[2025]: 2021/11/24 01:07:12 [W] [http.go:92] do http proxy request error: no such domain: 8.xxx.xxx.105 /favicon.ico
    

    Steps to reproduce

    1. 自己搭建本机后台服务器项目 127.0.0.1:9999
    2. 配置 frps
    3. 配置 frpc
    4. 阿里云服务器防火墙已放行端口
    5. 单独 http 请求内网穿透测试正常,而测试 https 请求出现上面问题。 ...

    Affected area

    • [ ] Docs
    • [ ] Installation
    • [ ] Performance and Scalability
    • [x] Security
    • [ ] User Experience
    • [x] Test and Release
    • [x] Developer Infrastructure
    • [X] Client Plugin
    • [X] Server Plugin
    • [ ] Extensions
    • [ ] Others
    opened by ddxl123 0
  • CentOS8 systemd start problem

    CentOS8 systemd start problem

    Bug Description

    fprc systemd start error with code=exited, status=203/EXEC

    frpc Version

    0.38.0

    frps Version

    0.38.0

    System Architecture

    linux/amd64

    Configurations

    frpc.ini [common] server_addr = xxxxxxxxx server_port = 7000 token =xxxxxx

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

    frpc.service #!/bin/bash [Unit] Description=Frp Client Service After=network.target

    [Service] Type=simple User=root Restart=on-failure RestartSec=5s ExecStart=/root/remote/fpc/frp_0.38.0_linux_amd64/frpc -c /root/remote/fpc/frp_0.38.0_linux_amd64/frpc.ini ExecReload=/root/remote/fpc/frp_0.38.0_linux_amd64/frpc reload -c /root/remote/fpc/frp_0.38.0_linux_amd64/frpc.ini LimitNOFILE=1048576

    [Install] WantedBy=multi-user.target

    Logs

    [[email protected] system]# systemctl status frpc ● frpc.service - Frp Client Service Loaded: loaded (/usr/lib/systemd/system/frpc.service; enabled; vendor preset: disabled) Active: activating (auto-restart) (Result: exit-code) since Tue 2021-11-23 09:12:42 EST; 1s ago Process: 23125 ExecStart=/root/remote/fpc/frp_0.38.0_linux_amd64/frpc -c /root/remote/fpc/frp_0.38.0_linux_amd64/frpc.ini (code=exited, status=203/EXEC) Main PID: 23125 (code=exited, status=203/EXEC)

    Steps to reproduce

    1. add chmod 777 to 3 different files frpc frpc.ini frpc.service
    2. add #!/bin/bash for fprc.service
    3. works for frps but for frpc on CentoOS8, didn't work ...

    Affected area

    • [ ] Docs
    • [X] Installation
    • [ ] Performance and Scalability
    • [ ] Security
    • [ ] User Experience
    • [ ] Test and Release
    • [ ] Developer Infrastructure
    • [ ] Client Plugin
    • [ ] Server Plugin
    • [ ] Extensions
    • [ ] Others
    opened by Handonghuang 0
  • 安卓手机用户

    安卓手机用户

    Describe the feature request

    有高手能开发frp安卓手机和苹果手机产品?

    Describe alternatives you've considered

    No response

    Affected area

    • [ ] Docs
    • [ ] Installation
    • [ ] Performance and Scalability
    • [ ] Security
    • [ ] User Experience
    • [ ] Test and Release
    • [ ] Developer Infrastructure
    • [ ] Client Plugin
    • [ ] Server Plugin
    • [ ] Extensions
    • [ ] Others
    opened by pc18189 6
  • [Feature Request]  Stop the client or server gracefully

    [Feature Request] Stop the client or server gracefully

    Describe the feature request

    Currently we don't have a command that can stop the frp client (or server) gracefully on a machine

    Describe alternatives you've considered

    we should have a command like frpc stop (or frps stop) to stop the active connections gracefully.

    Please let me know if this is something we would like to have as a feature, I can help to contribute as well.

    Thanks

    Affected area

    • [X] Docs
    • [x] Installation
    • [ ] Performance and Scalability
    • [ ] Security
    • [ ] User Experience
    • [X] Test and Release
    • [ ] Developer Infrastructure
    • [X] Client Plugin
    • [X] Server Plugin
    • [ ] Extensions
    • [ ] Others
    todo 
    opened by hinupurthakur 4
  • C端无法访问php文件,html正常访问,PHP提示404 not found

    C端无法访问php文件,html正常访问,PHP提示404 not found

    Bug Description

    C端无法访问php文件,html正常访问,PHP提示404 not found

    frpc Version

    0.38.0

    frps Version

    0.38.0

    System Architecture

    centos

    Configurations

    server{ listen 80; server_name *.test.xxx.com; location / { proxy_pass http://xx.xx.xx.xx:7001; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header REMOTE-HOST $remote_addr; } }

    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
    opened by okwindows 0
  • 编译时报错:mv: cannot stat ‘./release/frpc_windows_386’: No such file or directory make: *** [app] Error 1

    编译时报错:mv: cannot stat ‘./release/frpc_windows_386’: No such file or directory make: *** [app] Error 1

    Describe the feature request

    编译时候报错 mv: cannot stat ‘./release/frpc_windows_386’: No such file or directory make: *** [app] Error 1

    Describe alternatives you've considered

    No response

    Affected area

    • [ ] Docs
    • [ ] Installation
    • [ ] Performance and Scalability
    • [ ] Security
    • [ ] User Experience
    • [ ] Test and Release
    • [ ] Developer Infrastructure
    • [ ] Client Plugin
    • [ ] Server Plugin
    • [ ] Extensions
    • [ ] Others
    opened by uuuuuuzeus 0
Releases(v0.38.0)
Owner
To be yourself.
null
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 162 Dec 4, 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 17 Oct 26, 2021
Create a dynamic fou tunnels works behind NAT

Dynamic Linux Tunneling This software creates Gretap Tunnels over FOU for Dynamic client endpoints. It also works behind NAT444 (CGN-LSN). You can use

Ahmet ÖZER 2 Nov 4, 2021
Internet connectivity for your VPC-attached Lambda functions without a NAT Gateway

lambdaeip Internet connectivity for your VPC-attached Lambda functions without a NAT Gateway Background I occasionally have serverless applications th

Glass Echidna 19 Nov 14, 2021
A TCP proxy used to expose services onto a tailscale network without root. Ideal for container environments.

tailscale-sidecar This is barely tested software, I don't guarantee it works but please make an issue if you use it and find a bug. Pull requests are

Mark Pashmfouroush 60 Nov 26, 2021
mt-multiserver-proxy is a reverse proxy designed for linking multiple Minetest servers together

mt-multiserver-proxy mt-multiserver-proxy is a reverse proxy designed for linking multiple Minetest servers together. It is the successor to multiserv

null 7 Nov 27, 2021
TProx is a fast reverse proxy path traversal detector and directory bruteforcer.

TProx is a fast reverse proxy path traversal detector and directory bruteforcer Install • Usage • Examples • Join Discord Install Options From Source

Krypt0mux 26 Nov 27, 2021
Simple edge server / reverse proxy

reproxy Reproxy is simple edge HTTP(s) sever / reverse proxy supporting various providers (docker, static, file). One or more providers supply informa

Umputun 900 Nov 26, 2021
Reverse proxy server to filter traffic based on JA3 fingerprint/hash

JA3RP (JA3 Reverse Proxy) Ja3RP is a basic reverse proxy server that filters traffic based on JA3 fingerprints. It can also operate as a regular HTTP

Sleeyax 4 Nov 28, 2021
A standalone Web Server developed with the standard http library, suport reverse proxy & flexible configuration

paddy 简介 paddy是一款单进程的独立运行的web server,基于golang的标准库net/http实现。 paddy提供以下功能: 直接配置http响应 目录文件服务器 proxy_pass代理 http反向代理 支持请求和响应插件 部署 编译 $ go build ./main/p

fangyousong 2 Dec 2, 2021
gRelay is an open source project written in Go that provides the circuit break pattern with a relay idea behind.

gRELAY gRelay is an open source project written in Go that provides: Circuit Break ✔️ Circuit Break + Relay ✔️ Concurrecny Safe ✔️ Getting start Insta

null 26 Nov 7, 2021
It is a proxy to improve article readability, a directory for your favorite articles, and a way to make the internet lighter and more accessible.

timoneiro It is a work in progress. Some features are unimplemented yet. The helmsman's goal is to be a way to browse articles without all the distrac

Cesar Gimenes 7 Jul 11, 2021
A pair of local reverse proxies (one in Windows, one in Linux) for Tailscale on WSL2

tailscale-wsl2 TL;DR Running two reverse proxies (one in Windows, one in the WSL2 Linux VM), the Windows Tailscale daemon can be accessed via WSL2: $

Danny Hermes 0 Dec 6, 2021
This plugin allows you to start a local server with hot reloading with Esbuild

esbuild-dev-server This plugin allows you to start a local server with hot reloading with Esbuild Installation npm npm i esbuild-dev-server -D yarn y

Vladislav Fedotov 10 Nov 22, 2021
Reverse cwmp proxy

cwmp-proxy Integration of the proxy will provide you the ability to place CPEs and ACS servers in different networks. What about if the devices are pl

Ivan Stefanov 14 Feb 21, 2020
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.6k Dec 1, 2021
An Advanced HTTP Reverse Proxy with Dynamic Sharding Strategies

Weaver - A modern HTTP Proxy with Advanced features Description Features Installation Architecture Configuration Contributing License Description Weav

Gojek 540 Nov 20, 2021
Dead simple reverse proxy for all your containerized needss

Whats this ? Pawxi is yet another reverse proxy designed with simplicity in mind. Born out of a certain users frustration at the complexity of setting

null 12 Jun 22, 2021