An error message when declaring your income, a page that keeps loading, a password rejected without explanation: login problems with Urssaf online regularly affect self-employed workers and employers. The stakes go beyond a simple technical inconvenience, since every day of inaccessibility brings you closer to a contribution declaration or payment deadline.
Missed Urssaf deadline during an outage: evidence to keep
When the issue lasts long enough to cause you to miss a filing deadline, the consequences go beyond the technical problem. Late-payment surcharges and fixed penalties: the financial risk of a prolonged login issue is very real.
If the autoentrepreneur.urssaf.fr website or employer account remains inaccessible for more than a few hours, the first thing to do is put together a file of evidence. The goal is to be able to show, when requesting a waiver of penalties, that the delay was not your fault.
- Timestamped screenshots of the error message displayed by the website (blank page, 503 error, redirect loop, rejected login details). The operating system records the date and time in the file metadata.
- Submit a report on the Services Publics+ platform (plus.transformation.gouv.fr), which generates a receipt you can view later. Several users have already documented their inability to log in to Urssaf there.
- Copies of all correspondence with Urssaf support (an email sent through your account’s messaging service, a contact form, or a phone call for which you note the date, time, and name of the person you spoke to).
Once you have gathered this evidence, you can send a written request for a waiver of late-payment surcharges to the Urssaf office you are registered with. The request should explain that the digital service outage prevented you from meeting the deadline on time.
A problem logging in to Urssaf online that coincides with a filing deadline should therefore be documented as soon as it occurs, not after the fact.

Causes of Urssaf account access issues: diagnosis by error type
User reports on Services Publics+ and outage-tracking websites make it possible to group access issues into distinct categories. The table below compares the symptom, its likely cause, and the recommended action.
| Displayed symptom | Likely cause | Recommended action |
|---|---|---|
| “Incorrect username or password” message | Expired password, Caps Lock enabled while typing, or changed email address | Use the “Forgot password” process; check the email address linked to the account |
| Blank page or 503 error | Temporary Urssaf server outage (maintenance or overload) | Try again in a few hours; check recent reports on totalbug.com |
| Endless redirect loop | Corrupted browser cache or cookies | Clear the cache, delete cookies for the urssaf.fr domain, and try another browser |
| Account not found after registration | Activation period not yet complete, or Siret number not yet synced with the Urssaf system | Wait several business days after registration; contact Urssaf by phone if it takes more than two weeks |
| “Social Security number not recognized” | Typing error or account created with a different identifier (Siret number instead of NIR) | Check which identifier is required for your account type (self-employed, employer, independent worker) |
This diagnosis covers most of the reports visible on public platforms. Two issues come up more often than others: a password rejected for no apparent reason and a homepage that will not load at all.
Unable to log in to Urssaf: technical steps to try
Before contacting support, a few quick checks can help rule out issues with your own device.
Browser and cache
The urssaf.fr website uses sessions that expire. An outdated cookie can trigger an authentication loop. Deleting cookies for the urssaf.fr domain and restarting your browser resolves this issue in most cases.
Trying a different browser (Firefox if you use Chrome, or vice versa) can help identify an extension or local configuration issue. Ad blockers and some antivirus programs mistakenly filter requests to government domains.
AutoEntrepreneur Urssaf mobile app
The mobile app is an alternative when the website is down. If you also cannot log in through the app, the problem is probably on the server side. If the app works but the website does not, your browser or network is blocking access.
Testing both the website and the mobile app helps distinguish a server outage from a local issue.
Network and DNS
Some corporate networks and VPN connections block access to Urssaf portals. Switching to a mobile connection (4G/5G) for the test can help clarify the cause.
Contacting Urssaf when your account remains blocked
When none of the technical steps work, contacting Urssaf directly is the only option. Several users report on Services Publics+ that Urssaf’s toll-free number is sometimes unreachable or redirects to an automated phone system with no option to speak to an agent.
There are three ways to resolve the issue:
- Your Urssaf account’s secure messaging service (available only if you can log in, creating a vicious circle if your account is completely blocked).
- The contact form on urssaf.fr, which is available without signing in and lets you describe the problem and attach screenshots.
- An in-person appointment at your regional Urssaf office. This remains the most reliable option for account access issues that cannot be resolved remotely.
If your account has been blocked for several weeks and a deadline has passed, include your documented evidence with your request (screenshots, a Services Publics+ report, and emails sent). The right to make mistakes applies to online administrative procedures when users can demonstrate that they acted in good faith.

Clearing your browser cache, resetting your password, and testing the mobile app can resolve most common access issues. If the problem persists and a deadline is approaching, documenting the incident as soon as the first error message appears and contacting Urssaf in writing with supporting documents is the safest way to create a traceable record.



