Gemini API IP Checking?

[UnitTHK]

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?

[HanaokaYuzu]

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.

[UnitTHK]

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

[UnitTHK]

Result on remote server:

Result on local machine:

[UnitTHK]

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's not an IP ban either, cause it happens on multiple of my VPSes, even ones that are freshly created for testing, so I really don't get wtf is going on

it used to works fine, but all of a sudden things just stops working, even though nothing changed

[HanaokaYuzu]

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

[UnitTHK]

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: ***@***.***>

[gaoym121]

I can access the API normally from my VPS (US location). Please verify that you're using the same cookie values locally and remotely, particularly the Secure_1PSIDTS value.

Troubleshooting steps:

1. Uninstall browser-cookie3
2. Delete cache from /usr/local/lib/python3.12/site-packages/gemini_webapi/utils/temp
3. Add debug logging to verify cookie values:

async def send_request(cookies: dict) -> tuple[Response | None, dict]:
    logger.debug(f"Init attempt - Source: Cookies: {cookies}")
    async with AsyncClient(
        proxy=proxy,
        headers=Headers.GEMINI.value, 
        cookies=cookies,
        follow_redirects=True,
    ) as client:
        try:
            response = await client.get(Endpoint.INIT.value)
            response.raise_for_status()
            logger.debug(f"Init attempt - Status Code: {response.status_code}")

This will help confirm both environments are using identical cookie values.

[UnitTHK]

Yes, I can verify that the same cookie are being used both locally and remotely, it's literally being hardcoded in and the docker container for it is being rebuilt (with new dependencies builds) every push, I implemented a /eval command and run a few debugs command to verify that the same cookies are being used before, and the resulting printed cookies are matching the one hardcoded in and used on init, so I don't get what's going on either

…

On Wed, Feb 5, 2025 at 7:47 PM gaoym121 ***@***.***> wrote: I can access the API normally from my VPS (US location). Please verify that you're using the same cookie values locally and remotely, particularly the Secure_1PSIDTS value. Troubleshooting steps: 1. Uninstall browser-cookie3 2. Delete cache from /usr/local/lib/python3.12/site-packages/gemini_webapi/utils/temp 3. Add debug logging to verify cookie values: async def send_request(cookies: dict) -> tuple[Response | None, dict]: logger.debug(f"Init attempt - Source: Cookies: {cookies}") async with AsyncClient( proxy=proxy, headers=Headers.GEMINI.value, cookies=cookies, follow_redirects=True, ) as client: try: response = await client.get(Endpoint.INIT.value) response.raise_for_status() logger.debug(f"Init attempt - Status Code: {response.status_code}") This will help confirm both environments are using identical cookie values. — Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACSYSBY7EZWVONNMBXIUJMD2OIB65AVCNFSM6AAAAABTKR5QTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZWG4ZDENBTGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- - THK

[gaoym121]

Are you sure? You should check carefully. The Secure_1PSIDTS changes with every request, so you can't use the same cookie simultaneously on local machine and VPS.

[UnitTHK]

Yes, I am (was) pretty sure. The account is made fresh to be used only for the bot, and I've attempted to paste the cookie straight into the VPS, not even testing it on local to see if using the cookie locally will invalidate it, and it still occurred. That's why I am so perplexed on wtf is going on there. Esp when apparently no one else is experiencing the issue

…

On Wed, Feb 5, 2025 at 7:57 PM luke gao ***@***.***> wrote: Are you sure? You should check carefully. The Secure_1PSIDTS changes with every request, so you can't use the same cookie simultaneously on local machine and VPS. — Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACSYSBZXZCNODHISGD2GAH32OIDD3AVCNFSM6AAAAABTKR5QTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZWG44DONRZG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- - THK

[gaoym121]

Perhaps you can provide detailed information about:

1. How you obtained the cookie value
2. Which browser version you're using
3. Your local operating system
4. Local and server IP addresses, along with IP quality assessment
5. Whether you're using a proxy
6. How you tested the code locally
7. How you tested the code on the server side

The key is in the details (ideally, others should be able to reproduce the issue based on your description). By analyzing all these factors together, we might be able to find clues about what's causing the problem.

[UnitTHK]

1. Cookie value are obtained via the gemini.google.com site, in the F12 menu - Application - Cookies - ... 2. I'm currently using Brave Version 1.74.51 Chromium: 132.0.6834.160 (Official Build) (64-bit) 3. My Local OS is Windows 11, 24H2 4. Local IP: 171.253.240.124 (it's dynamic anyway so I don't mind it being leaked out or smth) Fraud Score 6 Server IP: 46.4.162.xxx (Hetzner Range) Fraud score 27 5. I'm not using a proxy normally 6 and 7: It's a discord bot, so I literally just ran the same program (the bot's program) to do testing on both sides. Works fine on my machine, but on the remote server it fails no matter what. After a fail on the server if I try again on local it still works fine, so the token was definitely valid

…

On Wed, Feb 5, 2025 at 8:10 PM luke gao ***@***.***> wrote: Perhaps you can provide detailed information about: 1. How you obtained the cookie value 2. Which browser version you're using 3. Your local operating system 4. Local and server IP addresses, along with IP quality assessment 5. Whether you're using a proxy 6. How you tested the code locally 7. How you tested the code on the server side The key is in the details (ideally, others should be able to reproduce the issue based on your description). By analyzing all these factors together, we might be able to find clues about what's causing the problem. — Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACSYSB4RPCM5DLARNE2ZAVD2OIEVNAVCNFSM6AAAAABTKR5QTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZWHAYTOMBYG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- - THK

[gaoym121]

1. Cookie value are obtained via the gemini.google.com site, in the F12
   menu - Application - Cookies - ...
2. I'm currently using Brave
   Version 1.74.51 Chromium: 132.0.6834.160 (Official Build) (64-bit)
3. My Local OS is Windows 11, 24H2
4. Local IP: 171.253.240.124 (it's dynamic anyway so I don't mind it being
   leaked out or smth) Fraud Score 6
   Server IP: 46.4.162.xxx (Hetzner Range) Fraud score 27
5. I'm not using a proxy normally
   6 and 7: It's a discord bot, so I literally just ran the same program (the
   bot's program) to do testing on both sides. Works fine on my machine, but
   on the remote server it fails no matter what. After a fail on the server if
   I try again on local it still works fine, so the token was definitely valid
   …

2 Try getting the cookie through Chrome browser and then try again.

[ranjitsingha]

Its working fine for me. I am also using multiple ip and have no problems