win或者linux下的版本无法登录x.com

[iptag]

使用sign in登录，每次在这个界面就会提示Could not log you in now. Please try again later. g;xxxx:-xxxx:xxxx:1

[iptag]

https://browserleaks.com/ip中的TCP/IP Fingerprint项，正常的chrome是如下参数

OS	Windows
MTU	1492
Link Type	PPPoE
Distance	17 Hops
JA4T	64240_2-1-3-1-1-4_1452_8

但是大佬的指纹浏览器，不管怎么随机种子，好像都是下面的参数，被识别为了安卓设备

OS	Android
MTU	1400
Link Type	Probably IPsec or other VPN
Distance	7 Hops
JA4T	65280_2-4-8-1-3_1360_7

[skka3134]

我是mac目前可以登录

[skka3134]

win和linux没测试

[funky-mango]

I've seen this happen when using a VPS. Same code, same proxy, same everything on a local (windows) machine works fine. So not sure it is purely a TLS Fingerprint issue, but I think it is playing a part along with some other detections

---

我在使用VPS时遇到过这种情况。同样的程序代码、同样的代理，所有配置在本地（Windows）机器上都运行正常。所以我不确定这是否完全是TLS指纹的问题，但我认为它可能与其他一些检测机制共同作用导致了这个问题。

[funky-mango]

https://browserleaks.com/ip中的TCP/IP Fingerprint项，正常的chrome是如下参数

但是大佬的指纹浏览器，不管怎么随机种子，好像都是下面的参数，被识别为了安卓设备

OS	Android
MTU	1400
Link Type	Probably IPsec or other VPN
Distance	7 Hops
JA4T	65280_2-4-8-1-3_1360_7

This is the IP, not the browser. Using cloudflare warp VPN I get:

TCP/IP Fingerprint
OS	Android
MTU	1420
Link Type	generic tunnel or VPN
Distance	10 Hops
JA4T	65535_2-4-8-1-3_1380_13

but using default IP

CP/IP Fingerprint
OS	Windows
MTU	1452
Link Type	PPPoE
Distance	16 Hops
JA4T	65535_2-1-3-1-1-4_1412_8

It's not the browser that is being reported. But regardless, I can log into twitter using the VPN or base IP. Run on a VPS server (With / without VPN with local IP / proxy and I Get your issue)

[funky-mango]

使用sign in登录，每次在这个界面就会提示`Could not log you in now. Please try again later. g;xxxx:-xxxx:xxxx:1

Disable GPU in browser. Fixed the issue for me

--disable-webgl
--disable-accelerated-2d-canvas
--disable-software-rasterizer
--disable-webgl2

Don't know which of those worked, but I no longer get the issue. Seems there is a giveaway you are a VPS,

This javascript

            const gl = canvas.getContext("webgl") || canvas.getContext("experimental-webgl");
            if (!gl) return "WebGL Context Creation Failed (No GPU/Driver)";
            
            const debugInfo = gl.getExtension('WEBGL_debug_renderer_info');
            return {
                "Vendor": debugInfo ? gl.getParameter(debugInfo.UNMASKED_VENDOR_WEBGL) : 'Unknown',
                "Renderer": debugInfo ? gl.getParameter(debugInfo.UNMASKED_RENDERER_WEBGL) : 'Unknown',
                "Version": gl.getParameter(gl.VERSION)
            };

Will error in the fingerprint-chromium browser.

Chrome will show:

 WebGL & Hardware Information

{

"Vendor": "Google Inc. (Microsoft)",

"Renderer": "ANGLE (Microsoft, Microsoft Basic Render Driver (0x0000008C) Direct3D11 vs_5_0 ps_5_0, D3D11)",

"Version": "WebGL 1.0 (OpenGL ES 2.0 Chromium)"

} 

something that chrome does chromium does not is provide the Microsoft basic render driver (VPS giveaway). As with chromium, the lack of this function returning antyhing is also a giveaway you are in a virtualised environemtn

  const gl = canvas.getContext("webgl") || canvas.getContext("experimental-webgl");
            if (!gl) return "WebGL Context Creation Failed (No GPU/Driver)";

whether this is something the project can spoof I have no idea. Way above my ability. But for now, adding the above flags to not allow webgl seems to work.

Be interested to know if it works for you