Skip to content

Connection Troubleshooting

When Test Connection fails on the site form, the message tells you which of a few different things went wrong. This page explains each one.

"No Connection" / "Connection Timed Out"

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

  • Your device is actually online, and the site loads in Safari from 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 sometimes 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), or when the site redirects an HTTPS request to a plain-HTTP address.

Change the site's URL so it starts with https://. If the site cannot serve HTTPS yet, that is the thing to fix first — HTTPS is required explains why Grafida has 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.

Note that Grafida also refuses this when your site starts on HTTPS but redirects to http://, which some servers do by accident after a configuration change. In that case the address you typed is fine and the site's redirect rules are what need attention.

"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. It means the site's TLS certificate could not be trusted: commonly an expired certificate, an incomplete certificate chain, a certificate issued for a different domain name, or a self-signed certificate on a development or staging site.

Grafida will not connect anyway, and offers no way to skip the check — see HTTPS is required. Load the site in Safari on the same device: it will report 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 CA installed and trusted on the device through a configuration profile.

"Token Rejected"

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

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

No working API found at that address

Grafida reached your server, but nothing at the address it tried looks like a Joomla Web Services API. The most common causes:

  • The URL field has more in it than the site's base address — no /administrator, no /api, no language code such as /en.
  • The site's Web Services plugins are not published.
  • A security rule, firewall, or CDN in front of the site is blocking or rewriting the request before Joomla ever sees it. If Grafida sends several requests in quick succession while testing, some hosts' rate limiters treat that as suspicious — try again after a short pause.

Things that look like a connection problem but are not

  • A publish is refused. The connection is fine; Joomla is refusing the specific action, usually because the account does not have the permission it needs — see Publishing.
  • Categories or tags look out of date. Grafida is showing its cached copy. Use Reload metadata — see Sites.
  • The article list looks wrong. Check the filters on the Articles screen; Clear Filters resets them.

When none of the above explains it

If your site connects but something still goes wrong, the Request Log shows you the exact requests Grafida sent and the exact answers it got back. Turn on Debug mode in Settings, reproduce the problem, and read — or export — what it caught.