Comments (8)
得看你的设置怎么配置的,地区 proxy 留空就是 直连
如果是自己用的,建议直接 nginx 反代 就可以了,多人用才用 特殊后端 处理 并 缓存
如果还是不清楚哪里出问题,打开 debug 查 log
from biliroaming-go-server-docker.
得看你的设置怎么配置的,地区 proxy 留空就是 直连 如果是自己用的,建议直接 nginx 反代 就可以了,多人用才用 特殊后端 处理 并 缓存
如果还是不清楚哪里出问题,打开 debug 查 log
问一下这里所说的更改password文件是什么意思,docker的话是不会访问我主机的数据库吧,那这个密码要改成什么?
修改 PostgreSQL 数据库密码 db/password.txt
我最初的时候更改了端口,因为我80和443被本地的Nginx占用了,我就修改了一下端口然后用Nginx代理了一下域名指向端口,这个会影响我那个地区问题吗?
from biliroaming-go-server-docker.
问一下这里所说的更改password文件是什么意思,docker的话是不会访问我主机的数据库吧,那这个密码要改成什么?
这里对应这个文件吧 db/password.txt
其实可以不改,外部 应该不能 访问 内部数据库,docker exec
查数据库用
我最初的时候更改了端口,因为我80和443被本地的Nginx占用了,我就修改了一下端口然后用Nginx代理了一下域名指向端口,这个会影响我那个地区问题吗?
如果你有外部 nginx
,建议直接用外部的 docker-compose.yml
外部 nginx 直接反代到 docker 端口,docker 端口这里改,改左边那个,右边的要对应 config/config.yml
biliroaming-go-server-docker/docker-compose.yml
Lines 11 to 13 in 5ffacf5
from biliroaming-go-server-docker.
问一下这里所说的更改password文件是什么意思,docker的话是不会访问我主机的数据库吧,那这个密码要改成什么?
这里对应这个文件吧
db/password.txt
其实可以不改,外部 应该不能 访问 内部数据库,
docker exec
查数据库用我最初的时候更改了端口,因为我80和443被本地的Nginx占用了,我就修改了一下端口然后用Nginx代理了一下域名指向端口,这个会影响我那个地区问题吗?
如果你有外部
nginx
,建议直接用外部的docker-compose.yml
外部 nginx 直接反代到 docker 端口,docker 端口这里改,改左边那个,右边的要对应config/config.yml
biliroaming-go-server-docker/docker-compose.yml
Lines 11 to 13 in 5ffacf5
是的,我就是用这样的方式修改了端口,然后使用Nginx反代
我重新部署了这个项目,没有变更任何东西,但是却出现了报错
{"level":"info","ts":1659858148.822775,"caller":"builder/main.go:231","msg":"Version: v2.16.0"} {"level":"fatal","ts":1659858148.8304217,"caller":"builder/main.go:276","msg":"pq: password authentication failed for user \"postgres\"","stacktrace":"main.main\n\t/tmp/builder/main.go:276\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"} {"level":"info","ts":1659858149.5067742,"caller":"builder/main.go:231","msg":"Version: v2.16.0"} {"level":"fatal","ts":1659858149.5138004,"caller":"builder/main.go:276","msg":"pq: password authentication failed for user \"postgres\"","stacktrace":"main.main\n\t/tmp/builder/main.go:276\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"} {"level":"info","ts":1659858150.1459754,"caller":"builder/main.go:231","msg":"Version: v2.16.0"} {"level":"fatal","ts":1659858150.1528046,"caller":"builder/main.go:276","msg":"pq: password authentication failed for user \"postgres\"","stacktrace":"main.main\n\t/tmp/builder/main.go:276\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"} {"level":"info","ts":1659858150.9448557,"caller":"builder/main.go:231","msg":"Version: v2.16.0"} {"level":"fatal","ts":1659858150.9521327,"caller":"builder/main.go:276","msg":"pq: password authentication failed for user \"postgres\"","stacktrace":"main.main\n\t/tmp/builder/main.go:276\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"} {"level":"info","ts":1659858152.146387,"caller":"builder/main.go:231","msg":"Version: v2.16.0"} {"level":"fatal","ts":1659858152.1538813,"caller":"builder/main.go:276","msg":"pq: password authentication failed for user \"postgres\"","stacktrace":"main.main\n\t/tmp/builder/main.go:276\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"} {"level":"info","ts":1659858154.155898,"caller":"builder/main.go:231","msg":"Version: v2.16.0"} {"level":"fatal","ts":1659858154.1629388,"caller":"builder/main.go:276","msg":"pq: password authentication failed for user \"postgres\"","stacktrace":"main.main\n\t/tmp/builder/main.go:276\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"}
我在第一次部署这个项目的时候在本地也创建了pgsql的库并且修改了文件中的用户名密码,后来我把它删了
from biliroaming-go-server-docker.
from biliroaming-go-server-docker.
问一下这里所说的更改password文件是什么意思,docker的话是不会访问我主机的数据库吧,那这个密码要改成什么?
这里对应这个文件吧
db/password.txt
其实可以不改,外部 应该不能 访问 内部数据库,
docker exec
查数据库用我最初的时候更改了端口,因为我80和443被本地的Nginx占用了,我就修改了一下端口然后用Nginx代理了一下域名指向端口,这个会影响我那个地区问题吗?
如果你有外部
nginx
,建议直接用外部的docker-compose.yml
外部 nginx 直接反代到 docker 端口,docker 端口这里改,改左边那个,右边的要对应config/config.yml
biliroaming-go-server-docker/docker-compose.yml
Lines 11 to 13 in 5ffacf5
另外就是您在biliroaming-go-server中./biliroaming-go-server这个指令,我没有在目录下找到对应的执行文件,是因为go语言需要编译吗?
from biliroaming-go-server-docker.
预编译了,https://github.com/JasonKhew96/biliroaming-go-server/blob/main/.github/workflows/docker.yml
除了配置文件,全都在 容器 里
from biliroaming-go-server-docker.
预编译了,https://github.com/JasonKhew96/biliroaming-go-server/blob/main/.github/workflows/docker.yml 除了配置文件,全都在 容器 里
好的,我这边再试试,打扰您了
from biliroaming-go-server-docker.
Related Issues (5)
- 无法正常使用 HOT 4
- 提示账号未登录 HOT 2
- 关于backend-1的端口占用 HOT 1
- 求教大佬们,运行报错:原因: {"code":429,"message":"解析服务器: 请求过于频繁!"} HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from biliroaming-go-server-docker.