> For the complete documentation index, see [llms.txt](https://docs.dorg.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dorg.pro/install-dorg/troubleshooting/installation-troubleshooting.md). # Installation Troubleshooting #### Installer reports an error when checking login to the subscription The installer may fail at the very intial checks to detect or validate the current Azure login session. This issue typically occurs when the user has access to **multiple subscriptions within the same tenant**, and the active subscription context is not correctly selected. Ensure the correct subscription is active before running the installer. Example using Azure CLI: ``` az account show az account set --subscription az login --tenant ``` If the issue persists, contact support. *** #### Unable to find the Admin Key option on Claude Platform If you can't find the menu option **Organization Settings > Admin keys**, you should need to assign the Admin role to at least one of your users on Claude Platform. *** #### Installation stops reporting inability to create a resource due to availability or quota limits The installation may fail if Azure cannot provision a required resource because of: * **Subscription quota limits** * **Regional capacity shortages** * **Unavailable SKUs in the selected region** Review the guidance in the [**Azure Preparation**](/install-dorg/install-a-new-dorg/azure-preparation.md) page to verify quotas, SKU availability, and regional capacity before retrying the installation. *** #### Installation stops reporting AKSCapacityHeavyUsage error The `AksCapacityHeavyUsage` is an occasionally error caused by a significant growth in demand for Azure Kubernetes Service in the specific region. Capacity is often reclaimed when other users stop or delete their AKS clusters. Therefore, the operation might succeed if you retry it later. {% embed url="" %} When this error occurs, the resources in the resource group can be left in a dirty state, so it is suggested to completely delete the resource group, recreate it and re-run the installation from scratch. *** #### Installation stops with an error like "missing required property 'principalId'" That message is a known glitch in the deploy tooling: the installer can occasionally try to assign a role to a managed identity before Azure has finished publishing its principal id. Close the installer and run it again; a second run usually completes normally. If it still fails after a couple of retries, update to the latest installer / project bundle and try once more.\ Re-run may require the resource that caused the issue to be started. In that case, start the resource (for example, a Postgres database) and re-run the installer again. *** #### Dorg does not answer when contacted via Teams Possibile causes: * Missing Office 365 license assigned to the Dorg user. * Dorg user has not be authorized properly (see [Authorize your Dorg User](/install-dorg/install-a-new-dorg/post-install-configurations.md#authorize-your-dorg-user)). * The contacting user does not belong to the same Entra ID Tenant. * User is a Guest user: see the next paragraph. *** #### Dorg does not answer when contacted via Teams by a Guest user A Guest user may exist in the customer's tenant but not yet be active within the Teams context. In this state, the user is unable to initiate or receive chats with Dorg users. The issue is resolved by completing the activation process through accepting an invitation to a group chat within the host tenant. Activation procedure 1. **Any member of the host organization** adds the Guest user to a group chat within the host tenant. It does not need to be a DORG user. 2. The Guest user **opens Teams and accepts the invitation** to the chat. Teams will perform a context switch to the host tenant and trigger the authentication flow against the host Entra ID. 3. Verify that the host tenant name is visible at the top of Teams, and not the user's personal or company tenant. 4. From this point, the user is active as a Guest and can **start a conversation with Dorg** directly in Teams. Note: this step is only required once per tenant. Once the first invitation has been accepted, the Guest user will not need to repeat the procedure. If the issue persists: verify that the Guest user account exists in the host tenant's Entra ID and has been assigned a valid Office 365 license. *** #### Installation stops with an ETIMEDOUT error on 127.0.0.1:56671 This error usually indicates that the local Pulumi/Node process cannot open a TCP connection to the local engine on `127.0.0.1` (loopback), and not necessarily an internet/network outage: `Error: 14 UNAVAILABLE: No connection established. Last error: Error: connect ETIMEDOUT 127.0.0.1:56671.` To diagnose it, run the PowerShell loopback test script below; if it returns OK, local loopback is working and the issue is likely elsewhere in the stack, but if it returns BLOCKED, loopback traffic is being silently dropped on the same machine, which is most commonly caused by endpoint protection or corporate security controls (e.g., restrictive Defender Firewall rules, EDR agents such as CrowdStrike/SentinelOne/Sophos/Trellix, or VPN/proxy filters like AnyConnect, Zscaler, or Netskope). {% code overflow="wrap" %} ```powershell $p=56671; $proc=Start-Process node -ArgumentList '-e',"require('net').createServer().listen($p,'127.0.0.1');setInterval(()=>{},1000)" -WindowStyle Hidden -PassThru; Start-Sleep -Seconds 2; $ok=(Test-NetConnection 127.0.0.1 -Port $p -WarningAction SilentlyContinue).TcpTestSucceeded; Write-Host ""; Write-Host "=== Loopback IPv4 test (127.0.0.1:$p) ===" -ForegroundColor Cyan; if($ok){Write-Host "RISULTATO: OK" -ForegroundColor Green; Write-Host "Il loopback IPv4 funziona. Pulumi/Node possono parlare con l'engine locale."; Write-Host "Il problema NON viene dalla rete locale di questa macchina."}else{Write-Host "RISULTATO: BLOCCATO" -ForegroundColor Red; Write-Host "Il loopback IPv4 sulla stessa macchina e' bloccato (pacchetti droppati, non rifiutati)."; Write-Host "Causa quasi certa: endpoint protection / firewall locale che intercetta TCP loopback."; Write-Host "Candidati tipici: Defender Firewall con regola restrittiva, EDR aziendale (CrowdStrike,"; Write-Host "SentinelOne, Sophos, Trellix), VPN/proxy (AnyConnect, ZScaler, Netskope), anti-cheat."}; Stop-Process -Id $proc.Id -Force -ErrorAction SilentlyContinue ``` {% endcode %} #### Dorg does not answer and the Console shows a Token issue If you have just installed a new Dorg, ensure that you have completed the [Authorization](/install-dorg/install-a-new-dorg/post-install-configurations.md#authorize-your-dorg-user) phase, and [granted](/install-dorg/install-a-new-dorg/post-install-configurations.md#grant-dorg-permissions) the Microsoft Graph application permissions.\ \ If you have upgraded to a new Dorg version, ensure that you have [granted](/install-dorg/install-a-new-dorg/post-install-configurations.md#grant-dorg-permissions) any new Microsoft Graph permission introduced by the new Dorg version. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dorg.pro/install-dorg/troubleshooting/installation-troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.