Orchestrav2, the extranet developed by EGI, remains the main entry point for property managers and administrators who need to provide co-owners and tenants with regulatory documents. The login procedure appears simple at first glance, but several technical parameters affect the reliability of access to the portal, especially since the implementation of mandatory electronic notifications.
DNS Configuration and SSL Certificate for the Orchestrav2 Portal
The portal is hosted on the subdomain orchestrav2.egiweb.net. Before any login attempt, we recommend checking that the browser is not blocking the site’s SSL certificate. Some corporate antivirus or office firewalls intercept certificates and generate a NET::ERR_CERT_AUTHORITY_INVALID error.
Recommended read : How to Optimize Your Job Search to Quickly Land an Online Job
In this case, it is not a password issue but rather a network filtering issue on the office infrastructure side. The solution involves adding an exception in the proxy or firewall for the domain egiweb.net. Managers using a corporate VPN encounter this blockage more frequently than those connected directly.
Another often overlooked point is the local DNS cache. If the server’s IP address has changed recently (migration, maintenance), a workstation that retains the old DNS record will display a blank page or a 504 error. A simple DNS cache flush (command ipconfig /flushdns on Windows, dscacheutil -flushcache on macOS) resolves the issue without EGI support intervention.
See also : How to Boost Your Business Performance with Innovative HR Solutions
Property Manager Credentials and Administrator Access Rights
The login to the Orchestrav2 client area is based on a username/password pair assigned by the management office. The property manager account has broader rights compared to the co-owner or tenant account: access to consolidated accounting documents, management of digital submissions, configuration of notification email addresses.
We regularly observe confusion between the main administrator account and collaborator accounts. The administrator account is unique per office and allows the creation of sub-accounts with restricted scopes (read-only on certain buildings, limited access to fund requests). Losing the credentials for this main account requires direct contact with EGI support, as the email reset procedure only works for secondary accounts.
For offices managing multiple co-ownerships, best practice is to document all credentials in a digital vault, clearly distinguishing the master account from delegated accounts. The departure of a collaborator without transferring these accesses can block the publication of documents for several days.
Recovery Email Address: A Critical Point
The email address associated with the account serves both as a password recovery channel and as a proof of support for electronic notifications. Since the law of April 9, 2024, notifications and formal notices in co-ownership must, in principle, be carried out electronically. The extranet thus becomes a channel with legal value, with timestamping and traceability of submissions.
If the email address linked to the property manager account is outdated (former collaborator, full inbox, expired domain), notifications sent via Orchestrav2 lose their enforceability. We recommend checking this address at least once a quarter and favoring a generic office address (like [email protected]) rather than a personal address.
Documentary Obligations and Extranet Configuration for Co-ownership
The extranet is no longer an optional service. The obligations arising from the ALUR law and then the ELAN law require the property manager to provide permanent access to a specific set of documents via a secure space. Among the documents that must be included in the extranet:
- The co-ownership regulations, minutes of general meetings, and the synthetic sheet of the co-ownership
- The annual accounts, the projected budget, and information related to the works fund
- The ongoing contracts (insurance, maintenance, upkeep) and the fund requests issued by the office
A poorly configured extranet, with missing documents or access not granted to certain co-owners, exposes the property manager to a breach of their legal obligations. In Orchestrav2, each uploaded document is linked to a building and an accounting period. Checking the completeness of the document tree is part of the initial login process for a new manager taking over a portfolio.
National Co-ownership Register and Data to Centralize
The decree published on July 19, 2026, enriches the mandatory data of the national co-ownership register, with full enforcement expected in January 2028. Offices must structure and centralize this data now in their management tools. Orchestrav2 serves as a gateway for part of this information, provided that the fields are correctly filled out during the configuration of the property manager account.
Resolving Common Orchestrav2 Connection Errors
Three situations frequently arise in the majority of support tickets related to Orchestrav2:
- The temporary password has expired before the first login: the activation link sent by email has a limited validity period; after this time, a new link must be requested from the office or EGI support
- The browser blocks third-party cookies: Orchestrav2 uses session cookies to maintain authentication, and certain configurations of Firefox or Safari in strict mode reject them by default
- Access is attempted from an outdated browser: versions prior to Chromium 90 do not properly handle the TLS protocol used by the portal, causing a silent connection failure
For the last two cases, the quickest solution is to test the connection in a private browsing window. If access works in private browsing but not in normal mode, the issue comes from a browser extension or a cookie setting that needs to be corrected.
The configuration of Orchestrav2 is not a one-time action. Regulatory developments (electronic notifications, enrichment of the national register) add functional layers that modify access rights and documents to be published. Each change of manager on a portfolio must include an audit of extranet access, just like the transfer of keys or ongoing contracts.