You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, a frontend guy that not so skilled in network stack is here.
What I try to do
I try to make FRP server fully isolated so it should work inside caddy network through Caddy server. (Is that even possible?)
Problem
The problem: since frps on VPS machine is working through Caddy server, it is accessible only by HTTP(S). While I can open dashboard in browser, any of frpc could not connect to server as they try to connect by TCP.
This problem is a ChatGPT conclusion and seems fair and adequate, I believe it.
Setup
FRP server is available on https://example.com/frp/server;
FRP server dashboard is on https://example.com/frp/dashboard.
I just setup Caddy server by this repo and never touch it. It refreshes Caddyfile config dynamically once new Docker container in caddy network is created, modified or removed.
Architecture that I try represent:
flowchart TD
aa(remote user) -.->|https://example.com/api/path| caddyserver
subgraph VPS
caddyserver(Caddy server) -.-> |https://127.0.0.1:80/,\nhttps://127.0.0.1:443/| frp
subgraph CaddyNetwork
frp(frp) -->|https://172.27.0.4:84\nor whatever internal IP Docker gives| b(tunnel server)
end
end
b ===|https tunnel| c(tunnel client: 172.19.0.3)
subgraph home server
c -->|frpc in network_host mode| d(frp)
d -->|http| e(app)
end
DOMAIN=example.com # your domain
CADDY_PATH=frp # must be present, or it produces bugs. Example value: `frps`
FRPS_SERVER_PORT=7000 # the port of the server
FRPS_DASHBOARD_PORT=7500 # the port of the dashboard
frpc | login to the server failed: dial tcp: lookup example.com/frp: no such host. With loginFailExit enabled, no additional retries will be attempted
frpc | 2024-04-18 17:00:14.523 [I] [sub/root.go:142] start frpc service for config file [/etc/frp/frpc.toml]
frpc | 2024-04-18 17:00:14.523 [I] [client/service.go:294] try to connect to server...
frpc | 2024-04-18 17:00:14.524 [W] [client/service.go:297] connect to server error: dial tcp: lookup example.com/frp: no such host
frpc | 2024-04-18 17:00:14.524 [I] [sub/root.go:160] frpc service for config file [/etc/frp/frpc.toml] stopped
Server (frps) displays nothing like client did not succeed to connect to it.
Since frps is inside caddy network, I check caddy and found nothing, too.
Affected area
Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others
The text was updated successfully, but these errors were encountered:
Bug Description
WhoAmI
Hi, a frontend guy that not so skilled in network stack is here.
What I try to do
I try to make FRP server fully isolated so it should work inside
caddy
network through Caddy server. (Is that even possible?)Problem
The problem: since
frps
on VPS machine is working through Caddy server, it is accessible only by HTTP(S). While I can open dashboard in browser, any offrpc
could not connect to server as they try to connect by TCP.This problem is a ChatGPT conclusion and seems fair and adequate, I believe it.
Setup
https://example.com/frp/server
;https://example.com/frp/dashboard
.I use lucaslorentz/caddy-docker-proxy repo that makes Caddy server setup even easier.
I just setup Caddy server by this repo and never touch it. It refreshes
Caddyfile
config dynamically once new Docker container incaddy
network is created, modified or removed.Architecture that I try represent:
frpc Version
0.56.0
frps Version
0.56.0
System Architecture
linux/amd64
Configurations
Why does not frpc connect to frps?
SERVER
~/caddy/docker-compose.yml:
~/frp/.env
~/frp/docker-compose.yml:
~/frp/config-frps/frps.toml
CLIENT:
~/frp/config-frpc/frpc.toml
~/frp/docker-compose.yml:
Logs
Client (frpc) says:
Server (frps) displays nothing like client did not succeed to connect to it.
Since frps is inside
caddy
network, I check caddy and found nothing, too.Affected area
The text was updated successfully, but these errors were encountered: