-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Hmmm… can't reach this page #76
Comments
Please use this version, the recent update has encountered some problems, I am working on it. https://github.com/lencx/ChatGPT/releases/tag/v0.5.1 |
Sure, sure. Thank you. 0.5.1 is working perfectly. Really good work by you! |
Please try v0.6.9, the problem should be fixed. |
Ok, I installed it. The same error is still present. |
This problem looks like a network reason, are you sure v0.5.1 is working? Because they are the same way of working. |
You are right. I am using Kaspersky and it is notorious for causing these
Firewall blockade issues.
Though 0.5.1 was not blocked at all, 0.6.9 was blocked. I've unblocked it
however.
Thanks for your insight.
…On Sun, 25 Dec 2022 at 00:29, lencx ***@***.***> wrote:
This problem looks like a network reason, are you sure v0.5.1 is working?
Because they are the same way of working.
—
Reply to this email directly, view it on GitHub
<#76 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALWX7DECUPUAJY5LDNVCWLDWO5B2BANCNFSM6AAAAAATIQNNH4>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
So currently 0.6.9 is working? Then you can use the sync feature too, it should work now. |
Yes, it is working. Thanks again!
…On Sun, 25 Dec 2022 at 00:48, lencx ***@***.***> wrote:
So currently 0.6.9 is working? Then you can use the sync feature too, it
should work now.
—
Reply to this email directly, view it on GitHub
<#76 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALWX7DHW6KEZ6KC3BGXOSO3WO5D7ZANCNFSM6AAAAAATIQNNH4>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
The previous version was working just fine. Don't know what happened with this one.
Could someone direct me to the older version please?
The text was updated successfully, but these errors were encountered: