User documentation
  1. What is redirection.io?
  2. Starter's guide
  3. What are organizations and projects?
  4. Invite new collaborators
  5. User account and preferences
  6. Using traffic logs
  7. Create a rule
  8. Triggers and markers reference
  9. Actions reference
  10. How to bulk-import or export redirection rules?
  11. Managing instances
  12. Project notifications
  13. Project segmentation
  14. How much does it cost?
  15. Can I use redirection.io for free?
  16. About us
Developer documentation
  1. TL;DR; Fast track
  2. Available integrations
  3. nginx module
  4. Apache module
  5. platform.sh integration
  6. Cloudflare Workers integration
  7. Fastly Compute@Edge integration
  8. Vercel Middleware Integration
  9. Using redirection.io with Docker
  10. How fast is it?
  11. Public API
Agent documentation
  1. Installing the agent
  2. Upgrading the agent
  3. Agent command line options
  4. The agent as a reverse proxy
  5. Agent configuration reference
  6. Minimal configuration
  7. Listening for requests
  8. Forwarding requests to the backend
  9. Virtualhosts
  10. Trusted proxies
  11. GeoIP database
  12. Response compression
  13. Performance tweaks
  14. Access logs
  15. Persisting data in a s3 bucket
  16. Monitoring the agent
  17. Using the agent behind a HTTPS proxy
  18. Agent configuration examples
Managed instances
  1. What are managed instances?
  2. Add a domain to your project
  3. Managed instances limits and quota
  4. Frequently asked questions
Crawler
  1. What is the redirection.io crawler?
  2. Start a crawl
  3. Schedule a crawl
  4. Analyzing the results of a crawl
  5. The crawls list
  6. Crawl credits and pricing
  7. Crawl Errors
  8. Crawler metrics reference
  9. Crawler columns reference
Knowledge base
  1. Create your first redirections
  2. redirection.io rules cookbook
  3. Setting up a redirection server on Azure Cloud
  4. Structured data and Rich Snippets
  5. What is a URL redirection?
  6. Why use URL redirections and how to setup
Legacy versions
  1. Agent 1.x configuration reference
  2. Agent 2.x configuration reference
  3. Legacy integrations
  4. Legacy Cloudflare Workers integration
Changelogs
  1. redirectionio-agent
  2. libnginx-mod-redirectionio
  3. libapache2-mod-redirectionio

Upgrading the agent

You are strongly encouraged to keep your redirection.io install up-to-date. We regularly push new versions of the agent, which include new features, improvements and fixes. Using the latest version of the agent is always a good idea.

The update can always be run safely, as we do not introduce breaking changes in minor versions of the agent or proxy modules. When breaking changes are required, they are added in a new major version, that can only be used after changing the packages repository URL.

  • for the legacy version 2.x, use the repository URLs https://packages.redirection.io/deb/stable/2 or https://packages.redirection.io/rpm/stable/2
  • for the current version 3.x, use the repository URLs https://packages.redirection.io/deb/stable/3 or https://packages.redirection.io/rpm/stable/3

Upgrading to a new major version of the agent and proxy

Upgrading from a legacy major version to the current version of the agent and the proxy requires to change the APT or RPM packages repositories.

If you use the nginx or Apache module, please note that the server module must be upgraded to a new major version synchronously with the agent: when upgrading to the agent 3.x, you must also upgrade the nginx or Apache module to the 3.x branch.

Debian and APT-based distributions

  1. Locate the apt redirection.io configuration files - the should live somewhere under /etc/apt/sources.list.d - usually in /etc/apt/sources.list.d/packages_redirection_io_deb.list

  2. change the repository URL. For example, for the current version (3.x) of the agent or the proxies, use:

    deb https://packages.redirection.io/deb/stable/3 any main
deb https://packages.redirection.io/deb/stable/3 bullseye main

    Of course, please choose the right distribution name.

  3. Run the other usual upgrade steps, as described below.

  4. Once the packages have been updated, please make sur to restart both the agent and the web server module services. For example:

    sudo systemctl restart redirectionio-agent
sudo systemctl restart nginx

Red Hat and RPM-based distributions

  1. Locate the rpm redirection.io configuration files - the should live somewhere under /etc/yum.repos.d/

  2. change the repository URL. For example, for the current version (3.x) of the agent or the proxies, use:

    baseurl=https://packages.redirection.io/rpm/any/stable/3

deb https://packages.redirection.io/rpm/stable/3 any main
deb https://packages.redirection.io/rpm/stable/3/centos_8 main

    Of course, use your distribution name in the repository URL.

APT-based distributions

  1. Update the apt cache

    sudo apt update

  2. Update only the agent:

    sudo apt install --only-upgrade redirectionio-agent

  3. Restart the agent service. Depending on your service manager, it can be one of:

    sudo systemctl restart redirectionio-agent
sudo service redirectionio-agent restart
sudo /etc/init.d/redirectionio-agent restart

RPM-based distributions

  1. Update the agent:

    sudo yum update redirectionio-agent

  2. Restart the agent service. Depending on your service manager, it can be one of:

    sudo systemctl restart redirectionio-agent
sudo service redirectionio-agent restart
sudo /etc/init.d/redirectionio-agent restart

Binary / manual upgrade

Upgrading the manual way is the same as the manual installation. However, we strongly advise, if possible, to use a package manager to streamline the upgrade process.

This page has been updated on Mar 30, 2026
Can't find your answer?