Troubleshooting

Supported browsers

As best practice, we recommend that voters always update their browsers and operating systems to their latest versions before participating in an election conducted via Assembly Voting solutions.

The following list contains the minimum version requirements for browsers to run Electa on the Live Conference Voting setting. Any earlier version not displayed on this list may display a “Browser might not be supported” warning when a voter attempts to access the election system.

This following list was last updated on 22/02/24

Technical abbreviation	Operating system / Device
and_chr 81	Chrome browser Android / Mobile + Tablet
and_ff 68	Firefox browser Android / Mobile + Tablet
and_qq 1.2	QQ browser Android / Mobile + Tablet
and_uc 12.12	UC browser Android / Mobile + Tablet
android 81	Android / Mobile + Tablet
baidu 7.12	Baidu / Mobile + Tablet
chrome 81	Chrome Windows + Mac / Desktop
chrome 80	Chrome Windows + Mac / Desktop
edge 81	Edge Windows + Mac / Desktop
edge 80	Edge Windows + Mac / Desktop
edge 18	Edge Windows + Mac / Desktop
firefox 76	Firefox Windows + Mac / Desktop
firefox 75	Firefox Windows + Mac / Desktop
firefox 74	Firefox Windows + Mac / Desktop
firefox 68	Firefox Windows + Mac / Desktop
ios_saf 13.4	Safari iOS / iPhone + iPad
ios_saf 13.3	Safari iOS / iPhone + iPad
ios_saf 12.2-12.4	Safari iOS / iPhone + iPad
kaios 2.5	Kaios / Mobile + Tablet
op_mini all	Opera iOS + Android / Mobile + Tablet
op_mob 46	Opera iOS + Android / Mobile + Tablet
opera 68	Opera Windows + Mac / Desktop
opera 67	Opera Windows + Mac / Desktop
safari 13.1	Safari for iOS / Desktop
safari 13	Safari for iOS / Desktop
samsung 11.1	Samsung Android / Mobile + Tablet
samsung 10.1	Samsung Android / Mobile + Tablet

The following list contains the minimum version requirements for browsers to authorize via Logins on Electa. Any earlier version not displayed on this list may result in an error when authorizing through Logins. All later versions should be supported.

This following list was last updated on 21/05/25

Technical abbreviation	Operating system / Device

Technical abbreviation	Operating system / Device
Chrome 126	Chrome Windows + Mac / Desktop + Android
Firefox 126	Firefox Windows + Mac / Desktop + Android
Microsoft Edge 126	Edge Windows + Mac / Desktop
Opera 112	Opera Windows + Mac / Desktop
Opera 83	Opera Android
Safari 18	Safari for iOS / Desktop

Common Issues and Solutions in…

In Electa, both users and end-users can encounter issues. Below see an overview of some of the most common issues organized by whether the solution is done in the backend or frontend.

Common issues in the backend:

The maximum number of login attempts is 10 attempts. After this, the user will be blocked, and will not be able to access the voting platform. The user has two options: either wait until the system automatically unlocks the user after 1 hour has passed, or alternatively, follow the instructions sent to the them by email to help them unlock their account. Finally, users with higher levels of permissions can also unlock other users' accounts.

In case of forgotten password or expired tokens (for new users), a user will need to reset their password. To do this, a user needs first go to the login screen of the Electa backend and click on “Forgot password.” This will show them a page in which they enter the email with which they are registered and wait for the email to arrive in your inbox. Afterwards, an email will be sent containing a new link with a valid token. This should be used immediately to prevent another invalid token link.

Often the issue here is that the election’s board has yet to be initialised, which then means that the frontend of the election cannot show. If it has not been initialised automatically when creating the election, make sure to initialise it manually - this can be done under “E2E” and “Election board” (read more here).

There are different reasons why a contest is locked. The contest has been assigned to a voting round, but there are no votes in the voting round yet. To unlock the contest, go to the voting round and deselect the contest that you wish to unlock. After this, go back to the “Contest” page, and the specific contest should now be unlocked and you can edit it. (You are not able to delete it though) Otherwise, if there are votes, you will need to remove the board and reset the votes (this will also allow you to delete the contest). To do this, from the “Summary” page, ensure that “Skip automatic E2E initiation” is enabled. After that, click on “Clear election” and then “Clear Votes”. This will clear all the votes in the ballot. Now, you should be able to make changes to any contest (as well as delete them). Don’t forget to initialise the board before proceeding with your election!

If the election has more than one locale, and the necessary translations have not been correctly filled out in voting rounds, contests, etc, the copying process will fail. Ensure that all mandatory translation fields are filled out.

One way to solve this issue is by deleting the voter importer (which will remove all voters from the system) and re-uploading the voter file with current mappings (ie. mappings that will match the new configuration of election codes) – read more on how to import voters here. A slightly more cumbersome option is to update each voter’s election codes individually – read more on how to edit an individual voter here.

Common issues in the frontend:

Sometimes, end-users (that is, voters) miss their voting credentials. There are two suggestions in this situation: First, ensuring that the voter checks their spam inbox, as sometimes emails sent from Electa can be flagged and end up in the spam folder. Otherwise, users can change the voter’s email address in the backend and re-send new credentials.

“You are not eligible to participate in this election. Please contact support for further enquiry.” This error message appears when an end-user attempts to access a voting round that is closed for voting. In this case, the end-user has to wait until the voting round is opened. Login failed. A possible cause for this error message is that the election has no digital board initialized. As such, you need to confirm this and if necessary initialize it. See how to do this here. “An error happened. Reload the page and try again, if the problem persists please contact support.” This error message appears when an end-user attempts to access a voting round that their voter group is not assigned to. “Election code is invalid. Please verify that the election code is correct before you try again.” This error message appears when an end-user inserts a wrong or mistyped election code. Make sure that they are typing the correct code.

Similarly to Candidacy, both users and end-users can encounter issues. Below see an overview of some of the most common issues organized by whether the solution is done in the backend or frontend.

Common issues in the frontend:

Go to the Candidacy sign-in page in the frontend. Click the “Didn’t receive unlock instructions?“ button. Enter the email with which you are registered and wait for the email to arrive in your inbox. You should now get an email with unlock instructions.

In case of a forgotten password or expired tokens (for new end-users), an end-user will need to reset their password. Go to the Candidacy sign-in page in the frontend Click the “Didn’t receive confirmation instructions?“ or “Forgot your password?“ button For either button, enter the email with which you are registered and wait for the email to arrive in your inbox. You should now get an email with instructions to reset your password.

Instruct the end-user to wait a little as some emails may take longer to arrive in the mailbox than others. Otherwise, they can change their email address in “Edit your account“ in the frontend and re-try.