Fixing AutoFirma, browser and certificate problems

Key rules

• Cl@ve: If the portal offers Cl@ve, you can use it instead of AutoFirma and avoid these problems.
• Java: Recent AutoFirma versions do not need Java, so do not install it as a fix.
• Certificate backup: To move a certificate, export it as a .pfx or .p12 file with the private key, not a .cer.
• Firefox: Firefox uses its own certificate store, so a certificate that works in Chrome may not appear there.

Start here: which part is failing?

Nearly every blocker is one of three things: AutoFirma does not open, the browser will not hand over to it, or your certificate is missing from the list. Each has a standard fix. If none works, there is an alternative at the end.

You only need AutoFirma when the portal asks you to sign with a certificate. If the portal offers Cl@ve, you can use that instead and skip AutoFirma completely.

AutoFirma does not open or signing hangs

AutoFirma is the Spanish government's free signing app. It works on Windows, macOS and Linux. Recent versions do not need Java, so do not install it to fix a problem.

Try these in order:

1. Uninstall any old AutoFirma, then download the latest version from the government's official electronic signature site.
2. Run the installer as administrator and restart the computer.
3. Close every browser window, reopen the browser and accept the prompt to open the afirma:// link.
4. Allow AutoFirma through your antivirus and firewall.
5. Open Task Manager, stop any leftover AutoFirma processes, then clear the browser cache.
6. Make sure only one signing session is open.

On a Mac, allow the app in the Security settings. On Linux, check the package is installed and that your browser allows the link to open.

The browser will not connect

Use a current version of Chrome or Edge. If signing hangs in one, try the other. Internet Explorer no longer works, and the old Java-applet signing is gone.

Firefox needs extra care because it keeps its own certificate store. Run the AutoFirma configuration so Firefox trusts the certificate, or import the AutoFirma root certificate by hand.

Your certificate does not show up

A certificate that works in one place can be invisible in another. Chrome, Edge and AutoFirma on Windows read the Windows Personal store. Firefox reads its own. A certificate installed in only one of them will not appear in the other.

Other common causes:

• The certificate has expired or been revoked. Check the dates in certmgr.msc and renew it if needed.
• It was imported without its private key. You need the .pfx or .p12 backup file, not just a .cer file.
• It went into the wrong store, such as Trusted Root or Other People, instead of Personal.
• The intermediate certificates are missing.
• You use a DNIe or smart card and the reader is not detected. Check the reader and its driver.

The fix is usually the same. Export the certificate with its private key as a .pfx from the browser where it works. Import it into the Windows Personal store, or into Firefox under Your Certificates. Then restart the browser.

If nothing works

Try another computer with a fresh install. You can also use the support form or FAQ on the official AutoFirma site. If you are close to a filing deadline, see the deadline-day guidance below and start early.

The documents, checklist, warnings and questions below cover the same steps in short form.

Documents you need

• A digital certificate (for example an FNMT software certificate) installed in your browser or in the Windows Personal store, or your DNIe with a working card reader. It must be valid, not expired or revoked.

• A backup of your certificate as a .pfx or .p12 file that includes the private key, needed if you move it to another browser or computer. A .cer file alone is not enough.

• The current AutoFirma installer, downloaded from the official government site for electronic signatures.

Checklist

• Check the validity dates of your certificate in certmgr.msc and renew it if it has expired.

• Make sure the certificate is in the Windows Personal store, or in Firefox under Your Certificates if you use Firefox.

• Check that only one signing session is open and that your DNIe or smart card reader is detected.

• If it still fails, try another computer or send the problem to the Ministry's support form.

What to watch out for

• Certificate installed in the wrong place: Your certificate may not show up when signing if it sits in a different store than the one the program reads. Chrome, Edge and AutoFirma use the Windows Personal store, and Firefox uses its own.

• Certificate without its private key: A .cer file does not include the private key, so the certificate will not appear for signing. Import the .pfx or .p12 file instead. If the key was marked non-exportable on another computer, you may need to get the certificate again.

• Expired or incomplete certificate: An expired or revoked certificate, or one missing its intermediate certificates, will not work for signing.

• Old AutoFirma or old Java conflicts: An old AutoFirma version or leftover Java copies can stop the program opening or make signing hang. Uninstall the old version, install the latest one and restart the computer.

• Firefox does not trust the certificate: Firefox may not trust the certificate and so may refuse to sign.

The portal or AutoFirma fails on deadline day

If the portal or AutoFirma fails on deadline day, file on paper at a registry before the deadline. Do not wait for the system to come back.

Do not count on an extension

If a portal is down, a deadline extension is not automatic: it only applies if the administration publishes a notice, so file on paper at any registry before the deadline instead of waiting.

The administration decides whether to extend and for how long. Planned maintenance is usually announced in advance on the site itself. For unplanned outages, check the portal's home page for a notice, but treat an unpublished extension as non-existent.

Gather evidence straight away

Do this before you try another route, because it proves the fault was not yours.

• Take full-screen screenshots showing the error message, the web address, and the date and time (keep the clock visible).
• Write down the exact error text or code, and the name and code of the procedure.
• If signing failed, note the AutoFirma and browser versions.
• Keep any partial receipt or reference number.
• Retry a few times and note the time of each attempt. If you can, try another browser or device to show the problem is not on your side.
• Save any incident or maintenance notice shown on the site.

Report the failure

Use the incident or technical support form on the site, or the support email or phone shown there. For State administration procedures, 060 is a general helpline. Keep the case number you are given. Support channels differ between agencies, so use the ones shown on the specific site.

File on paper before the deadline

You can submit a paper filing at any of these:

• The registry of the body the filing is addressed to.
• The registry of any State body or any regional administration.
• The registry of a town hall or other local body that has an agreement with the region.
• A post office (Correos). Hand it over open, so the clerk can date and stamp the form before sealing the envelope.
• A Spanish embassy or consulate, if you are abroad.

The date you hand it in counts as your filing date. Attach a short note explaining the technical failure, with your screenshots, and ask the body to accept the filing as on time.

If you must deal with the administration online

Companies, professionals and some other people are required to file electronically. If that is you, the office may ask you to correct the filing and send it again online. In that case, the date of the corrected filing counts. Keep all your evidence for any later appeal, and ask the office how to handle it when you file.

Frequently asked questions

Do I still need Java to run AutoFirma?

No, recent versions of AutoFirma do not need Java because they bundle their own runtime. If signing fails, check that no old Java copies conflict with it, and install the latest AutoFirma after uninstalling the old one.

Why does my certificate not show up in Firefox when it works in Chrome?

Firefox keeps its own certificate store, while Chrome, Edge and AutoFirma on Windows read the Windows Personal store. Import the certificate file with its private key (.pfx or .p12) into Firefox under Your Certificates, or run the AutoFirma option that makes Firefox trust the system store.

Can I sign with AutoFirma from my phone?

Mobile versions of AutoFirma exist, but the browser setup described here is for Windows, macOS and Linux computers. For a portal that needs certificate signing, a desktop computer is the safer choice.

What can I do if nothing works on my computer?

Try another computer, then use the Ministry's FAQ or support form. A different browser such as Chrome or Edge is also worth a try first.