Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot access after using nginx proxy minio service #1300

Closed
xiao-arch opened this issue Oct 30, 2023 · 5 comments
Closed

Cannot access after using nginx proxy minio service #1300

xiao-arch opened this issue Oct 30, 2023 · 5 comments
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@xiao-arch
Copy link

What happened?

消息发送图片,文件等报错
image

What did you expect to happen?

消息发送成功,可以预览图片、文件等

How can we reproduce it (as minimally and precisely as possible)?

image
.env配置:MINIO_ENDPOINT=https://jtgzjg.nxjtkj.com:10090

Anything else we need to know?

No response

version

```console $ {name} version # paste output here ```

Cloud provider

OS version

```console # On Linux: $ cat /etc/os-release # paste output here $ uname -a # paste output here # On Windows: C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture # paste output here ```

Install tools

@xiao-arch xiao-arch added the bug Categorizes issue or PR as related to a bug. label Oct 30, 2023
@kubbot kubbot changed the title 使用nginx代理minio服务后无法访问 Cannot access after using nginx proxy minio service Oct 30, 2023
@cubxxw
Copy link
Contributor

cubxxw commented Oct 30, 2023

It appears that the domain name in your hosts file may have been compromised. To resolve this issue, you can manually modify the endpoint field or use the command "export IP='xxxx' (external IP)" followed by "make init".

@xiao-arch
Copy link
Author

export IP = '42.63.105.92'是这样吗

@kubbot
Copy link
Contributor

kubbot commented Nov 3, 2023

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


Is this the case with export IP = '42.63.105.92'?

@kubbot
Copy link
Contributor

kubbot commented Jan 4, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@kubbot
Copy link
Contributor

kubbot commented Jan 12, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@kubbot kubbot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants