Calibre News Recipe Login Failed: How to Fix It

A “calibre news recipe login failed” message usually means calibre reached a protected news source but could not create an authenticated session. The cause may be an incorrect saved username or password, a website login change, expired cookies, two-factor authentication, a blocked network request, or an outdated custom recipe. The safest approach is to test one variable at a time, inspect the job log, and stop as soon as calibre downloads a readable news issue successfully.

1. Confirm the Symptom With a Small Safe Test

Begin by confirming that authentication is the failing stage. A login error is different from a general internet failure, certificate problem, timeout, empty feed, or article-conversion error. Treating every failed news job as a password problem can lead to unnecessary account resets and recipe changes.

1.1 Run the failing recipe manually

Open calibre, select Fetch news, locate the affected source, and start a manual download instead of waiting for its schedule. If calibre displays username and password fields, re-enter the credentials carefully rather than assuming the saved values remain correct.

• Use the username format accepted by the website, which may be an email address.
• Check for accidental spaces before or after the username.
• Confirm that Caps Lock and the keyboard layout are correct.
• If you recently changed the website password, update it in calibre.
• Do not use credentials belonging to a different subscription or regional edition.

Success means the job finishes and adds a new news issue containing accessible articles. If that happens, stop changing settings. The problem was most likely an outdated or incorrectly entered credential.

1.2 Test a news source that does not require login

Next, download a simple public news source or feed that does not require a subscription. This is a useful control test because it checks whether calibre can reach websites, retrieve content, and create an e-book without involving the protected account.

If the public source downloads but the authenticated source fails, the library, conversion engine, and general news-download feature are probably working. Focus on the account, login workflow, cookies, or recipe. If both sources fail, investigate the network, firewall, proxy, certificate, or security software before changing the authenticated recipe.

1.3 Verify the account in a normal browser

Sign out of the publisher’s website in your browser, open a private or incognito window, and sign in again by typing the same credentials. A private window reduces the chance that an old browser session hides an incorrect password.

After signing in, open one of the articles that calibre is expected to download. Reaching an account page is not enough if the subscription does not include the requested content. Success means the protected article opens without another password prompt, subscription notice, consent interruption, or account-verification request.

A successful browser login does not guarantee that the calibre recipe can log in. Modern sites may require JavaScript, CAPTCHA challenges, email verification, device approval, or a multi-step identity service that an older recipe does not understand.

2. Check the Recipe Username, Password, and Authentication Method

Authenticated recipes are designed to request or receive a username and password. The recipe then uses those values in the login procedure defined by its code. If the website changes its form fields, login address, cookies, or redirects, correct credentials can still produce a login failure.

2.1 Re-enter the recipe credentials

Open the affected source from the Fetch news interface and review its account fields. Delete the existing entries and type them again. Avoid copying from formatted documents or password-manager notes that may add spaces or invisible characters.

If your password includes unusual characters, first prove that it works when typed manually into a private browser window. Do not weaken a password merely to accommodate a recipe. If the site offers an official app-specific password and calibre’s recipe supports ordinary username-and-password authentication, that app password may be appropriate. Never assume the main account password and an app password are interchangeable.

Success means a manual fetch proceeds beyond the login step and begins retrieving feeds or articles. Once the job succeeds, do not reset the account password or alter the recipe further.

2.2 Understand two-factor authentication limitations

Two-factor authentication can break a recipe that only knows how to submit a username and password. A website may expect a one-time code, push approval, security key, CAPTCHA, or trusted-device confirmation. calibre cannot automatically complete an interactive challenge unless the particular recipe and website provide a compatible, non-interactive method.

• Check whether the publisher officially supports app passwords.
• Complete any pending account verification in a normal browser.
• Review whether the account requires acceptance of updated terms.
• Do not disable two-factor authentication merely as a routine troubleshooting step.
• Do not copy authentication tokens into recipes obtained from untrusted sources.

If the site has no supported non-interactive login method, the recipe may require maintenance or may no longer be able to access authenticated content. That is a recipe compatibility issue, not proof that calibre itself is broken.

2.3 Recognize cookie and session failures

Many websites set cookies after a successful login and require those cookies on later article requests. A recipe may fail if the cookie name, domain, consent flow, or session behavior changes. It may also appear to log in successfully but receive a sign-in page when it opens an article.

Look in the job log for repeated redirects to login pages, messages about cookies, or downloaded pages whose titles say “Sign in,” “Access denied,” or “Verify your account.” These signs suggest that authentication was not preserved. Avoid manually importing browser cookies unless the recipe’s trusted maintainer provides clear instructions. Browser cookie workarounds can expose account sessions and often stop working when the site changes again.

3. Determine Whether the Website Changed or the Network Failed

A publisher can redesign its website without changing your account. Login URLs, form field names, identity providers, article paths, consent pages, and bot protections can all change. An authenticated recipe that worked yesterday may fail even though the username and password remain valid.

3.1 Distinguish login failure from network failure

A true login failure usually shows that calibre reached the site and received a response, but the recipe could not confirm authentication. A network failure typically contains terms such as timeout, connection refused, name resolution, proxy error, certificate verification, or host unreachable.

• HTTP 401 or 403: The server rejected authentication or access.
• HTTP 404: A recipe URL may no longer exist.
• Repeated 301 or 302 redirects: The site may be sending calibre back to login.
• Timeout or DNS error: Test the network before editing credentials.
• HTML parsing or missing-element error: The website layout may have changed.

If the log shows a network error before any login request completes, stop changing the password. Resolve connectivity first, then rerun the same small test.

3.2 Check VPNs, proxies, firewalls, and antivirus tools

Temporarily test without a VPN or filtering proxy if permitted by your network policy. Some publishers restrict data-center addresses, unusual regions, or rapidly changing IP addresses. Corporate networks, DNS filters, parental controls, and antivirus web shields can also block login domains while allowing the publisher’s main page.

Allow calibre through the operating system firewall and security software rather than disabling protection for an extended period. On Windows, confirm that the relevant calibre applications are permitted on the active network profile. On macOS and Linux, check outbound filtering, proxy environment settings, and security tools that inspect HTTPS traffic.

Success means the identical recipe and credentials work after the connection path is corrected. Stop there. Do not edit recipe code when the network was the actual cause.

3.3 Check the computer clock and certificate errors

An incorrect system date, time, or time zone can interfere with HTTPS certificates and time-sensitive authentication. Enable automatic time synchronization, correct the clock, restart calibre, and test again. If the log reports a certificate problem, do not bypass certificate validation casually. Update the operating system’s trusted certificates and check whether antivirus HTTPS inspection is replacing the site certificate.

4. Use Job Details and Recipe Diagnostics

calibre runs news downloads as jobs. The job details are the most useful evidence because they identify the URL and stage that failed. Reading the log is safer than reinstalling calibre or deleting a library based on a generic error dialog.

4.1 Open the failed job log

Click the Jobs area in calibre after the download fails. Locate the failed news job and open its details, commonly by double-clicking it. Read from the first warning or traceback rather than focusing only on the final “failed” line.

Look for these clues:

• The first URL that returned an error.
• Whether the failure occurred during login, feed retrieval, or article download.
• HTTP status codes and redirect destinations.
• Messages about missing forms, fields, tags, or elements.
• Whether the returned page was a login, consent, CAPTCHA, or access-denied page.

Do not publish a complete log without reviewing it. Logs can contain usernames, URLs, account identifiers, or other private information. Remove sensitive values before sharing an excerpt with a recipe maintainer or support forum.

4.2 Diagnose a built-in recipe

If the failing source uses a built-in recipe, first make sure your calibre installation is supported and up to date through the official calibre release channel. Recipe fixes are often distributed with calibre updates, but an update should not be described as a guaranteed solution. The website may have changed after the recipe was last maintained, or the authentication method may no longer be automatable.

After updating, repeat one manual fetch with freshly entered credentials. Success means the updated recipe can authenticate and download readable articles. If the same login-stage error remains, preserve the job log and look for a known recipe problem or report it with a sanitized error excerpt.

4.3 Maintain a custom recipe carefully

A custom recipe is your responsibility unless another maintainer supplies updates. In Fetch news, open the custom news source and review its advanced recipe code. Make a backup before editing it.

Common breakpoints include an obsolete login URL, renamed form fields, a changed submit button, a new identity-provider redirect, or an article page that now requires a different cookie. A recipe may declare that it needs a subscription and then use its browser object to submit the credentials. If the website no longer presents the expected form, the recipe must be updated to match the supported login flow.

Non-developers should avoid making random code changes. Provide the sanitized job log, the custom recipe file, and a description of what changed to a trusted maintainer. Do not post your username, password, cookies, or subscription tokens.

4.4 Use command-line testing when appropriate

Advanced users can save a custom recipe as a .recipe file and run a limited test with verbose output and conversion debug files:

ebook-convert myrecipe.recipe test.epub --test -vv --debug-pipeline debug

The test option limits the amount of content downloaded, verbose output reveals the processing sequence, and the debug pipeline saves intermediate material. Inspect the downloaded input carefully for a login page, consent page, or access-denied response. Protect or delete debug folders after testing because retrieved pages may contain account-related information.

calibre-debug is useful for broader calibre debugging, but it does not repair a broken website login automatically. Use it only when a maintainer requests debug-mode output or when you are comfortable reviewing technical logs.

5. Run a Clean Temporary Test Before Reinstalling

Reinstalling calibre rarely fixes a recipe whose login process no longer matches the website. Deleting the library is even less appropriate because news authentication is not normally repaired by removing books or metadata. Run an isolated test first.

5.1 Create a temporary library

Create or switch to a temporary empty library and run the same authenticated news recipe manually. Enter the credentials again when requested. This checks whether unusual library automation, duplicate handling, or destination behavior is confusing the result, although most login failures will reproduce in every library.

If the login fails in both libraries with the same log message, the library is not the cause. Return to the normal library and stop changing its metadata or files.

5.2 Test with a clean configuration

For a deeper isolation test, advanced users can launch calibre with a temporary configuration directory by setting CALIBRE_CONFIG_DIRECTORY to an empty folder before starting calibre. This separates the test from existing preferences and third-party plugins. Exact environment-variable steps differ across Windows, macOS, and Linux, so record the original setup and use a disposable directory.

Enter the recipe credentials only for the test and run one manual download. If it works in the clean configuration, compare plugins, proxy settings, and relevant preferences in the normal profile. If it fails identically, the evidence points back to the account, website, recipe, or network.

5.3 Disable only relevant third-party interference

A typical metadata, device, viewer, or editor plugin does not control authenticated news login. Do not disable every plugin without evidence. Concentrate on plugins or external tools that alter networking, news retrieval, proxies, credentials, or generated files.

Likewise, USB mode, connected e-reader limitations, email delivery, Content server settings, conversion layout options, and book metadata do not explain a failure that occurs during website login. Troubleshoot sending or conversion only after the recipe successfully creates the news e-book.

6. Quick Fix Checklist

1. Run the affected recipe manually with a small download.
2. Re-enter the exact username and password used on the publisher’s site.
3. Confirm the account can open a protected article in a private browser window.
4. Check whether two-factor authentication requires an officially supported app password.
5. Download a public recipe to test calibre’s general network and conversion path.
6. Open Jobs and inspect the first meaningful error in the failed job details.
7. Separate HTTP login errors from DNS, timeout, proxy, and certificate failures.
8. Test without an unnecessary VPN or filtering proxy.
9. Update calibre through its official release channel and repeat one test.
10. For custom recipes, back up the code and check for changed login URLs or fields.
11. Use a temporary library or configuration before reinstalling or deleting anything.
12. Stop changing settings as soon as one clean fetch produces readable protected articles.

7. Frequently Asked Questions

7.1 Why does the website login work while the calibre recipe fails?

Your browser can execute JavaScript, display CAPTCHA challenges, request a two-factor code, remember trusted devices, and follow complex identity-provider redirects. A recipe may use a simpler automated browser and expect a specific login form. If the site changed that workflow, the recipe can fail even with valid credentials.

7.2 Does a login failure mean calibre is not working?

Not necessarily. If a public news source downloads correctly and calibre can create the resulting e-book, the core application is working. The problem is more likely limited to the protected account, website access, or recipe authentication logic.

7.3 Should I delete my calibre library or reinstall the application?

No, not as an early step. A library deletion can destroy organization work and normally has no effect on a publisher login. Inspect job details and run a temporary clean test first. Reinstallation is reasonable only when application files appear damaged or calibre cannot perform unrelated tasks.

7.4 Can I fix two-factor authentication by entering the current code as my password?

Usually not. One-time codes expire and recipes generally cannot pause for interactive verification. Use an app-specific password only when the publisher officially offers one and the recipe supports that authentication method. Do not disable account security merely to test a download.

7.5 How do I know whether a custom recipe needs maintenance?

Strong signs include errors about a missing login form or field, a login URL returning 404, repeated redirects, protected articles containing sign-in HTML, or failure beginning immediately after a site redesign. A sanitized job log can help a maintainer identify the exact broken step.

7.6 What does a successful fix look like?

The news job completes without an authentication error, calibre adds a new issue to the library, and protected articles contain their expected text rather than login or subscription pages. When all three conditions are met, stop troubleshooting and avoid making unrelated changes.