--- title: Troubleshoot DXP slug: dxp/cms12-docs/troubleshoot-dxp docTags: createdAt: 2026-06-01T17:39:49.147Z --- :::hint{type="warning"} **Caution** You should debug code only in the **Integration** environment. You should debug in the Preproduction/Production environments only when absolutely necessary. Contact Optimizely to submit a support ticket for remote debugging. ::: ## Check service status Visit the :::Iframe{code=""} ::: Microsoft Azure Status dashboard for general service operation information. See the [Optimizely service dashboard](http://status.episerver.com/) for Optimizely-specific operational status. ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/5L2Ov5qcHyHv3obuRWB3H_584c961-servicedashboard.png) ## Access Azure Portal Contact Optimizely to [get access to your DXP-specific resources](docId\:BNuzWffvzlfed0Yyu5u9l) in the Azure portal so that you can monitor and troubleshoot your solutions. When logged in, the Azure portal will display information as in the example below. ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/T-10tUhS4KdJ-XAUjuc1p_56e4fc1-azureportal.png) ## Enable debugging You need to enable debugging in the Azure Portal and Visual Studio. You first allow remote debugging in the Azure portal and then attach it to the correct process in Visual Studio. :::hint{type="info"} **Note** See [Microsoft’s Remote Debugger Port Assignments](https://docs.microsoft.com/en-us/visualstudio/debugger/remote-debugger-port-assignments?view=vs-2019) to ensure your remote debugger’s IP address is connected. ::: 1. In the Azure portal, select **App Services**. 2. Select an Integration environment from the **App Services** list. 3. Select **Settings > Configuration**. 4. Open the **General settings** tab and go to the **Debugging**section. a. Set **Remote debugging** to **On**. b. Set **Remote Visual Studio version** to the version being used. 5. In Visual Studio, select **View > Cloud Explorer**. 6. Click the person icon to display your subscriptions. 7. Select your subscription and click **Apply**. 8. Select *subscription* > **App Services** >, right-click on the Integration environment (a subscription with an *inte* suffix), and select **Attach Debugger**. :::hint{type="warning"} **Important** If a connection error occurs with the URL of the site being loaded, go back to the Azure portal, select **Settings > Custom domains** to obtain the IP address that is used by the URL. Add this IP address and the URL from the error message to the `hosts` file on the machine (located at `C:\Windows\System32\drivers\etc\hosts`). For example: `111.111.111.111 INTESite.org`If you get an error message—*Unable to connect to the Microsoft Visual Studio Remote Debugger*—fix this with the following procedure: 1. Get the development machine's public IP. 2. In the Azure portal, go to **AppService > Networking > Access restrictions**. 3. Place the public IP on the allow list. Then repeat step 8. ::: ## Activate logging Optimizely supports writing to the diagnostics log using BLOB storage. See [Log into .Net Diagnostics Trace](docId\:v2tzNKe6zQLSdJ_lny5UQ) for more details on how this works. To activate the logging: 1. Select **App Services** for the Integration environment, and go to **Diagnostics log**. 2. Set the **Application Logging (Blob)** to **On**, select desired **Level** of verbiage, and select a storage account and container under **Storage Settings.** 3. Click **Save** when done. ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/9OJOdLDB-Xl18nS6CZ_yX-20260826-135107.png) :::hint{type="info"} **Note** The Web App will restart when activating the logging. ::: ## Log information and Kudu services Access the website log files in the integration environment using any methods described in this section. ### Download log files Use the download or FTP options available in Azure Portal under **Diagnostics logs** for the environment. ### Kudu services tool Azure websites have an associated "scm" service site, where you can run site extension tools. For DXP, the [Kudu services tool](https://github.com/projectkudu/kudu/wiki/Accessing-the-kudu-service) is available with your access to the Azure Portal. To access the service tool, you add an "scm" segment to the environment site URL, for example `https://epvscms3p60ginte.**scm**.azurewebsites.net`. The service tool lets you access files for the site and display information in Optimizely logs available under `site/wwwroot/appdata` and `logfiles/eventlog`. ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/5Ccj1LIXFpjkZCTx353TP-20260826-135107.png) ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/bhV0556D4GC6D7_GwwrvS-20260826-135107.png) ## Enable detailed error messages You might find it useful to :::Iframe{code=""} ::: turn on detailed ASP.NET error messages in `web.config` for your solution in the Integration environment as an additional debugging tool. ## Deployments Notifications may display at the top of the page sent by the system administrator. Also, support information is provided if you have issues during deployment. ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/-cdqAvv4-JgpUQGlJfvIy_b80188aa27bbe85eb43093011846318066940e70180e85e89f6c624818dfbb78-image.png) An error message displays on the Project page if an unsuccessful deployment occurs. ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/gNxF5KOt7eJ-_idQs3ntL_d9dc9b7f3a08889bd39ae6a2e4da24e2e05ec5a06dd459839b1af34f44c91bb3-image.png) Click **error log for detailed information** to see a summary of the deployment issues. ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/CkreQDijj8cQYMO4FrVkL_e9d6f2b-9086969-paasdeployerrorlog2.png) If the information cannot identify the issues, click **View Job Log** to open the **Job output** view. This contains detailed deployment information, as described in the following section. ### Deployment job log output This view provides information about the sites and environments involved in the deployment. You can also find exceptions, error messages, warnings, and deployment output steps useful when troubleshooting deployment issues. Click **Get Detailed Log**to receive the same information in an email. This is useful if you want to share the information with someone without access to the portal. ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/w1FTa543KWUVaYtui3oSs_f72009e-paasdeployerrorlog3.png) ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/P_UKTBb2x0Ww469sZGwAc-20260826-135107.png) ### Log Stream The *Log Stream* option lets you view output from Optimizely log files to help troubleshoot deployment errors. This option requires enabling diagnostics logging to a BLOB storage, as described in the article :::Iframe{code=""} ::: Enable diagnostics logging for Web Apps in Azure App Service. ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/qd1ed7Nq0ojpYaJ-i_hNe-20260826-135107.png) Click **Open Log Stream Window** to access the log stream. You can hook on the Optimizely logs to monitor the live log stream from site instances. Click **Pause** or **Resume** to stop or continue streaming log information. Click **Clear** to remove the recent log output. ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/vCx2ch4PCZS6wIcLVzJty_41a8872-014a076-paaslogstream.png) **Related blog post:** :::Iframe{code=""} ::: Setting up Continuous Integration with Azure DevOps and Episerver DXC Service (Optimizely DXP) by Stephan Lonntorp