The QR image on the MFA enrollment page is generated and served by the instance, so a blank/broken image is nearly always the image request being blocked, not your authenticator app. Things that fix it in practice: 1) Use the "Or type in" / "Try another way to setup" link right under the QR - it exposes the TOTP secret key. In your authenticator choose "Enter a setup key" manually, account = your instance/user, key = that string, type = Time-based. This completes enrollment without the QR and is the fastest unblock. 2) If no secret shows either, the request is being blocked upstream: corporate proxy/AV, an ad blocker, or a CSP/content-filter stripping the inline data: image. Test on a phone hotspot or a non-corporate network; incognito alone does not disable proxies or all extensions. 3) On the instance side, check that the MFA plugin properties are sane: sys_properties glide.authenticate.multifactor (true) and glide.authenticate.multifactor.issuer / instance name - a blank or invalid issuer string can break generation of the otpauth URL and yield an empty image. 4) Clear any half-finished enrollment: as admin, delete the user's record in the Multi-factor Authentication / user MFA device table (sys_user_mfa_device or "Enable multifactor authentication" flag on sys_user), then have the user re-enroll to get a fresh QR/secret. 5) For a developer instance (developer.servicenow.com), the enrollment is on the Now account side - resetting MFA from your developer profile or via Support is the path; do not repeatedly retry, the code caches. If the type-in key works, the QR failure is purely a browser/network image issue and can be ignored.
