How to fix browser-use PostHog SSL CERTIFICATE_VERIFY_FAILED error?
Running browser-use, I keep seeing repeated log errors: ERROR [posthog] error uploading: HTTPSConnectionPool(host='eu.i.posthog.com', port=443) ... SSLError(SSLCertVerificationError ... self signed certificate). This happens when PostHog uploads telemetry data. How do I fix the SSL error or stop these log messages?
Originally asked on GitHub: https://github.com/browser-use/browser-use/issues/282
4 answers
This issue is closed as a duplicate and has no maintainer fix in the thread. The two user-reported workarounds are fixing the proxy configuration or disabling telemetry.
The error comes from PostHog's telemetry upload to eu.i.posthog.com failing SSL certificate verification because a self-signed certificate is in the chain. One user confirmed the same error. Another user said they solved it by checking that their proxy was correctly enabled and the port number was right, then exporting:
export http_proxy=http://127.0.0.1:7890/ export https_proxy=http://127.0.0.1:7890/
In reply to a question about running browser-use alongside mitmproxy (which requires its own certificates), a user suggested disabling telemetry by adding this to your .env file:
ANONYMIZED_TELEMETRY=false
The thread does not confirm that this setting stops the error, only that it was suggested as a way to avoid the telemetry upload. It also does not state whether the error interrupts normal browser-use runs, and it does not explain how to make PostHog trust a mitmproxy or self-signed certificate.
General advice: if you keep telemetry enabled behind a proxy that presents a self-signed certificate, the proxy's certificate needs to be trusted by your Python environment. The thread does not cover those steps.
Did this work for you?What a GitHub user tried on GitHub (Outcome unclear)
The reporter saw the PostHog telemetry upload fail with an SSL certificate verification error (self-signed certificate) when connecting to eu.i.posthog.com and asked if anyone had encountered it.
Source: https://github.com/browser-use/browser-use/issues/282 (opens external site)
Did this work for you?What @duyuwen-duen tried on GitHub (Worked)
A user solved the problem by exporting the proxy environment variables export http_proxy=http://127.0.0.1:7890/ and export https_proxy=http://127.0.0.1:7890/, and checking that the proxy was enabled with the correct port.
Source: https://github.com/browser-use/browser-use/issues/282#issuecomment-2600588633 (opens external site)
Did this work for you?What @Sunraiseevery tried on GitHub (Outcome unclear)
In reply to a question about running with mitmproxy, a user suggested setting ANONYMIZED_TELEMETRY=false in the .env file.
Source: https://github.com/browser-use/browser-use/issues/282#issuecomment-2613790371 (opens external site)
Did this work for you?
Related questions
- How to pause browser-use and ask a human for input mid-run?
- browser-use agent stuck at Step 1 with Chromium on about:blank page
- How do I use OpenRouter with browser-use for DeepSeek when it fails with 429 or 'Could not parse response'?
- browser-use SSLError to eu.i.posthog.com: how do I disable the telemetry call?
- browser-use stuck at 'Step 1' with blank Chromium page, what causes it and how to fix it?