Troubleshooting the Joomla connection

This page covers connections between Content Uploader and a Joomla site. (For WordPress, see troubleshooting the WordPress connection; for a general overview, the connection fails.)

Symptoms#

You see one of the messages listed at the top of this page, Components → Content Uploader Connector says Not connected. or The connection expired. Reconnect to continue publishing., or publishing stops with an error that names the connection or the publishing account.

Two-minute test: can Content Uploader reach the connector?#

Open this address in a browser, replacing the first part with your own site's address:

https://your-site.example/api/index.php/v1/content-uploader/capabilities

• You see a short line of text that starts {"code":"cu_unauthorized" and says Connection invalid, revoked or expired. The connector is installed, its web services plugin is enabled, and the address is reachable from the internet. This is the answer you want: the message is only a refusal, because you are not Content Uploader. If connecting still fails, the cause is the connection itself: continue with The connection was revoked or expired below.
• You see {"errors":[{"title":"Resource not found","code":404}]}. Joomla does not know the connector's route: the Web Services - Content Uploader Connector plugin is disabled, or the package is not installed. Enable the plugin in System → Plugins, or install the connector.
• You see a login page, a Forbidden or Access denied page, a security extension's notice, a blank page or a web server error. Something in front of Joomla is blocking /api/. Continue with Content Uploader cannot reach the site below.

Likely causes and what to do#

"Could not complete the secure connection"#

Confirmed: when you approve, Content Uploader contacts your site once to complete the pairing, and it could not.

When the site did answer, the message says so, as in Could not complete the secure connection (the site answered with HTTP 403). A 403 usually means the invitation expired or was already used, or that a firewall or security extension refused the request. A 404 usually means the connector is not active on the site. The site answered with an error (HTTP 500) means a failure inside the site itself: look in the site's PHP error log, for example for an extension that runs out of memory, and raise PHP's memory limit if it does.

Possible causes, in the order to check them:

1. The web services plugin is disabled. The test above answers 404. Enable Web Services - Content Uploader Connector in System → Plugins.
2. The host blocks /api/, puts it behind HTTP authentication, or does not pass the path after /api/index.php/. Pairing fails with a message that names /api/index.php. Ask your host to allow requests to it, including the Authorization header (Content Uploader also sends a second copy of it, X-CU-Authorization, for hosts that remove the first).
3. A security extension or firewall blocks API requests from an unfamiliar server. Look in its log and allow requests to /api/index.php/v1/content-uploader/.
4. The site's address redirects. Content Uploader does not follow redirects. If http://example.com redirects to https://www.example.com, make sure the address Joomla reports (System → Global Configuration → Server, and the site's own URL) is the one that answers directly over HTTPS.
5. The certificate is not valid (expired, self-signed or issued for another name). Content Uploader verifies certificates and does not accept an invalid one.
6. The site is only reachable over IPv6, on a non-standard port, or on a private address. See the requirements.

Then start the connection again from Components → Content Uploader Connector. You can retry any time before the invitation expires.

"This site must use HTTPS to connect to Content Uploader"#

The connection screen refuses to start because Joomla believes the site is not served over HTTPS. Serve the site over HTTPS, and check System → Global Configuration → Server → Force HTTPS if the site sits behind a proxy that terminates TLS.

"Connection invitation expired"#

Confirmed: more than ten minutes passed. Open Components → Content Uploader Connector and select Connect to Content Uploader again.

The connection screen has no Connect button#

It says Only users who may manage extensions can connect this site or choose the account it publishes as. By default, only Super Users may manage extensions. Sign in as a Super User.

"No account may create articles yet"#

The Publish as list is empty. Add a user to a group that may create articles, such as Publisher, then return to the screen (the publishing account).

"Only the workspace owner can connect a site. Ask them to approve this connection."#

You are signed in to Content Uploader as a team member. Sign in as an owner, or ask an owner to approve the connection (team members).

"The Free plan connects 1 site…"#

The workspace already has the number of sites its plan allows. Upgrade the plan, or disconnect a site you no longer publish to. Reconnecting a site that is already in the workspace is never refused.

"This installation is still connected to another workspace"#

Confirmed: a different workspace, possibly your own other account, has this Joomla installation connected. A site is connected to one workspace at a time. Sign in to the workspace that has it, open Sites and select Disconnect on the site (workspace owners only), then start again at Components → Content Uploader Connector in Joomla and approve the connection in the workspace you want. Once a workspace has disconnected the site, any other workspace can connect it. Nothing is deleted: the first workspace keeps its configurations and publishing history, and the new connection starts without them. Contact support if you cannot reach the workspace that has it.

"The connection expired or permission was revoked. Reconnect in Joomla."#

Confirmed: your site refused Content Uploader's key. Possible causes: access passed its 90 days; someone selected Disconnect or disabled the web services plugin; the connector was uninstalled and installed again; the site was restored from a backup that does not contain the connection. Reconnect from Joomla.

"The Joomla account Content Uploader publishes as no longer exists, is blocked or may no longer create articles"#

Confirmed: every request checks the publishing account. Possible causes: it was deleted or blocked, or its group lost the right to create articles. The connection screen also says it: This account is blocked or may no longer create articles, so publishing fails. Choose another account and reconnect. or An account that no longer exists. Choose another account and reconnect. Choose an account that works under Publish as and select Reconnect.

"The Content Uploader extension on this site is outdated or not active"#

Either the web services plugin is disabled (the test above answers 404) or the connector is too old. Enable the plugin, or update the connector, then select Refresh fields on the Sites page.

"The Joomla installation identity changed. Reconnect the site."#

The site answered with a different identity than the one that was connected, for example after it was moved or restored. Reconnect it from Joomla.

How to verify it is fixed#

1. On Sites, the site shows connected, with an end date about 90 days away.
2. Refresh fields completes without an error.
3. The configuration editor lists Articles and the article fields.

If the problem persists#

Write to support with: the exact message, the address of your site, the Joomla, PHP and database versions (System → System Information), the connector version, the name of any security extension or firewall, and what the two-minute test showed. Do not include passwords. Contacting support says what to expect.