-
Notifications
You must be signed in to change notification settings - Fork 115
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
failed to start #112
Comments
你的config.json有问题 |
这个是梯子问题还是 api url的问题我用的是这个https://api.chatgpt.com/v1/generate [ERROR][2024-02-15 23:29:21][api.py:46] - Get personal info failed! |
这个报错像是你的dll没有注入成功,所以程序连接不到微信。你按照注入操作执行了吗,是否有看到inject success ? |
注入过了我在试下看看 |
成功启动了但是gpt回复I cannot connect the server, please check the network and try again 是梯子的问题么 |
这是你的反代地址吗?连接超时既可能是url服务有问题,也可能是梯子问题。如果这是你的反代地址,那应该不加generate;如果是中转站买的key,那就参考中转站的站点配置。 |
不加generate也不行 那个 "openai_api_base"用的是这个"https://api.chatgpt.com/v1", |
测了一下,是那个反代地址已经失效了。你如果是官方的key,能魔法,你就直接用官方的地址:"https://api.openai.com/v1",如果不想架梯子,可以用我的反代地址:【】。 |
这个是啥情况 |
key 没钱了或者过期了 |
Search for answers in existing issues
Python version
python 3.10
Issue description
[ERROR][2024-02-13 12:09:38][app.py:22] - App startup failed!
[ERROR][2024-02-13 12:09:38][app.py:23] - Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
File "C:\Users\Gne\Desktop\wechat-gptbot-main\app.py", line 11, in
load_config()
File "C:\Users\Gne\Desktop\wechat-gptbot-main\config.py", line 16, in load_config
config = json.loads(config_str)
File "C:\Users\Gne\AppData\Local\Programs\Python\Python310\lib\json_init_.py", line 346, in loads
return _default_decoder.decode(s)
File "C:\Users\Gne\AppData\Local\Programs\Python\Python310\lib\json\decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "C:\Users\Gne\AppData\Local\Programs\Python\Python310\lib\json\decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
Repro steps
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: