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

[Bug] API Key Misconfiguration - Custom Model Usage Consumes AIHubMix Tokens Instead of Personal Keys #6312

Open
varcoh opened this issue Feb 28, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@varcoh
Copy link

varcoh commented Feb 28, 2025

📦 部署方式

Other

📌 软件版本

V2.15.8

💻 系统环境

Ubuntu

📌 系统版本

24

🌐 浏览器

Edge

📌 浏览器版本

133.0.3065.82

🐛 问题描述

I am using an API Key obtained from AIHubMix and have set the BASE_URL in my .env file as follows:

BASE_URL=https://aihubmix.com

I have also added specific models in the custom settings, which work correctly. I can verify that token consumption details appear on AIHubMix.

However, I have separately applied for a DeepSeek API Key and configured it in my .env file:

DEEPSEEK_API_KEY=sk-XXXXX
DEEPSEEK_URL=https://api.deepseek.com

I then added the following custom model setting:

+deepseek-chat=DeepSeek

But when I use DeepSeek, it still consumes tokens from AIHubMix instead of my personal DeepSeek API Key.

Similarly, I applied for a Grok API Key and configured it as follows:

GROK_API_KEY=xai-XXXXX
GROK_URL=https://api.x.ai/v1

However, when using Grok, it also consumes AIHubMix tokens instead of my personal Grok API Key.

Where could the issue be? Is there an additional configuration required to ensure that DeepSeek and Grok use my personal API keys instead of AIHubMix?

Looking forward to your guidance. Thanks!

Image

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

No response

@varcoh varcoh added the bug Something isn't working label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant