“The link you followed has expired.” message appears while installing the plugin

FAQ & Troubleshooting · 3 min read · Updated May 21, 2026

you tried to install (or update) a WordPress plugin or theme and got the message “The link you followed has expired.” The frustrating part: there’s no actual link, no expiration, no helpful context. This message is WordPress’s catch-all for a request that hit a server limit. The fix is to raise the limit.

Why it happens

When you upload a plugin ZIP, the server has to:

  1. Receive the entire upload (bound by upload_max_filesize, post_max_size).
  2. Allocate enough memory to unzip and process it (memory_limit).
  3. Finish before the script timeout kicks in (max_execution_time, max_input_time).

If any of those limits is too low for the size of the plugin you’re uploading, WordPress aborts and shows the generic “link expired” message. It’s misleading — there’s no actual broken link — but that’s the wording WordPress uses.

The fix: raise six PHP values

Get these to at least the levels below. Most hosts default lower:

SettingSuggested valueWhat it controls
memory_limit256MHow much RAM PHP can use per request
upload_max_filesize64MMax individual file size for uploads
post_max_size64MMax total POST body size (must ≥ upload_max_filesize)
max_execution_time300How long a PHP script can run, in seconds
max_input_time300How long PHP can spend parsing input data

Where to set them

Depends on your host. In order of cleanliness:

  1. Hosting control panel. Most managed hosts (Kinsta, SiteGround, WP Engine, Cloudways) have a “PHP settings” page with sliders for these values. Easiest path.
  2. php.ini. If you have shell access, edit php.ini directly. The settings appear under their literal names.
  3. .htaccess (Apache). Add php_value upload_max_filesize 64M etc. Some hosts block this.
  4. wp-config.php (last resort). Use @ini_set( 'memory_limit', '256M' ); — only some settings can be raised this way.

If you can’t change the limits

Use the FTP/SFTP install method instead. Download the plugin ZIP, unzip locally, upload the unzipped folder to /wp-content/plugins/, then activate it from WordPress admin. This skips the upload mechanism entirely and works regardless of upload limits. See can’t upload .zip file for the full FTP workflow.

Not Tickera-specific

This message appears for any plugin upload that hits server limits — Tickera, any add-on, any WordPress plugin. The fix is the same regardless of which plugin triggered it. If you’re hitting it with Tickera specifically, you’ll likely hit it with other large plugins too — raise the limits once and you’re set.

Related

Was this article helpful?

Yes — great. No or partially? Tell us what was missing — we read every message and use it to improve these docs.