notebooklm-upstream-auth-google-fingerprint-rejection
Valid, non-expired cookies migrated from notebooklm-py’s storage_state.json are rejected by Google when used with notebooklm-mcp-cli upstream. The upstream uses a different HTTP client fingerprint (different headers/user-agent) than notebooklm-py, causing Google’s CSRF refresh step to fail at the RPC level even when cookies parse and load correctly. Fresh cookies MUST be captured from a live desktop Chrome session via CDP or manual extraction — cookie migration from notebooklm-py to upstream is not viable for auth.
Related
- notebooklm-py-cookies-rejected-by-upstream-client-fingerprin
- notebooklm-mcp-cli-auth-requires-fresh-capture-not-migration
- notebooklm-upstream-auth-fingerprint-rejection
- notebooklm-mcp-cli-auth-two-file-format
- notebooklm-mcp-cli-auth-format-two-files
- notebooklm-upstream-auth-requires-fresh-cookies-not-migrated
- notebooklm-mcp-cli-rejects-migrated-notebooklm-py-cookies
- notebooklm-legacy-cookies-rejected-by-upstream-client
- notebooklm-migrated-cookies-rejected-different-http-fingerpr
- notebooklm-py-cookies-rejected-by-upstream-client
- google-auth-cookies-are-httponly-document-cookie-fails
- google-session-cookies-require-periodic-refresh-cron
- notebooklm-auth-fingerprint-mismatch
- notebooklm-upstream-auth-http-fingerprint-rejects-migrated-c