The token is what tells the Ultrapack Auto Updater installed on your site that it belongs to your account. Without it, the plugin installs and activates normally, but doesn’t find any update, and that’s how most “no update showing up” cases begin.
Where to generate it
Log into your account and go to Manage Sites (UAU). That’s where the token is generated and where the sites already linked are listed.
Copy the token and paste it into the designated field in the plugin settings, inside your WordPress. Save. The screen starts listing the managed items: if it listed them, it’s working.
Mistakes when pasting
Two things to watch out for solve most rejections:
- Space at the beginning or end. Copying with an extra space is common and the token gets rejected without explaining why. Paste it and delete any spaces at the ends.
- Truncated token. If you copied it from an email or a narrow screen, check that it came through in full.
One token per site
Each linked site takes up a slot, and the number of slots comes from your plan. The Manage Sites screen shows how many you have and how many you’ve used.
Two details that cause rework: a subdomain counts as another site (loja.seusite.com.br is different from seusite.com.br), and a test site you abandoned keeps taking up a slot. Remove the old one on the same screen before linking a new one.
It suddenly stopped working
In order of likelihood:
- The subscription expired or is being processed. The token stops being valid along with it. Check the status in your account.
- The site changed address. Migrated domain, dropped
www, switched to HTTPS, or was moved to a subfolder: the link was to the old address. Remove it and link again. - The token was regenerated. Generating a new one invalidates the previous one. If you have several sites, all of them need the new token.
- You’ve hit the site limit. The screen warns you; remove one you no longer use.
If none of that is it
Before opening a ticket, open Settings > Ultrapack Auto Updater > Logs. Every attempt is logged there, with the reason for the failure. Send that snippet along with the exact domain of the site: that’s the information that resolves it in the first response instead of the third.
