WordPress: “The Link You Followed Has Expired” — How to Fix It

If you’ve seen the message “The link you followed has expired” in your WordPress dashboard, you’re not alone. It’s one of the more common WordPress errors — and one of the more cryptic, given that it usually appears when you’re trying to upload a file or install a plugin, not click an actual link.

The good news: it’s almost always fixable in a few minutes. This guide explains what causes the error and walks through the most reliable fixes.

What Does “The Link You Followed Has Expired” Actually Mean?

Despite the wording, this error usually has nothing to do with a link expiring. It’s WordPress telling you that a file upload — or another admin action — failed because one of the following limits was exceeded:

• The maximum file upload size allowed by PHP
• The maximum POST size allowed by your server
• The maximum execution time for a PHP script
• The memory limit available to WordPress

WordPress uses nonces (security tokens) to validate admin actions. When an upload takes too long or exceeds a server limit, the nonce expires before the action completes — and WordPress displays this error rather than a more specific technical message.

It can also be triggered by plugin conflicts or an outdated WordPress installation, but server and PHP limits are the cause in the vast majority of cases.

How to Fix “The Link You Followed Has Expired” in WordPress

Fix 1: Increase File Upload and Execution Limits via .htaccess

The quickest fix for most users is to increase the relevant PHP limits via your site’s .htaccess file. You’ll find this file in the root directory of your WordPress installation (the same folder as wp-config.php).

Add the following lines to your .htaccess file:

php_value upload_max_filesize 64M
php_value post_max_size 64M
php_value max_execution_time 300
php_value max_input_time 300

Save the file and try your upload again. Adjust the values if needed — 64M is sufficient for most situations, but if you’re uploading very large files or video, you may need to go higher.

If your hosting environment doesn’t support PHP directives in .htaccess (some do not, particularly Nginx-based servers), move on to Fix 2.

Fix 2: Modify php.ini Directly

If you have access to your server’s php.ini file, you can increase the limits there. Look for these directives and update them:

upload_max_filesize = 64M
post_max_size = 64M
max_execution_time = 300
max_input_time = 300
memory_limit = 256M

If you can’t find an existing php.ini file, you can create one in your WordPress root directory with the values above. On shared hosting, this is often the most reliable method.

After saving, restart your server or contact your hosting provider if you’re unsure how to apply the changes.

Fix 3: Add Limits to wp-config.php

WordPress also allows you to increase the memory limit directly in wp-config.php. Open the file and add this line before the /* That's all, stop editing! */ comment:

define('WP_MEMORY_LIMIT', '256M');

This won’t fix upload size limits on its own, but it can help if memory exhaustion is contributing to the error — particularly on sites with many active plugins.

Fix 4: Use a Plugin

If you’d prefer not to edit server files, plugins like WP Tools and WP Memory Limit can increase upload limits and memory allocation from within the WordPress dashboard.

Install and activate your chosen plugin, configure the upload size and execution time settings, then retry the upload. These plugins are a good option for users on managed hosting where direct server file access is restricted.

Fix 5: Check for Plugin Conflicts

If increasing limits doesn’t resolve the error, a plugin conflict may be the cause. The quickest way to test this is to deactivate all plugins except the one you’re actively using, then attempt the upload again.

If the error disappears, reactivate plugins one at a time until the problem returns — that’s your culprit. Update or replace the conflicting plugin.

Fix 6: Update WordPress

Outdated WordPress installations can introduce compatibility issues that trigger this and other errors. Check your dashboard for available updates and apply them. Before updating, ensure you have a current backup — something a WordPress maintenance plan would typically handle automatically.

Best Practices to Prevent This Error in Future

Once you’ve fixed the error, a few habits will help prevent it from recurring:

• Optimise images before uploading. Large, uncompressed images are the most common trigger. Use a tool like TinyPNG or a WordPress plugin like Smush to reduce file sizes before they hit your server. For detailed guidance on this, see our article on responsive images in WordPress.
• Keep WordPress, themes, and plugins updated. Outdated software introduces compatibility issues. Regular updates are one of the most effective forms of WordPress maintenance.
• Choose a reliable hosting provider. Budget shared hosting often enforces very conservative PHP limits that make this error more likely. If you’re regularly hitting upload limits, it may be worth reviewing your hosting setup.
• Use a CDN for large media files. Offloading video and large assets to a Content Delivery Network reduces the load on your server and bypasses file upload limits for those assets entirely.
• Monitor plugin compatibility. Before installing new plugins, check their reviews and compatibility with your WordPress version. Remove plugins you’re not actively using — they add overhead and potential conflict points.

If this error is recurring or part of a pattern of WordPress issues, it may be worth looking at your site’s overall maintenance setup — particularly if you’re managing the site without any ongoing technical support.

Still Having Problems?

If none of the fixes above resolve the error, the issue may be specific to your server configuration or hosting environment. In that case, contact your hosting provider’s support team directly — they can check your server logs and adjust PHP settings at the server level.

Alternatively, if you’d like a WordPress developer to take a look, get in touch — this is a quick fix in most cases.

You might also find these useful:

• WordPress: Fix Fatal Error Maximum Execution Time Exceeded
• WordPress “File Type Not Permitted” Error Fix
• How to Fix the 500 Internal Server Error in WordPress
• WordPress Maintenance Plans: What’s Included?

FAQs

What causes “The Link You Followed Has Expired” error in WordPress?

The error is almost always caused by a file upload exceeding your server’s PHP limits — specifically the maximum upload file size, POST size, or execution time. WordPress’s security nonce expires before the upload completes, triggering this message. Plugin conflicts and outdated WordPress versions can also be contributing factors.

Is “The Link You Followed Has Expired” a security error?

No. Despite the wording, it’s not a sign of a security breach. It refers to an expired nonce — a one-time security token WordPress uses to validate admin actions. The nonce expires when an upload takes longer than the server’s execution time limit allows.

How do I increase the file upload limit in WordPress?

The most reliable methods are editing your .htaccess file, modifying php.ini, or using a plugin like WP Tools or WP Memory Limit. The specific method that works depends on your hosting environment — some hosts restrict .htaccess PHP overrides, in which case php.ini or a plugin is the better route.

Can this error affect plugin or theme installations?

Yes. Installing a large plugin or theme via the WordPress dashboard triggers the same upload process as a media file. If the plugin or theme file exceeds your server’s upload limit, you’ll see the same error. The fix is identical — increase the relevant PHP limits.

Why does this error keep coming back?

If the error recurs after fixing it, the most likely cause is that your limits were reset by a server update, or that you’re regularly uploading files that exceed the new limits. Setting limits in php.ini (rather than .htaccess) tends to be more persistent. Optimising images before upload is the most effective long-term prevention.