-
Notifications
You must be signed in to change notification settings - Fork 21
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
Gemini API IP Checking? #48
Comments
Tested with multiple ip addresses and no error was found. You should use each set of cookies only in a single environment. Try a fresh login with incognito mode and copy new cookies from there when running on a remote host. |
I've tried with these, nothing worked. Even a new google account didn't work, all the credential works fine when it's on local machine, but once uploaded to a remote machine, or the proxy setting turned on, then the client will fail to auth, saying that the token is expired/etc. I can give remote access to my machine for more in-depth testing if required |
The same token is used on both Even when I generate a complete new set of token and only paste it on the remote server without running it on local, it will still error like this. it used to works fine, but all of a sudden things just stops working, even though nothing changed |
Are you able to play with https://gemini.google.com/app behind the problematic proxy or on those vps? According to google gemini is not available to some countries/regions |
I am able to use Gemini when connected to the proxy (location Germany) via the browser, the 2 VPSs are in Germany and Singapore, both are experiencing the same issue. I used to be able to use the Singapore VPS to host the bot just fine too, the issue only started recently
Best regards
THK
…On Dec 12, 2024, 11:34 PM +0700, UZQueen ***@***.***>, wrote:
Are you able to play with https://gemini.google.com/app behind the problematic proxy or on those vps? According to google gemini is not available to some countries/regions
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
It seems like Google are starting to implement an IP check or something for the API, if I use the cookie from the same IP address as the one used to generate the cookies things are fine, but once I put it on another IP (proxy/moving the source code to host machine) then the client refuses to login, anyone else experiencing that?
The text was updated successfully, but these errors were encountered: