❌

Reading view

There are new articles available, click to refresh the page.

Why Your Printer Isn’t Recognising Your New Ink Cartridge

✇Galido IT
By: galidon

Few things are more frustrating than installing a fresh ink cartridge only for your printer to flash a “cartridge not recognised” or “ink error” message. You’ve spent the money, followed the instructions, and expected to get back to printing, yet your printer refuses to cooperate.

This issue is incredibly common across brands like HP, Canon, Brother and Epson, and it usually comes down to a handful of simple causes. The good news? Most of them can be fixed quickly at home.

Below, we break down the most likely reasons your printer isn’t recognising your new ink cartridge and what you can do to get things running again.

1. The Cartridge Isn’t Installed Properly

It sounds basic, but even a small misalignment can cause the printer to reject a cartridge.

What to check:

  • Make sure all protective tapes, seals or plastic strips are removed (especially the tape covering the ink port or chip).

  • Push the cartridge firmly into the slot until you hear a click.

  • Double-check that it’s in the correct colour position.

Sometimes the installation feels secure, even when the cartridge isn’t fully seated. Removing and reinstalling it usually solves the problem.

2. You’re Using a Non-Genuine or Compatible Cartridge

Many consumers choose compatible cartridges to save money, no issue there, but printers can be picky.

Brands like Epson, HP and Canon often release firmware  updates that block third-party chips. If your printer updated itself automatically, that may be the culprit.

What you can do:

  • Disable automatic firmware updates.

  • Reinstall the previous firmware if your printer allows rollback.

  • Make sure you’re buying reputable compatible cartridges rather than low-quality cheap ones.

Quality third-party cartridges normally work fine; it’s the ultra-cheap, poorly chipped ones that cause endless error messages.

3. The Cartridge Chip Is Dirty or Not Making Contact

Ink cartridges use electronic chips to communicate with the printer. If that chip is dirty, damaged, or simply not aligned properly, the printer will reject it.

Try this fix:

  1. Remove the ink cartridge.

  2. Gently wipe the chip with a soft, dry cloth.

  3. Reinstall the ink cartridge and restart the printer.

Sometimes a tiny amount of dust or residue is enough to interrupt the connection.

4. Mixing Old and New Cartridges

Some printers rely heavily on reading the full set of cartridges together. If one is empty, incompatible, or partly blocked, it can cause the new cartridge to fail detection.

Also, if the printer memory still thinks the “old” cartridge is installed, it may continue showing the error.

Try this:

  • Remove all cartridges.

  • Turn the printer off and unplug it for a few minutes.

  • Reinstall the full set.

This forces the printer to rescan and recognise the cartridges.

5. The Cartridge Is Incorrect for Your Printer

Printer model names can be confusingly similar. For example, Canon and Brother often have different models within the same series, but the cartridges aren’t interchangeable.

If your printer doesn’t accept the new cartridge at all, take another look at the model code. An extra letter or number can make all the difference.

Tip: The model listed on the box must match your printer exactly. Close isn’t good enough.

6. Firmware Updates Blocking the Cartridge

This is a growing issue. Manufacturers routinely release firmware patches that quietly block older or third-party cartridges.

If your printer suddenly stopped recognising cartridges that previously worked fine, this is a strong clue.

What you can do:

  • Turn off automatic updates.

  • Install a compatible firmware version if your brand supports downgrading.

7. The Cartridge Itself Is Faulty

Even genuine cartridges occasionally ship with defective chips or damaged contacts. It’s rare, but it happens.

Signs your cartridge may be faulty:

  • The error appear even after cleaning the chip.

  • Other cartridges work fine.

  • You’ve tried reinstalling multiple times with no luck.

If you purchased from a reputable supplier, you can request a replacement. 

8. The Printer Needs a Hard Reset

Many modern printers “remember” ink cartridge data, which can cause issues when you replace the cartridge with the same model.

A hard reset clears that cached memory.

How to do it (most models):

  1. Remove all ink cartridges.

  2. Turn off the printer.

  3. Unplug the power cable.

  4. Wait 10–20 minutes.

  5. Plug the printer back in and restart.

  6. Install the cartridges again.

This forces the printer to recognise them as new units.

When to Seek Further Help

If you’ve tried all the above and the printer still refuses to recognise the cartridge, consider:

  • Testing with another cartridge (even an old one) to confirm it’s not a chip issue.

  • Checking the printer warranty, print head or board faults can cause similar errors.

  • Contacting the supplier for troubleshooting or replacement.

Final Thoughts

A “cartridge not recognised” message doesn’t necessarily mean your cartridge is broken. Most of the time, the issue is something small, chip contact, protective tape, a firmware update, or simply a reset that’s overdue.

With the right steps, you can usually fix it in minutes and get back to printing without wasting money or time.

The post Why Your Printer Isn’t Recognising Your New Ink Cartridge first appeared on Information Technology Blog.

REST-Attacker - Designed As A Proof-Of-Concept For The Feasibility Of Testing Generic Real-World REST Implementations

✇KitPloit
By: Unknown


REST-Attacker is an automated penetration testing framework for APIs following the REST architecture style. The tool's focus is on streamlining the analysis of generic REST API implementations by completely automating the testing process - including test generation, access control handling, and report generation - with minimal configuration effort. Additionally, REST-Attacker is designed to be flexible and extensible with support for both large-scale testing and fine-grained analysis.

REST-Attacker is maintained by the Chair of Network & Data Security of the Ruhr University of Bochum.


Features

REST-Attacker currently provides these features:

  • Automated generation of tests
    • Utilize an OpenAPI description to automatically generate test runs
    • 32 integrated security tests based on OWASP and other scientific contributions
    • Built-in creation of security reports
  • Streamlined API communication
    • Custom request interface for the REST security use case (based on the Python3 requests module)
    • Communicate with any generic REST API
  • Handling of access control
    • Background authentication/authorization with API
    • Support for the most popular access control mechanisms: OAuth2, HTTP Basic Auth, API keys and more
  • Easy to use & extend
    • Usable as standalone (CLI) tool or as a module
    • Adapt test runs to specific APIs with extensive configuration options
    • Create custom test cases or access control schemes with the tool's interfaces

Install

Get the tool by downloading or cloning the repository:

git clone https://github.com/RUB-NDS/REST-Attacker.git

You need Python >3.10 for running the tool.

You also need to install the following packages with pip:

python3 -m pip install -r requirements.txt

Quickstart

Here you can find a quick rundown of the most common and useful commands. You can find more information on each command and other about available configuration options in our usage guides.

Get the list of supported test cases:

python3 -m rest_attacker --list

Basic test run (with load-time test case generation):

python3 -m rest_attacker <cfg-dir-or-openapi-file> --generate

Full test run (with load-time and runtime test case generation + rate limit handling):

python3 -m rest_attacker <cfg-dir-or-openapi-file> --generate --propose --handle-limits

Test run with only selected test cases (only generates test cases for test cases scopes.TestTokenRequestScopeOmit and resources.FindSecurityParameters):

python3 -m rest_attacker <cfg-dir-or-openapi-file> --generate --test-cases scopes.TestTokenRequestScopeOmit resources.FindSecurityParameters

Rerun a test run from a report:

python3 -m rest_attacker <cfg-dir-or-openapi-file> --run /path/to/report.json

Documentation

Usage guides and configuration format documentation can be found in the documentation subfolders.

Troubleshooting

For fixes/mitigations for known problems with the tool, see the troubleshooting docs or the Issues section.

Contributing

Contributions of all kinds are appreciated! If you found a bug or want to make a suggestion or feature request, feel free to create a new issue in the issue tracker. You can also submit fixes or code ammendments via a pull request.

Unfortunately, we can be very busy sometimes, so it may take a while before we respond to comments in this repository.

License

This project is licensed under GNU LGPLv3 or later (LGPL3+). See COPYING for the full license text and CONTRIBUTORS.md for the list of authors.



REST-Attacker - Designed As A Proof-Of-Concept For The Feasibility Of Testing Generic Real-World REST Implementations

✇KitPloit
By: Unknown


REST-Attacker is an automated penetration testing framework for APIs following the REST architecture style. The tool's focus is on streamlining the analysis of generic REST API implementations by completely automating the testing process - including test generation, access control handling, and report generation - with minimal configuration effort. Additionally, REST-Attacker is designed to be flexible and extensible with support for both large-scale testing and fine-grained analysis.

REST-Attacker is maintained by the Chair of Network & Data Security of the Ruhr University of Bochum.


Features

REST-Attacker currently provides these features:

  • Automated generation of tests
    • Utilize an OpenAPI description to automatically generate test runs
    • 32 integrated security tests based on OWASP and other scientific contributions
    • Built-in creation of security reports
  • Streamlined API communication
    • Custom request interface for the REST security use case (based on the Python3 requests module)
    • Communicate with any generic REST API
  • Handling of access control
    • Background authentication/authorization with API
    • Support for the most popular access control mechanisms: OAuth2, HTTP Basic Auth, API keys and more
  • Easy to use & extend
    • Usable as standalone (CLI) tool or as a module
    • Adapt test runs to specific APIs with extensive configuration options
    • Create custom test cases or access control schemes with the tool's interfaces

Install

Get the tool by downloading or cloning the repository:

git clone https://github.com/RUB-NDS/REST-Attacker.git

You need Python >3.10 for running the tool.

You also need to install the following packages with pip:

python3 -m pip install -r requirements.txt

Quickstart

Here you can find a quick rundown of the most common and useful commands. You can find more information on each command and other about available configuration options in our usage guides.

Get the list of supported test cases:

python3 -m rest_attacker --list

Basic test run (with load-time test case generation):

python3 -m rest_attacker <cfg-dir-or-openapi-file> --generate

Full test run (with load-time and runtime test case generation + rate limit handling):

python3 -m rest_attacker <cfg-dir-or-openapi-file> --generate --propose --handle-limits

Test run with only selected test cases (only generates test cases for test cases scopes.TestTokenRequestScopeOmit and resources.FindSecurityParameters):

python3 -m rest_attacker <cfg-dir-or-openapi-file> --generate --test-cases scopes.TestTokenRequestScopeOmit resources.FindSecurityParameters

Rerun a test run from a report:

python3 -m rest_attacker <cfg-dir-or-openapi-file> --run /path/to/report.json

Documentation

Usage guides and configuration format documentation can be found in the documentation subfolders.

Troubleshooting

For fixes/mitigations for known problems with the tool, see the troubleshooting docs or the Issues section.

Contributing

Contributions of all kinds are appreciated! If you found a bug or want to make a suggestion or feature request, feel free to create a new issue in the issue tracker. You can also submit fixes or code ammendments via a pull request.

Unfortunately, we can be very busy sometimes, so it may take a while before we respond to comments in this repository.

License

This project is licensed under GNU LGPLv3 or later (LGPL3+). See COPYING for the full license text and CONTRIBUTORS.md for the list of authors.



❌