Skip to content
This repository has been archived by the owner on Sep 13, 2023. It is now read-only.

Is there anyway to bypass the proxy rate limit? #94

Open
MichaelZhouwang opened this issue Jul 5, 2023 · 8 comments
Open

Is there anyway to bypass the proxy rate limit? #94

MichaelZhouwang opened this issue Jul 5, 2023 · 8 comments

Comments

@MichaelZhouwang
Copy link

I want to use revChatGPT with multiple access tokens(without ChatGPT plus). Is there any way I can bypass the 5 request per 10 seconds rate limit for the proxy? For example, can I build my own proxy and set a higher rate limit? Or can I use an IP pool to use different IPs? Where exactly does this rate limit come from? Thanks!

@acheong08
Copy link
Owner

acheong08 commented Jul 5, 2023

For example, can I build my own proxy and set a higher rate limit

yes. the reason for rate limit is due to previous spam/abuse. I set it up so the server wont crash

@MichaelZhouwang
Copy link
Author

Hey I'm not getting "too many requests in one hour" message even with many access tokens and my own proxy server. I think it's an IP-based rate limit. But it seems the proxy used in the revChatGPT repo is not limited by the same limitation. How should I bypass this limit? Thanks!

@bi1101
Copy link

bi1101 commented Jul 23, 2023

Can you be clearer?

I suspect the churchless server also use dynamic proxy in addition to the reverse proxy to by pass the IP rate limitation, considering they are a public server with tons of traffic

If you want to by pass the IP limit, you could use dynamic proxy too.

Can anyone confirm this?

@acheong08
Copy link
Owner

_puid cookie

@bi1101
Copy link

bi1101 commented Jul 24, 2023

Hmm, I use puid (from plus account) on both the chat api and my own proxy too but still encounter some rate limit.

However, I didnot encounter any rate limit when I use the churchless bypass with the same puid.

In fact, I run the same spam test with both proxy and the churchless server but the churchless server has has way higher rate limit.

From my point of view, the only difference is the server IP or some fingerprints.

Do you have any idea why this is?

@acheong08
Copy link
Owner

acheong08 commented Jul 24, 2023

From my point of view, the only difference is the server IP or some fingerprints.

Probably server IP. The binary running on churchless is directly deployed from releases & built by GitHub actions without any changes

@bi1101
Copy link

bi1101 commented Aug 4, 2023

This is probably a dumb question but how exactly do you set the puid?

I tried setting it in the .env file and using the admin API but the limit per hour still happens even with plus account.

But when I use the proxy on bypass.churchless the limit is gone

This is really puzzling and since the latest update to the chat.openai.com endpoint we have to use reverse proxy to make calls so I don't want to put tons of load on the churchless server

@acheong08
Copy link
Owner

I tried setting it in the .env file and using the admin API but the limit per hour still happens even with plus account.

Using the admin API should do it. Or PUID=<_puid cookie> ./ChatGPTProxy

It might or might not work. Not sure what is going on. bypass.churchless.tech is no longer using a valid PUID since I don't have a Plus account anymore but it continues to work

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants