Skip to content

Connection Troubleshooting

When Test connection fails on the site form, the message names which of several different things went wrong. This page explains each one.

"No Connection" and "Connection Timed Out"

Grafida could not reach your server at all, or it took too long to answer. Check that:

  • This machine is actually online, and the site loads in a browser on the same network.
  • There is no typo in the site's address.
  • A corporate proxy, VPN or firewall is not blocking the request even though a browser gets through — browsers are often configured separately from the rest of the system.

"Insecure Connection Refused"

Nothing went wrong on the network. Grafida decided not to send anything, because the address is not HTTPS. This happens when the URL field starts with http:// or another scheme entirely, and also when the site starts on HTTPS but redirects to a plain-HTTP address.

Change the site's URL so that it starts with https://. If your site cannot serve HTTPS yet, that is the thing to fix first — HTTPS is required explains why there is no "connect anyway" option, and lists the free and standard ways to get a certificate for a public site, an intranet site or a development box.

Where the address you typed is fine and the site redirects to http:// by itself, it is the site's redirect rules that need attention rather than anything in Grafida.

"Certificate Not Verified"

This is reported separately from the two above on purpose: it is not a connectivity problem, and checking your internet connection will not fix it. The server answered; its TLS certificate could not be trusted. Common causes are an expired certificate, an incomplete certificate chain, a certificate issued for a different domain name, and a self-signed certificate on a development or staging site.

Grafida will not connect anyway, and offers no way to skip the check. Load the site in a browser on the same machine: it reports the same problem, usually with more detail about which part of the certificate is at fault.

For an internal site using your organisation's own certificate authority, the fix is to have that authority installed and trusted in Android's own trusted-credentials store.

"Token Rejected"

Your site answered, and answered as a Joomla API, so the address is right. The problem is the token or the account behind it:

  • Check you copied the whole token. Joomla's tokens can end in one or two = characters, and a double-click selection sometimes stops just short of them.
  • Check the token is still Active on that user's profile — see Connect a Site. Switching Active off and back on mints a new token, and the old one stops working immediately.
  • Check the account has the core.login.api permission.
  • Check the account is not blocked, and that it may work with articles in the category you are trying to use.

"Redirect Refused" and "Too Many Redirects"

Your site sent the request on to another address. Grafida follows a redirect only when the destination is still your site and still HTTPS, and stops rather than hand your API token to a host you did not name. It also stops after a reasonable number of hops.

Check the site's URL, and check with whoever runs the site whether that redirect is expected. A redirect from the bare domain to www, or the reverse, is normal and is followed; one that leaves the domain, or drops to http://, is not.

"Could not find a working Joomla Web Services API endpoint at this URL"

Grafida reached your server, but nothing at the addresses it tried behaves like a Joomla Web Services API. The usual causes:

  • The URL field has more in it than the site's base address. Leave off /administrator, /api and any language code such as /en.
  • The site's Web Services plugins are not published — see Connect a Site.
  • A security rule, firewall or CDN in front of the site is blocking or rewriting the request before Joomla ever sees it. Some hosts' rate limiters also treat several requests in quick succession as suspicious; try again after a short pause.

"Site Not Connected"

Grafida has never successfully connected to this site. Open the site's form, make sure a token is entered, and press Test connection.

Things that look like a connection problem but are not

  • A publish is refused. The connection is fine; Joomla is refusing that particular action, usually a permission the account does not have — see Publishing.
  • Categories or tags look out of date. Grafida is showing its local copy. Use Reload metadata on the Articles screen.
  • The article list looks wrong. Check the filters on the Articles screen; Clear filters resets them all.
  • The Articles or Media screen says to select a site. No site is active. Press Set as active site on the Sites screen.
  • The editor's text looks nothing like your site. Grafida could not find your template's editor.css. Set the path by hand — see Sites.