You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: The verbiage expressed here are that of the author and are not representative of State Farm.
Describe the bug
Multiple scripts on the State Farm website are failing due to various connection and timeout errors, impacting user experience and potentially critical functionality. The issues appear to be related to network communication, third-party script loading, and potentially the security infrastructure of the website. Additionally, the module boto3 cannot be found:
Traceback (most recent call last):
File "/home/qenmity/AndroidStudioProjects/apacheredcache/libcloud/CLAWS/claws.py", line 7, in<module>
import boto3
ModuleNotFoundError: No module named 'boto3'
1754845739061 Error Proxy Timeout in communication with remote server - log entry timeout with remote server
9396: function(t, n, e) and t.exports = function(t, n) - webpack bundle legacyFingerprintParts.js mishandling custom error DOM. System log report suggests connection failure.
try { let c = await fetch("https://online.statefarm.com/ddc/trafficdetection.aspx"); ... } catch {}:
JavaScript fetching data from URL determining external or internal connection. Based on the HTTP status the connectivity could be failing to log the error.
Response header X-Amz-Apigw-Id PGUnGGZIoAMF_0Q=: - AMZN API Gateway infrastructure that is hosting on the AWS CDN. Suggesting that the tracking is relevant to the failed request.
Akami-Request-BC [a=23.221.213.204,b=1316502726,c=g,n=US_FL_MIAMI,o=20940]: - Numerous byte header requests from AKAM CDN that is providing details to the request path. Showing that the server passed in Miami routing all the way to Royal Palm Beach. Suggesting a data point of failure.
static1.st8fm.com:443: - Remote Host terminated the handshake. This critical error log indicated that the TLS could not be established due to a server misconfig or firewall.
In JavaScript network error logs. Resolve the false promise when the script fails to load unsuccessfully...
Dynamically loading scripts can mishandle the success rate for using a Promise. Relating this to how the site is loading the external resources. As seen in the network logs.
Source map for webpack URL debugging resources indicates that refactoring the fingerprint system is for 'fraud detection'. The error logged here in this network is related to how the fingerprint process can be misused and fail.
Third-party Optimizely "digital experience" initialized this JavaScript DOM query and pushed the data for the user including "city, country, and IP" for "A/B" testing and "personalization". Which successfully collected user data on the client side.
ak_bmsc=...:
Upon this successful data collection set by the AKAM AI. The user's cookie was extracted ak_bmsc and detected bot traffic. (Blue Team Security Infrastructure) Which is related to "Auth Failure" logs and network requests as flagged.
To Reproduce
Steps to reproduce the behavior:
Go to google.com
Click on statefarm.com
Scroll down to "Privacy Policy"
See error "Access Denied"
Expected behavior
Access Granted.
Screenshots
Desktop (please complete the following information):
OS: Linux cs-542741498729-default 6.6.97+ Add support for Lambda code versions. #1 SMP PREEMPT_DYNAMIC Sun Jul 27 08:59:14 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Browser garcon_host_browser.desktop
Version xdg-settings 1.1.3
Smartphone (please complete the following information):
Note: The verbiage expressed here are that of the author and are not representative of State Farm.
Describe the bug
Multiple scripts on the State Farm website are failing due to various connection and timeout errors, impacting user experience and potentially critical functionality. The issues appear to be related to network communication, third-party script loading, and potentially the security infrastructure of the website. Additionally, the module
boto3cannot be found:1754845739061 Error Proxy Timeout in communication with remote server- log entry timeout with remote server9396: function(t, n, e) and t.exports = function(t, n)- webpack bundlelegacyFingerprintParts.jsmishandling custom error DOM. System log report suggests connection failure.try { let c = await fetch("https://online.statefarm.com/ddc/trafficdetection.aspx"); ... } catch {}:JavaScript fetching data from URL determining
external or internal connection. Based on the HTTP status the connectivity could be failing to log the error.Response header X-Amz-Apigw-Id PGUnGGZIoAMF_0Q=:- AMZN API Gateway infrastructure that is hosting on the AWS CDN. Suggesting that the tracking is relevant to the failed request.Akami-Request-BC [a=23.221.213.204,b=1316502726,c=g,n=US_FL_MIAMI,o=20940]:- Numerous byte header requests from AKAM CDN that is providing details to the request path. Showing that the server passed in Miami routing all the way to Royal Palm Beach. Suggesting a data point of failure.static1.st8fm.com:443:- Remote Host terminated the handshake. This critical error log indicated that the TLS could not be established due to a server misconfig or firewall.#9 #11
CLI Script Config ⚙️
In JavaScript network error logs.
Resolve the false promise when the script fails to load unsuccessfully...Dynamically loading scripts can mishandle the success rate for using a Promise. Relating this to how the site is loading the external resources. As seen in the network logs.
webpack://idpersist-refactor/legacyFingerprintParts.js:Source map for webpack URL debugging resources indicates that refactoring the fingerprint system is for 'fraud detection'. The error logged here in this network is related to how the fingerprint process can be misused and fail.
(function(){ window['optimizely'] = window['optimizely'] || []; ... }):Third-party Optimizely "digital experience" initialized this JavaScript DOM query and pushed the data for the user including "city, country, and IP" for "A/B" testing and "personalization". Which successfully collected user data on the client side.
ak_bmsc=...:Upon this successful data collection set by the AKAM AI. The user's cookie was extracted
ak_bmscand detected bot traffic. (Blue Team Security Infrastructure) Which is related to "Auth Failure" logs and network requests as flagged.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Access Granted.
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
a23-221-212-68.deploy.static.akamaitechnologies.coma.root-servers.net. nstld.verisign-grs.com. 2025081001 1800 900 604800 86400