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.

Sign up for GitHub

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

Jump to bottom

[Request] About midjourney's proxy address #2552

Open
BInodes-official opened this issue May 18, 2024 · 2 comments
Open

[Request] About midjourney's proxy address #2552

BInodes-official opened this issue May 18, 2024 · 2 comments
Labels
🌠 Feature Request New feature or request | 特性与建议 Inactive No response in 30 days | 超过 30 天未活跃

Comments

@BInodes-official
Copy link

🥰 需求描述

Through testing, I have discovered that the proxy address for midjourney must be a self-hosted HTTPS address, and this proxy must be openly accessible without being restricted by firewall IP policies for private access.
This poses a significant challenge to security.
My requirements are:

  1. Without using HTTPS, I only need to set up a proxy on the server's local address 127.0.0.1 and access it directly.
  2. Alternatively, it can be set directly in the Docker parameters, such as -e MIDJOURNEY_PROXY_URL=https://XXXXX. It does not need to be displayed on the web or externally, but this solution still poses a risk of the HTTPS proxy being accessed by others.

🧐 解决方案

To deploy the midjourney's proxy directly on the server's localhost 127.0.0.1, for example, on port 3382 (as in 127.0.0.1:3382). lobe-chat can interact with https://midjourney.chat-plugin.lobehub.com/ by accessing the midjourney's proxy through http://127.0.0.1:3382/.

📝 补充信息

No response
@BInodes-official BInodes-official added the 🌠 Feature Request New feature or request | 特性与建议 label May 18, 2024
@lobehubbot
Copy link
Member

👀 @zhoufann9188

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

@BInodes-official
Copy link
Author

i read the github project midjourney-proxy again. i found the parameter :

<html>
<body>
<!--StartFragment-->
mj.api-secret | 否 | 接口密钥，为空不启用鉴权；调用接口时需要加请求头 mj-api-secret
-- | -- | --
<!--EndFragment-->
</body>
</html>

If so, I think using HTTPS for the proxy of midjourney may be more secure, but the following two conditions need to be met:

  1. lobe-chart can configure the midjourney proxy address and corresponding request header mj-api-secret in the Docker startup parameters.
  2. Is it possible to interact without forcing the use of port 443, but instead allowing any specified port?

@lobehubbot lobehubbot added the Inactive No response in 30 days | 超过 30 天未活跃 label Jul 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🌠 Feature Request New feature or request | 特性与建议 Inactive No response in 30 days | 超过 30 天未活跃
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@BInodes-official @lobehubbot