MyCitya brings together document consultation, charge payments, and exchanges with your Citya manager on a single portal. When the connection fails, the blockage rarely comes from a simple forgotten password. Several technical factors, often related to the very architecture of the platform, explain why access is interrupted at specific times.
MyCitya outages and load peaks: what the incident calendar reveals
Reports of outages on the Citya portal are not randomly distributed. The independent tracking site TotalBug records a concentration of alerts in the evening and at the beginning of the month, a time when tenants and co-owners log in simultaneously to pay rents and charges.
Recommended read : How to Successfully Compare a Casden Home Loan with Traditional Banks
In the spring of 2026, several widespread incidents were reported: 500 errors and inability to validate authentication. These episodes are not mentioned in any competing guide, even though they potentially affect all users at the same time.
| Type of incident | Typical time | User-side symptom |
|---|---|---|
| 500 Error (server) | Beginning of the month, evening | Blank page or generic error message |
| Authentication failure | Peak of simultaneous connections | Credentials denied despite correct information |
| Reset email not received | Any time | No message in the inbox or spam |
| Excessive loading time | Peak hours | Portal spinning without ever displaying the dashboard |
When the problem is a server outage, no user-side manipulation resolves anything. Checking TotalBug before resetting your password saves time and, most importantly, prevents locking your account after several unsuccessful attempts.
You may also like : How to Plan an Unforgettable Wedding with Professional Tips
Many users trying to log in to MyCitya interpret an authentication denial as a password issue when the server is temporarily unavailable.
Technical separation between citya.com and espaceclient.citya.com
A point rarely explained in existing guides: the showcase site citya.com and the secure extranet operate on distinct domains. The authentication brick is hosted on espaceclient.citya.com, with its own password reset page.
This architecture has direct consequences on troubleshooting.
- Reset emails come from an address linked to the espaceclient subdomain, not from the main citya.com domain. Some anti-spam filters automatically classify them as suspicious because the sending domain differs from the one the user knows.
- A favorite saved on citya.com/mycitya redirects to the extranet, but if the redirection fails (outdated browser cache, blocking extension), the user remains on a page that never loads the login form.
- Session cookies are compartmentalized between the two domains. Logging out of citya.com does not log out of the client area, and vice versa. A cookie conflict can cause a redirection loop.
To bypass these blockages, access espaceclient.citya.com directly from your browser’s address bar instead of going through the “My account” button on the showcase site.
Outdated email address: the invisible blockage of MyCitya
Since 2025, several third-party sources (Cogim-Parisel, Crisimmo) have reported a recurring scenario: the email address registered in the Citya system no longer matches the one used by the client. The password reset then sends the link to an inaccessible inbox, without any explicit error message on the portal side.
The MyCitya portal does not allow you to change the email address associated with your account yourself. The update must be done directly with your Citya agency, by phone or in person. As long as this correction is not made, any password recovery procedure remains blocked.
This scenario particularly affects co-owners who have changed their internet service provider or mobile operator since creating their account. The old address at @orange.fr or @sfr.fr may no longer exist at all.
Checks to make before contacting the agency
First, test the “Forgot password” procedure on espaceclient.citya.com. If no email arrives within ten minutes (including in the spam folder), the problem is likely related to the registered address. Prepare an ID and your client reference before calling your agency: changing the email requires identity verification.
Browser-side resolution: cache, JavaScript, and extensions
When the server outage is ruled out and the email address is correct, the problem often lies in the browser. The MyCitya extranet relies on JavaScript scripts to display the login form. An ad blocker or security extension may prevent the form from loading without displaying any visible error message.
- Temporarily disable extensions (uBlock Origin, Adblock Plus, Privacy Badger) or test the connection in private browsing, which loads the browser without extensions by default.
- Clear the cache and cookies specifically for the domains citya.com and espaceclient.citya.com. On Chrome: Settings, Privacy, Cookies, search for “citya” and delete the associated entries.
- Ensure that JavaScript is enabled for the domain. Some corporate configurations disable JavaScript by default on sites not listed in a whitelist.
- Use an up-to-date browser. Older versions of Internet Explorer or Safari no longer support certain TLS security protocols required by the extranet.
However, if the form displays correctly but authentication fails in a loop, the problem lies with the server or the identifier, not the browser.
The majority of MyCitya blockages are resolved by first identifying the affected layer: server, authentication domain, email address, or browser. Acting on the wrong layer (resetting a password during a server outage, clearing the cache when the email is outdated) only delays access to the portal. Check TotalBug, then test espaceclient.citya.com in private browsing, and contact the agency if nothing works: this diagnostic order covers almost all encountered cases.