Most common access issues

Most access issues can be resolved with a few checks. Before opening a ticket, try the sequence described here: in most cases, the cause is trivial and the solution is within reach.

Unrecognized credentials

If the system does not recognize your credentials, the most frequent cause is a typing error. Check:

• the email entered, without leading or trailing spaces;
• unintentional activation of caps lock;
• the keyboard language if you use special characters;
• any password managers filling in the wrong email.

If you are certain of your credentials but the login continues to reject them, start the recovery described in How to recover your password.

Login page not loading

If the login page does not appear or remains white, the problem is almost always with the browser or the local network. Try:

• an incognito mode, which disables extensions and cache;
• a different browser or another device;
• a different network (for example, a mobile connection).

2FA code not accepted

Two-factor authentication uses temporary codes synchronized with the device's time. If the code is rejected:

• check that your smartphone's time is set to synchronize automatically;
• wait for the next code generation and try again;
• use a recovery code if you have lost access to the 2FA app.

Account blocked or inactive

In rare cases, the account may be temporarily suspended for security or administrative reasons. In this case, the error message indicates this and directs you to the correct channel. Do not repeatedly retry login attempts: open a ticket from support with the description of the displayed error and wait for the team's response.

Distinguishing between a local problem and a platform problem

A good diagnosis starts with the question: "does the problem occur in another context as well?". If another browser, another device, or another network resolves the issue, the cause is almost always local: cache, extensions, network filters. If, however, the problem occurs everywhere, it is likely related to the platform or the account itself.

This simple test changes the ticket's priority: if you have already excluded local causes, support can focus directly on the account, without asking for verifications you could have done independently.

Signals that help with triage

• Did the problem appear today or has it been recurring for days?
• Does it concern only a specific action or the entire login?
• Does it appear in every browser or only on one?

What to write to support

If you have tried the checks and have not resolved it, a good ticket saves you time. Include:

• the account email (without the password);
• the exact message received during login;
• the browser and device you are using;
• the approximate time of the attempts.

The support team usually responds within a few business days. In the meantime, if you need to consult public information, Arbicsxpedia remains accessible without login.