Most blockages on IntraParis Nomade do not come from the portal. Expired password, poorly configured browser, nomadic authorization never requested: the causes are almost always on the agent’s side. We detail here the technical points to check to restore functional access without having to wait for a prolonged period with support.
Nomadic authorization: the prerequisite that many agents overlook
Having an IntraParis account is not enough to access the nomadic portal. Nomadic access is a separate authorization, distinct from intranet access from a fixed workstation at the town hall. An agent trying to connect from home without this authorization will receive an authentication refusal, often confused with a technical failure.
This authorization must be requested by the hierarchical supervisor via a specific internal form. The processing time varies depending on the departments. We recommend initiating the request several days before the first planned teleworking day.
If the authentication page appears but your credentials are consistently refused while they work on a workstation at the town hall, this is the first point to check with your HR department or IT contact. Many agents experiencing difficulties with connecting to Intraparis Nomade discover at this stage that their profile has never been activated for remote access.
Expired IntraParis password: diagnosis and reset
The password for the IntraParis account has a limited lifespan. An agent who does not regularly connect to the nomadic portal may find their password has expired without being notified, especially if they primarily use a fixed workstation at the town hall where the session is managed differently.
An expired password produces the same error message as an incorrect identifier. The portal does not distinguish between the two cases in its feedback to the user, which generates confusion.
The reset procedure goes through the dedicated page accessible from the portal nomades.apps.paris.fr (link “Forgot password”). You will need to enter your agent identifier. If the self-service reset fails, the IT service of your department remains the only authorized contact to unlock the account.
Preventive reflex to adopt
We recommend testing your nomadic connection at least once before each teleworking day. This simple reflex allows you to detect an expired password or a certificate issue before being blocked on the day itself, without access to nearby support.
Browser and personal VPN: the two most common technical causes
The IntraParis Nomade portal relies on an authentication layer that interacts poorly with certain browser configurations. Two recurring cases arise.
Outdated browser or active script blockers
Extensions such as ad blockers or anti-tracking tools can prevent the authentication page from displaying. The portal loads scripts necessary for session validation. If these scripts are blocked, the page remains blank or returns a generic error.
- Temporarily disable uBlock Origin, Ghostery, or any other script blocker before loading the login page.
- Clear the browser’s cache and cookies, especially cookies related to the domain apps.paris.fr, to eliminate corrupted sessions.
- Use an up-to-date browser (older versions of Firefox or Chrome no longer support certain TLS protocols required by the portal).
- Test in private browsing: if the connection works in private mode but not in normal mode, the problem comes from an extension or a corrupted cookie.
Active personal VPN
A personal VPN (NordVPN, ProtonVPN, etc.) routes the connection through third-party servers sometimes located outside France. The nomadic portal may refuse a connection coming from an unidentified IP address or geolocated abroad. Disabling any personal VPN before accessing the portal resolves this type of blockage in the vast majority of cases.
Connecting to IntraParis from a smartphone: specific points of caution
Accessing from a mobile phone adds a layer of complexity. The default mobile browser (Safari on iOS, Chrome on Android) must be up to date. An outdated operating system can cause SSL certificate errors that the desktop browser does not encounter.
On iOS, the “iCloud Private Relay” mode (enabled by default for iCloud+ subscribers) changes the outgoing IP address. This produces the same effect as a personal VPN: the portal may reject the connection. Disable iCloud Private Relay in the network settings before attempting nomadic access.
On Android, check that the browser is not using a custom DNS (private DNS in network settings) that could interfere with the resolution of the domain apps.paris.fr.
When to contact the IT support of the City of Paris
If all the previous checks have been made without result, the problem is likely due to a server-side blockage or an incident on the infrastructure. Contact the IT contact of your department specifying the following elements:
- The exact error message displayed (screenshot if possible).
- The browser used and its version.
- The type of internet connection (home Wi-Fi, mobile hotspot, public network).
- Confirmation that the personal VPN is disabled and that the cache has been cleared.
- The date of your last successful connection to the nomadic portal.
This information allows support to quickly distinguish between an authorization issue, an expired password, or a network incident, and to avoid unnecessary back-and-forth.
Most agents regain functional access after verifying their nomadic authorization and resetting their password. The remaining causes (browser, VPN, private relay) can be resolved in a few minutes with the right settings. Testing your connection the day before teleworking remains the most reliable way to avoid a blockage on the day itself.