Closed Camouflager closed 1 year ago
Hey @Camouflager but if ChatGPT is a foreground tab, does that not happen? (If not, the cause is Chrome's "tab throttling" and I will find a way to workaround))
thanks, will it work if i keep it in a separate window? I'll try and test.
thanks, will it work if i keep it in a separate window? I'll try and test.
Yes because Chrome kills background tab activity since the software is so bloated so users complained about slow computer speeds, but I think I can solve it too actually
just tried keeping the tab in a separate window, and the error still occurs :(
just tried keeping the tab in a separate window, and the error still occurs :(
I'm testing a new method by smoking to kill time and will let you know if it works (in both chrome and FF)
@Camouflager the new method seems to work!! Can you update here: https://greasyfork.org/en/scripts/462422-chatgpt-auto-refresh
After you visit chat.openai.com, press Ctrl+Shift+I to open console, then make it a background tab.
Then, much later, go back to it and you will notice requests were still sent in the background:
(the 400 response didn't seem to matter, no errors appeared for me in either FF or Chrome)
@Camouflager I tested it for over half an hour and it works in Chrome background tabs! Can you confirm the same for you? ( Can you update to 2023.04.03 @ https://greasyfork.org/en/scripts/462422-chatgpt-auto-refresh
thanks, the problem seems to be alleviated. But it still happens. And i noticed that the post status code changed from 400 to 403 when the session dies and needs refresh.
So by alleviated you mean at least it works in background tabs, but if sessions get too long the network errors appear? Also how long did it take
Hi thanks for trying to fix this, it is a useful script. It doesn't work on the latest version of Brave, see console log: chat.openai.com-1680622605787.log
Using 2023.04.04 version of your script and, Version 1.49.132 Chromium: 111.0.5563.147 (Official Build) (64-bit)
Hey @ArtificialTruth do you mean you still get network errors and/or cloudflare checks? Because your log shows it's actually working as intended (send background request every min, regardless of 403 which it does @ (5:35 and 5:36)
The other errors are for various other scripts like framework-7a789ee31d2a7534.js
, onloadwff.js
& _app-cbc5532d92566a48.js
Yes I still get network error on the chat and have to manually refresh the page in order to get a response.
I have the same issue. my browser is Edge, and from the console, I can see that the script sends a request but receives a 403 error. After asking a question, it shows "Something went wrong...".
@Liumeng404 thank you for the info I will try to fix
Same 403, watch on this.👀
Another example
@ArtificialTruth @Liumeng404 @mzvast @Camouflager I replaced the foreground method from GET to POST per @NoahXcl's solution in https://github.com/adamlui/chatgpt-auto-refresh/issues/7 can you tell me if it works now?
Still doesn't work :( Console output:
↻ ChatGPT >> Auto refresh activated
userscript.html?name=ChatGPT%2520Auto%2520Refresh%2520%25E2%2586%25BB.user.js&id=66836bbf-f137-4719-8c27-a2dbabfd7add:150 ↻ ChatGPT >> [3:54:30 PM] ChatGPT session refreshed (via POST-fetch)
/api/auth/session:1 Failed to load resource: the server responded with a status of 400 ()
2onloadwff.js:71 Assertion failed: Input argument is not an HTMLInputElement
getFormProfile @ onloadwff.js:71
userscript.html?name=ChatGPT%2520Auto%2520Refresh%2520%25E2%2586%25BB.user.js&id=66836bbf-f137-4719-8c27-a2dbabfd7add:178 ↻ ChatGPT >> [3:55:0 PM] ChatGPT session refreshed (via POST-fetch)
/api/auth/session:1 Failed to load resource: the server responded with a status of 400 ()
userscript.html?name=ChatGPT%2520Auto%2520Refresh%2520%25E2%2586%25BB.user.js&id=66836bbf-f137-4719-8c27-a2dbabfd7add:178 ↻ ChatGPT >> [3:55:30 PM] ChatGPT session refreshed (via POST-fetch)
/api/auth/session:1 Failed to load resource: the server responded with a status of 403 ()
onloadwff.js:71 Assertion failed: Input argument is not an HTMLInputElement
getFormProfile @ onloadwff.js:71
/backend-api/conversation:1 Failed to load resource: the server responded with a status of 403 ()
_app-44807f2f4dc5abc4.js:7 FatalError: Something went wrong. If this issue persists please contact us through our help center at help.openai.com.
at 264-ddc9493a71b67c4e.js:1:7424
at main-149b337e061b4d04.js:1:101106
at Object.next (main-149b337e061b4d04.js:1:101211)
at r (_app-44807f2f4dc5abc4.js:23:1497)
at a (_app-44807f2f4dc5abc4.js:23:1694)
at _app-44807f2f4dc5abc4.js:23:1753
at new Promise (
------- Original Message ------- søndag den 16. april 2023 kl. 14:16, skrev Adam Lui 刘展鹏 @.***>:
@.(https://github.com/ArtificialTruth) @.(https://github.com/Liumeng404) @.(https://github.com/mzvast) @.(https://github.com/Camouflager) I replaced the foreground method from GET to POST per @.***(https://github.com/NoahXcl)'s solution in #7 can you tell me if it works now?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
@ArtificialTruth @mzvast @Liumeng404 @Camouflager I replaced the autorefresh method w/ a new headless one I tested to work even after an hour in the latest update!
"something went wrong ..." still pops up from time to time, anyway i can help debug this?