jasonkhew96 / biliroaming-go-server-docker Goto Github PK

{"level":"error","ts":1673160740.5811954,"caller":"builder/playurl.go:248","msg":"models: unable to upsert play_url_caches: pq: null value in column \"quality\" of relation \"play_url_caches\" violates not-null constraint","stacktrace":"main.(*BiliroamingGo).handleAndroidPlayURL\n\t/tmp/builder/playurl.go:248\nmain.initHttpServer.func1\n\t/tmp/builder/main.go:194\ngithub.com/valyala/fasthttp.(*Server).serveConn\n\t/go/pkg/mod/github.com/valyala/[email protected]/server.go:2338\ngithub.com/valyala/fasthttp.(*workerPool).workerFunc\n\t/go/pkg/mod/github.com/valyala/[email protected]/workerpool.go:224\ngithub.com/valyala/fasthttp.(*workerPool).getCh.func1\n\t/go/pkg/mod/github.com/valyala/[email protected]/workerpool.go:196"}

curl http://api.bilibili.com/x/web-interface/zone 的结果
{"code":0,"message":"0","ttl":1,"data":{"addr":"*****8","country":"香港","isp":"amazon.com","latitude":*****,"longitude":******,"zone_id":******,"country_code":852}}

直接挂v2到节点能看

手机上也重新登录好几次
我换了好几个服务器都一样.
用php版太慢了.

如题
在隔壁那个go弄了半天之后，我觉得还是docker好弄，就来搞了一下
弄完之后测试了一下，直接访问域名能看到我留下的index.html
但是在进番剧的时候，却提示您所在的地区不可看
我的服务器确实是处于香港的，之前用过php版的，但是那个在我换域名之后响应变得特别慢，就来试试这个

请教一下，这个端口映射在哪里修改？

[+] Running 1/2
 ⠿ Container biliroaming-go-server-docker-master-db-1       Running                             0.0s
 ⠴ Container biliroaming-go-server-docker-master-backend-1  Starting                            0.5s
Error response from daemon: driver failed programming external connectivity on endpoint biliroaming-go-server-docker-master-backend-1 (73710a6cb83a9a8ba6f04cdea3deda8fcb202ff3b0a7df312a20bc88cc34d0da): Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use

运行模式：
宝塔面板，先部署docker后，从宝塔面板进行反代
相关设置：
未在proxy/certs/放证书
docker-compose 更改设置：

    # 映射端口:容器端口
    ports:
      - 7096:7095

docker-compose-http 更改设置：

    # 映射端口:容器端口
    ports:
      - 7096:7095

config/config.yml 更改设置：

    # 监听端口
port: 7095

运行后无论是ip:7096还是反代的域名均可正常显示此页面：
图1
B站脚本测速正常

但是使用解锁B站番剧会报错：
图2

docker日志如下：
{"level":"info","ts":1680364906.3190937,"caller":"builder/main.go:233","msg":"Version: 2.25.1"}
{"level":"fatal","ts":1680364906.3333013,"caller":"builder/main.go:278","msg":"pq: the database system is starting up","stacktrace":"main.main\n\t/tmp/builder/main.go:278\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"}
{"level":"info","ts":1680364908.0177362,"caller":"builder/main.go:233","msg":"Version: 2.25.1"}
{"level":"fatal","ts":1680364908.0374112,"caller":"builder/main.go:278","msg":"pq: the database system is starting up","stacktrace":"main.main\n\t/tmp/builder/main.go:278\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"}
{"level":"info","ts":1680364909.6792326,"caller":"builder/main.go:233","msg":"Version: 2.25.1"}
{"level":"fatal","ts":1680364909.6885643,"caller":"builder/main.go:278","msg":"pq: the database system is starting up","stacktrace":"main.main\n\t/tmp/builder/main.go:278\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"}
{"level":"info","ts":1680364911.3588006,"caller":"builder/main.go:233","msg":"Version: 2.25.1"}
Applied 0 migrations!
{"level":"info","ts":1680364911.4382117,"caller":"builder/main.go:209","msg":"Listening on :7095 ..."}
2023/04/01 16:02:41 0.000 #0000000200000001 - 172.18.0.3:7095<->138.2.90.*:30094 - GET http://******我的IP:7096/favicon.ico - cannot open file "/runner/html/favicon.ico": open /runner/html/favicon.ico: no such file or directory
2023/04/01 16:03:00 0.000 #0000000400000001 - 172.18.0.3:7095<->172.18.0.1:56506 - GET http://我的域名/favicon.ico - cannot open file "/runner/html/favicon.ico": open /runner/html/favicon.ico: no such file or directory

已尝试操作：
将容器内端口还原为80
将映射文件权限给777
修改反代配置
无果

猜测：
是不是宝塔面板的反代的配置少了这其中的部分配置？

server {
    # https
    listen  443 ssl;
    listen  [::]:443 ssl;

    server_name         bili.example.com;

    # 证书
    ssl_certificate     /etc/nginx/certs/site.crt;
    ssl_certificate_key /etc/nginx/certs/site.key;

    # 限制客户端请求大小
    client_max_body_size 1M;

    # 获取 CLOUDFLARE 真实 IP
    # https://support.cloudflare.com/hc/en-us/articles/200170786-Restoring-original-visitor-IPs
    # https://www.cloudflare.com/ips/
    # ipv4
    set_real_ip_from    173.245.48.0/20;
    set_real_ip_from    103.21.244.0/22;
    set_real_ip_from    103.22.200.0/22;
    set_real_ip_from    103.31.4.0/22;
    set_real_ip_from    141.101.64.0/18;
    set_real_ip_from    108.162.192.0/18;
    set_real_ip_from    190.93.240.0/20;
    set_real_ip_from    188.114.96.0/20;
    set_real_ip_from    197.234.240.0/22;
    set_real_ip_from    198.41.128.0/17;
    set_real_ip_from    162.158.0.0/15;
    set_real_ip_from    172.64.0.0/13;
    set_real_ip_from    131.0.72.0/22;
    set_real_ip_from    104.16.0.0/13;
    set_real_ip_from    104.24.0.0/14;
    # ipv6
    set_real_ip_from    2400:cb00::/32;
    set_real_ip_from    2606:4700::/32;
    set_real_ip_from    2803:f800::/32;
    set_real_ip_from    2405:b500::/32;
    set_real_ip_from    2405:8100::/32;
    set_real_ip_from    2a06:98c0::/29;
    set_real_ip_from    2c0f:f248::/32;

    # 2 选 1
    real_ip_header CF-Connecting-IP;
    # real_ip_header X-Forwarded-For;

    location / {
        proxy_pass  http://127.0.0.1:80;
    }
}

请求大佬们解答，十分感谢！