【开源】你们要的一键脚本部署naiveproxy

格孑孑

绑定

Erik

在7楼 发表于 2023-1-7 11:25
可以的。

如果只是部署时单纯想修改伪装站点，可以在部署脚本最后加上参数-f或--fake-host：

多谢大佬

b66667777

支持一下

joshuabu

666

cici9911

这个岂不是会占用80和443？

hanjibin

环境：ovh  ubuntu22.04
已知：
root@vps-f5e18458:~/naive# docker -v && docker-compose -v
Docker version 20.10.22, build 3a2c30b
docker-compose version 1.29.2, build 5becea4c
问题：
docker: 'compose' is not a docker command.
See 'docker --help'

hanjibin

手动启动docker，申请成功证书，但是节点无法连接
工具：小火箭
协议：https 和 http2都试了

docker日志：
root@vps-f5e18458:~/naive# docker-compose logs -f
Attaching to naiveproxy
naiveproxy | 2023/01/07 07:20:51.301    INFO    using provided configuration    {"config_file": "/data/Caddyfile", "config_adapter": ""}
naiveproxy | 2023/01/07 07:20:51.305    WARN    Caddyfile input is not formatted; run the 'caddy fmt' command to fix inconsistencies    {"adapter": "caddyfile", "file": "/data/Caddyfile", "line": 4}
naiveproxy | 2023/01/07 07:20:51.311    INFO    admin   admin endpoint started  {"address": "localhost:2019", "enforce_origin": false, "origins": ["//localhost:2019", "//[::1]:2019", "//127.0.0.1:2019"]}
naiveproxy | 2023/01/07 07:20:51.317    INFO    http    server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS {"server_name": "srv1", "https_port": 443}
naiveproxy | 2023/01/07 07:20:51.318    INFO    http    enabling automatic HTTP->HTTPS redirects        {"server_name": "srv1"}
naiveproxy | 2023/01/07 07:20:51.326    INFO    http.log        server running  {"name": "srv0", "protocols": ["h1", "h2", "h3"]}
naiveproxy | 2023/01/07 07:20:51.333    INFO    http    enabling HTTP/3 listener        {"addr": ":443"}
naiveproxy | 2023/01/07 07:20:51.334    INFO    failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details.
naiveproxy | 2023/01/07 07:20:51.335    INFO    http.log        server running  {"name": "srv1", "protocols": ["h1", "h2", "h3"]}
naiveproxy | 2023/01/07 07:20:51.341    INFO    http.log        server running  {"name": "remaining_auto_https_redirects", "protocols": ["h1", "h2", "h3"]}
naiveproxy | 2023/01/07 07:20:51.341    INFO    http    enabling automatic TLS certificate management   {"domains": ["ovh.cclcdq.ga"]}
naiveproxy | 2023/01/07 07:20:51.343    INFO    autosaved config (load with --resume flag)      {"file": "/root/.config/caddy/autosave.json"}
naiveproxy | 2023/01/07 07:20:51.348    INFO    serving initial configuration
naiveproxy | 2023/01/07 07:20:51.344    INFO    tls.obtain      acquiring lock  {"identifier": "ovh.cclcdq.ga"}
naiveproxy | 2023/01/07 07:20:51.332    INFO    tls     cleaning storage unit   {"description": "FileStorage:/root/.local/share/caddy"}
naiveproxy | 2023/01/07 07:20:51.350    INFO    tls     finished cleaning storage units
naiveproxy | 2023/01/07 07:20:51.324    INFO    tls.cache.maintenance   started background certificate maintenance      {"cache": "0xc00026d3b0"}
naiveproxy | Successfully started Caddy (pid=11) - Caddy is running in the background
naiveproxy | tail: 2023/01/07 07:20:51.357      INFO    tls.obtain      lock acquired   {"identifier": "ovh.cclcdq.ga"}
naiveproxy | 2023/01/07 07:20:51.358    INFO    tls.obtain      obtaining certificate   {"identifier": "ovh.cclcdq.ga"}
naiveproxy | cannot open 'tail' for reading: No such file or directory
naiveproxy | ==> /dev/null <==
naiveproxy | 2023/01/07 07:20:51.584    INFO    http    waiting on internal rate limiter        {"identifiers": ["ovh.cclcdq.ga"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": "[email protected]"}
naiveproxy | 2023/01/07 07:20:51.585    INFO    http    done waiting on internal rate limiter   {"identifiers": ["ovh.cclcdq.ga"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": "[email protected]"}
naiveproxy | 2023/01/07 07:20:51.689    INFO    http.acme_client        trying to solve challenge       {"identifier": "ovh.cclcdq.ga", "challenge_type": "http-01", "ca": "https://acme-v02.api.letsencrypt.org/directory"}
naiveproxy | 2023/01/07 07:20:51.921    INFO    http    served key authentication       {"identifier": "ovh.cclcdq.ga", "challenge": "http-01", "remote": "54.218.60.222:56178", "distributed": false}
naiveproxy | 2023/01/07 07:20:51.938    INFO    http    served key authentication       {"identifier": "ovh.cclcdq.ga", "challenge": "http-01", "remote": "23.178.112.103:27854", "distributed": false}
naiveproxy | 2023/01/07 07:20:51.982    INFO    http    served key authentication       {"identifier": "ovh.cclcdq.ga", "challenge": "http-01", "remote": "18.217.58.150:38158", "distributed": false}
naiveproxy | 2023/01/07 07:20:52.329    INFO    http.acme_client        authorization finalized {"identifier": "ovh.cclcdq.ga", "authz_status": "valid"}
naiveproxy | 2023/01/07 07:20:52.330    INFO    http.acme_client        validations succeeded; finalizing order {"order": "https://acme-v02.api.letsencrypt.org/acme/order/905462177/157371397887"}
naiveproxy | 2023/01/07 07:20:53.119    INFO    http.acme_client        successfully downloaded available certificate chains    {"count": 2, "first_url": "https://acme-v02.api.letsencrypt.org/acme/cert/039da2610aa7ca288bb7a7e24fb4e11e9f87"}
naiveproxy | 2023/01/07 07:20:53.121    INFO    tls.obtain      certificate obtained successfully       {"identifier": "ovh.cclcdq.ga"}
naiveproxy | 2023/01/07 07:20:53.122    INFO    tls.obtain      releasing lock  {"identifier": "ovh.cclcdq.ga"}

makizhang

先收藏一波顺便点个星星

kukuyan

感谢分享收藏了

hanjibin

伪装站点正常，配置域名用户名密码正确，修复好了我重装看看