使用 Docker Compose 部署 LobeChat 服务端数据库版本时候遇到Logto 404的错误 #3678
-
📦 EnvironmentDocker 📌 Versionv1.14.9 💻 Operating SystemOther Linux 🌐 BrowserChrome 🐛 Bug Description访问: docker compose使用的是: 相关域名默认用的是demo的域名,仅仅做了如下调整:
应该不是反向代理的问题,因为minio的 ui界面就可以正常访问 docker ps情况如下:
📷 Recurrence Steps
🚦 Expected Behavior可以正常打开Logto 📝 Additional InformationNo response |
Beta Was this translation helpful? Give feedback.
Replies: 18 comments 2 replies
-
|
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
Beta Was this translation helpful? Give feedback.
-
|
域名解析在Cloudflare上？ |
Beta Was this translation helpful? Give feedback.
-
Domain name resolution on Cloudflare? |
Beta Was this translation helpful? Give feedback.
-
不是的, 本机配置的域名. window下使用vm安装的centos系统,docker跑在centos上的. ip是192.168.1.129 |
Beta Was this translation helpful? Give feedback.
-
No, the domain name is configured locally. The centos system is installed using vm under window, and docker runs on centos. The IP is 192.168.1.129 |
Beta Was this translation helpful? Give feedback.
-
|
windows上不是可以直接本地部署吗？没必要在虚拟机上部署吧。 |
Beta Was this translation helpful? Give feedback.
-
Isn’t it possible to deploy directly locally on Windows? There is no need to deploy it on a virtual machine. |
Beta Was this translation helpful? Give feedback.
-
写后端比较多一些.之前一直在centos下开发. 不过这个环境理论上应该也是能支持的吧[实际我们到时候内网部署时候,也是类似的情况,内网的centos,内网的域名]? 不是很理解为啥会404 docker logs 里能看到Logto 是输出成功的,没有报错 |
Beta Was this translation helpful? Give feedback.
-
I write more backends. I have been developing under centos before. But in theory, this environment should be able to support it, right [actually when we deploy the intranet, it will be a similar situation, centos on the intranet, domain name on the intranet]? I don’t quite understand why it’s 404 You can see in docker logs that Logto output is successful and no error is reported. |
Beta Was this translation helpful? Give feedback.
-
|
你这个问题我也遇到过，我是域名解析在CF上，开启了小黄云代理。在CF上把代理关了就没问题了。 |
Beta Was this translation helpful? Give feedback.
-
I have also encountered your problem. I resolved the domain name on CF and enabled the Xiaohuangyun proxy. If you turn off the proxy on CF, there will be no problem. |
Beta Was this translation helpful? Give feedback.
-
|
这个我也遇到了，3001和3002全部反代理就解决了 |
Beta Was this translation helpful? Give feedback.
-
I also encountered this problem. It was solved by anti-proxying all 3001 and 3002. |
Beta Was this translation helpful? Give feedback.
-
我也遇到了，本地部署，直接打开，和反代应该没关系 |
Beta Was this translation helpful? Give feedback.
-
我上午都配置了的反向代理,依然还是 404. lobe-auth-api.example.com 的 |
Beta Was this translation helpful? Give feedback.
-
请问你解决了吗？ |
Beta Was this translation helpful? Give feedback.
-
|
建个用户试一下
在 2024年8月30日星期五，vannchic ***@***.***> 写道：
… 这个我也遇到了，3001和3002全部反代理就解决了
我上午都配置了的反向代理,依然还是 404.
lobe-auth-ui.example.com 的
image.png (view on web)
<https://github.com/user-attachments/assets/588d9f96-857a-460a-841c-b4c8baa28c7c>
lobe-auth-api.example.com 的
image.png (view on web)
<https://github.com/user-attachments/assets/7fb82d23-ab93-4eab-bed0-a765d00a3d49>
—
Reply to this email directly, view it on GitHub
<#3673 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADYYUAWBSE4KNFQ6YH6UZGTZUAN33AVCNFSM6AAAAABNLS3D62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRQGM2DINRZHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
没理解你说的建用户. |
Beta Was this translation helpful? Give feedback.
-
|
我也遇到同样的问题，看到你也使用了宝塔面板做的反向代理，现在我怀疑是宝塔面板造成的 |
Beta Was this translation helpful? Give feedback.
-
|
如果是反代 https 的可以参考这个 issue，加个 Ngnix 配置就好了 logto-io/logto#4279 |
Beta Was this translation helpful? Give feedback.
-
|
这个方法可以，已经解决了👍 |
Beta Was this translation helpful? Give feedback.
-
请问增加的配置可以贴下吗？ |
Beta Was this translation helpful? Give feedback.
-
|
光加header还不行，似乎端口也必须是443？ |
Beta Was this translation helpful? Give feedback.
如果是反代 https 的可以参考这个 issue，加个 Ngnix 配置就好了 logto-io/logto#4279