My IntraParis concentrates the essentials of the administrative life of the agents of the City of Paris: payslips, leave requests, professional messaging, access to business applications. The malfunctions on this portal are not merely a technical bug. They often reflect a poor interaction between the workstation, the browser, and the municipal authentication infrastructure.
Account Lockout on My IntraParis after Input Errors
On My IntraParis Nomades, three consecutive incorrect entries lock access to the account. This deliberately low threshold protects against intrusion attempts but regularly traps agents who confuse their personal and professional identifiers.
Read also : Understanding the Main Reasons for Refusals on BlaBlaCar and How to Avoid Them
Unlocking requires the support service of the DSIN. Do not attempt to reset the password while the account is locked, as the procedure will also fail and delay resolution.
The current recommendations for My IntraParis advise to maintain a strong password without periodically changing it, except in cases of suspected compromise. This approach, aligned with contemporary security best practices, reduces blocks related to forgotten recently changed passwords.
Read also : Going Topless on the Beach: Tips and Advice to Take the Plunge
Several agents encounter difficulties precisely because they still apply the old quarterly rotation reflex, which multiplies input errors. The locking mechanism and recovery steps are detailed in the tips on the Le Carolo Geek site.
Initial Account Activation: Anticipating Administrative Delays
The activation of a My IntraParis account depends on the SOI number assigned to the new agent. This number is only generated after the administrative processing of the contract, with a typical delay of one to two working days after signing.
During this window, any login attempt returns an error of type “unknown account” or “invalid identifier.” This is not a malfunction of the portal. The account simply does not yet exist in the directory.
Checks to Perform Before Contacting Support
- Confirm that the SOI number has been communicated by HR, usually via internal mail or email to a temporary personal address
- Ensure that the one to two working days after the contract signing has elapsed
- Test the connection from the City’s internal network (not in nomadic mode) to rule out a certificate or proxy issue
If the delay has passed and the SOI number is confirmed, the blockage then falls under the HR service or the DSIN, not a password issue.
Nomadic Connection: Specific Errors on nomades.apps.paris.fr
The nomadic portal (nomades.apps.paris.fr) adds a layer of authentication compared to internal access. Agents working remotely or traveling encounter errors that on-site users never see.
The most frequent cause is a non-compatible browser or one with a corrupted SSL cache. My IntraParis Nomades operates stably on recent versions of Firefox and Edge. Chrome may cause intermediate certificate issues if automatic updates are disabled.
Troubleshooting Protocol in Nomadic Mode
Start by clearing the cache and cookies specifically related to the paris.fr domain. A simple “clear all cache” does not always suffice, as some browsers keep certificate exceptions in a separate store.
Next, check that the internet connection at home or the remote workplace does not block the ports used by the municipal VPN. Some consumer routers default to filtering outgoing connections on non-standard ports. A test from a mobile hotspot quickly isolates local network filtering.
My IntraParis Messaging: When Emails No Longer Send
Problems sending emails from the integrated messaging system in My IntraParis are not always related to the portal itself. The City’s messaging infrastructure relies on mailbox quotas and antispam rules that can silently block outgoing messages.
When a message remains in the outbox without a visible error, two recurring causes emerge:
- The mailbox has reached its storage quota. Incoming messages continue to arrive (with increasing delays), but outgoing messages are suspended without explicit notification
- The attachment exceeds the size allowed by the municipal SMTP server. The limit is not always displayed in the web interface, leaving the agent uncertain
- The recipient is on an external domain filtered by the City’s outgoing antispam policy, which particularly affects certain free email providers
Deleting large messages from the “Sent Items” folder frees up quota more effectively than emptying the trash, as this folder is often the heaviest and least monitored.
Display Errors and Portal Slowness: Causes on the Workstation Side
A portal that partially displays or takes several tens of seconds to load a page rarely points to a widespread server outage. Browser extensions are the primary cause of display degradation on My IntraParis.
Ad blockers, in particular, interfere with the single sign-on (SSO) scripts used by the portal. Temporarily disabling all extensions and then reactivating them one by one allows for conflict identification within minutes.
Persistent slowness on a desktop connected to the internal network may also indicate a local DNS resolution issue. The workstation then attempts to reach the portal via a suboptimal network route. Restarting the workstation (not just putting it to sleep) forces the renewal of the DHCP lease and DNS configuration.
Agents who switch between the internal network and nomadic mode on the same laptop accumulate contradictory network configurations. Clearing the network configuration before each context switch avoids most unexplained slowness.