notebooklm-py-cookies-rejected-by-upstream-client-fingerprint
Migrating cookies from notebooklm-py’s storage_state.json to upstream notebooklm-mcp-cli profile format succeeds at the file level, but Google rejects the session when the upstream client attempts CSRF token refresh. The upstream uses different HTTP headers and user-agent fingerprint than notebooklm-py, causing Google to invalidate the session. Fresh auth via nlm login (interactive browser CDP) or save_auth_tokens MCP tool is required — cookie migration alone is insufficient.
Related
- notebooklm-mcp-cli-auth-two-file-format
- notebooklm-mcp-cli-auth-format-two-files
- notebooklm-cookie-refresh-cron-must-update-on-migration
- docker
- notebooklm-cookie-auth-keepalive
- notebooklm-mcp-cli-auth-two-file-profile-format
- notebooklm-mcp-container-requires-1gb-memory-not-512mb
- nlm-login-only-valid-auth-path-for-notebooklm-upstream
- notebooklm-mcp-cli-auth-requires-fresh-capture-not-migration
- notebooklm-mcp-container-needs-1g-memory
- notebooklm-upstream-auth-fingerprint-rejection
- notebooklm-upstream-auth-google-fingerprint-rejection
- notebooklm-upstream-auth-two-file-format
- notebooklm-upstream-auth-requires-fresh-cookies-not-migrated
- notebooklm-legacy-cookie-refresh-cron-obsolete-after-upgrade
- notebooklm-mcp-cli-rejects-migrated-notebooklm-py-cookies
- google-auth-cookies-httponly-use-network-tab-for-extraction
- notebooklm-legacy-cookies-rejected-by-upstream-client
- notebooklm-upstream-auth-http-fingerprint-rejects-migrated-c