IntraParis Nomade is the remote access portal reserved for agents of the City of Paris, accessible from nomades.apps.paris.fr. It allows users to consult their professional email, HR services, and administrative tools outside the internal network. Connection failures to this portal do not always stem from a server outage: in most cases, the blockage comes from the device used, the browser, or the network context from which the agent is trying to connect.
Access context and network filtering: the primary cause of blockage on IntraParis Nomade
An agent connecting from their office, from home, or from an external site does not encounter the same obstacles. This distinction is rarely taken into account during troubleshooting, even though it conditions the solution to be applied.
At the office, the workstation is configured by the IT department. The internal network allows direct access to the intranet without going through the Nomade portal. If an agent tries to use nomades.apps.paris.fr from this network, the connection may fail or loop, because the portal is designed for external access.
At home, the problem often comes from the internet service provider or the firewall of the internet box. Some ISPs apply DNS filtering that blocks institutional subdomains. Changing the DNS server of the box (switching to a public DNS) is sometimes enough to restore access.
On the ground (media library, associative branch, coworking space), shared Wi-Fi networks frequently filter connections to secure portals. Network access control devices intercept HTTPS traffic and prevent authentication from occurring. In this case, switching to the phone’s 4G/5G connection remains the most reliable solution to bypass filtering.
Several agents who encountered recurring difficulties found solutions to connect to Intraparis Nomade by precisely identifying their access context before modifying anything on their workstation.
Browser and cache: the technical settings that block authentication
The Nomade portal uses secure authentication that relies on session cookies and certificates. When the browser is not properly configured, the login page may remain blank, display a certificate error, or loop after entering the password.
Browser choice for nomades.apps.paris.fr
Edge and Chrome are the best-supported browsers. Firefox works in most cases, but some versions apply enhanced security policies on certificates that may reject the connection to the portal. Safari on Mac sometimes poses similar problems.
Using an up-to-date browser is a prerequisite, not just a comfort recommendation. Updates include the root certificates necessary for validating the portal.
Cache, cookies, and session data
A corrupted cache is one of the most common causes of blockage. The portal stores a session cookie during the first attempt. If this attempt fails (incorrect password, network cut), the cookie remains in memory and prevents subsequent attempts from initializing correctly.
- Clear the browser cache and cookies, then restart it before trying to connect again.
- Test in private browsing (incognito mode) to eliminate the possibility of an extension or rogue cookie.
- Temporarily disable ad blocker or integrated VPN extensions, which intercept HTTPS requests to the portal.
If the connection works in private browsing but not in normal mode, the problem comes from an extension or a persistent cookie in the browser profile.
Password and authentication: specific errors related to the agent account
Access to IntraParis Nomade relies on a personal agent identifier and a password. Upon the first connection, a temporary password is assigned, which must be changed immediately. Several common errors are related to this step.
The temporary password has a limited validity period. If the agent does not connect within the allotted time, the password expires, and the page displays a refusal without an explicit message. The reset procedure goes through the dedicated page on vdp-gestionidentitenumerique.apps.paris.fr, or through a request to the HR service.
Another frequent trap: entering the password with caps lock enabled, or with a keyboard configured to QWERTY instead of AZERTY. On a shared workstation, these settings change from one user to another.
- Check the keyboard layout (AZERTY/QWERTY) before any input.
- Test the password in a plain text editor to confirm the entered characters.
- In case of a blocked account after several attempts, contact HR or IT support with the agent identifier and a screenshot of the error message.
Mobile connection to IntraParis Nomade: specifics of the application
A mobile version of the portal exists and allows agents to access their email and certain services from a smartphone. The Nomades application requires specific permissions to function correctly: notifications, network access, and local storage for synchronization.
The mobile application bypasses some browser-related issues, because it manages its own certificates and network stack. An agent blocked on a desktop browser can often connect via the application without difficulty.
However, the application requires a recent version of Android or iOS. On an old phone whose system is no longer updated, installation may fail or authentication may not succeed. Checking the compatibility of the operating system before looking for another issue avoids significant time loss.
The mobile connection is also dependent on the type of network. A filtered public Wi-Fi will block the application in the same way as the browser. The cellular network remains the most reliable channel for Nomade access on the go.
When the blockage persists despite these checks, requesting support from the IT department or HR remains the recourse. Providing the agent identifier, the type of device used, the browser or application, and a screenshot of the error message allows support to process the request without unnecessary back-and-forth.
