# Troubleshooting Chrome Dependencies in IronPDF
The Google Chromium HTML renderer is an essential part of IronPDF's "Html To PDF" rendering process. The essential binary for this renderer should be readily found inside the IronPDF NuGet package. Absence of this binary from the project folder will throw the following error:
```txt
Unhandled exception. IronSoftware.Exceptions.IronSoftwareDeploymentException: Error while deploying IronPdf Chrome renderer: 'Unable to locate 'IronInterop'.
```
If IronPDF is unable to deploy Chrome Dependencies automatically, they may need to be added to a project manually via NuGet. Multiple dependencies can be added:
- [`IronPdf.Native.Chrome.Windows`](https://www.nuget.org/packages/IronPdf.Native.Chrome.Windows/)
- [`IronPdf.Native.Chrome.Linux`](https://www.nuget.org/packages/IronPdf.Native.Chrome.Linux/)
- [`IronPdf.Native.Chrome.MacOs`](https://www.nuget.org/packages/IronPdf.Native.Chrome.MacOs/)
[[i:(In later versions of IronPDF, the required binaries will be automatically downloaded from the NuGet source based on the OS used during runtime, if they are absent from the project folder. This will be successful as long as the project is connected to the Internet and has Read, Write, and Execute permission to the project folder.)]]
On Windows, it is a good idea to ensure the target operating system has [Visual C++ Runtimes](/troubleshooting/visual-c-redistributable-for-visual-studio-ironpdf/) installed. Many modern applications cannot run without this essential operating system component.
We also have compatibility guides for [Linux](/get-started/linux/) and [Docker](/get-started/ironpdf-docker/).
## Linux
- Ensure the correct Docker file is used.
- Use the IronPdf.Linux NuGet package instead of IronPDF.
- Set GPU mode for Chrome rendering to disabled:
```csharp
IronPdf.Installation.ChromeGpuMode = IronPdf.Engines.Chrome.ChromeGpuModes.Disabled;
```
- Disable the automatic configuration for Linux and Docker dependencies:
```csharp
IronPdf.Installation.LinuxAndDockerDependenciesAutoConfig = false;
```
## MacOS
- Check that the .NET runtime is set to the correct architecture - x64 or arm64.
### What to do if that does not solve it?
If that does not fix the issue, we are here to assist. Compatibility is a high priority for our engineering team. Please send an email bug report to [support@ironsoftware.com](mailto:support@ironsoftware.com). All compatibility issues will be seriously reviewed by a senior engineer.
Be sure to let us know about the operating system/platform being deployed to, especially if it is a cloud platform like AWS or Azure.
#### How to Enable Native Logging in IronPDF
Attaching log files to a bug report more than *doubles the probability that we can isolate the issue and solve it rapidly.*
Place this at the top of your code before running any IronPDF methods (all versions after 2021.3.1):
```csharp
// Set the log file path, this can be a directory or a full file path
IronPdf.Logging.Logger.LogFilePath = "Default.log";
// Enable all logging modes for detailed logging information
IronPdf.Logging.Logger.LoggingMode = IronPdf.Logging.Logger.LoggingModes.All;
```
Log files created by IronPDF are found in the /bin directory of your project where your DLLs are deployed:
- default.log (Deployment process)
- cef.log (Rendering)
- IronSoftwareCefSubprocess.log (Rendering & Threading)
- [IronSoftwareEngine.log](/troubleshooting/timeout-while-rendering-pdf/) (Useful for debugging exceptions beginning with "Error generating PDF from...")
Cloud servers often have specific locations for log files. We have guides for generating log files in [Azure](/troubleshooting/azure-log-files/) and [AWS](/troubleshooting/aws-log-files/).
The Google Chromium HTML renderer is an essential part of IronPDF's "Html To PDF" rendering process. The essential binary for this renderer should be readily found inside the IronPDF NuGet package. Absence of this binary from the project folder will throw the following error:
Unhandled exception. IronSoftware.Exceptions.IronSoftwareDeploymentException: Error while deploying IronPdf Chrome renderer: 'Unable to locate 'IronInterop'.
Unhandled exception. IronSoftware.Exceptions.IronSoftwareDeploymentException: Error while deploying IronPdf Chrome renderer: 'Unable to locate 'IronInterop'.
Text
If IronPDF is unable to deploy Chrome Dependencies automatically, they may need to be added to a project manually via NuGet. Multiple dependencies can be added:
Please note: In later versions of IronPDF, the required binaries will be automatically downloaded from the NuGet source based on the OS used during runtime, if they are absent from the project folder. This will be successful as long as the project is connected to the Internet and has Read, Write, and Execute permission to the project folder.
On Windows, it is a good idea to ensure the target operating system has Visual C++ Runtimes installed. Many modern applications cannot run without this essential operating system component.
We also have compatibility guides for Linux and Docker.
Linux
Ensure the correct Docker file is used.
Use the IronPdf.Linux NuGet package instead of IronPDF.
Check that the .NET runtime is set to the correct architecture - x64 or arm64.
What to do if that does not solve it?
If that does not fix the issue, we are here to assist. Compatibility is a high priority for our engineering team. Please send an email bug report to support@ironsoftware.com. All compatibility issues will be seriously reviewed by a senior engineer.
Be sure to let us know about the operating system/platform being deployed to, especially if it is a cloud platform like AWS or Azure.
How to Enable Native Logging in IronPDF
Attaching log files to a bug report more than doubles the probability that we can isolate the issue and solve it rapidly.
Place this at the top of your code before running any IronPDF methods (all versions after 2021.3.1):
// Set the log file path, this can be a directory or a full file pathIronPdf.Logging.Logger.LogFilePath = "Default.log";// Enable all logging modes for detailed logging informationIronPdf.Logging.Logger.LoggingMode = IronPdf.Logging.Logger.LoggingModes.All;
// Set the log file path, this can be a directory or a full file path
IronPdf.Logging.Logger.LogFilePath = "Default.log";
// Enable all logging modes for detailed logging information
IronPdf.Logging.Logger.LoggingMode = IronPdf.Logging.Logger.LoggingModes.All;
' Set the log file path, this can be a directory or a full file pathIronPdf.Logging.Logger.LogFilePath = "Default.log"' Enable all logging modes for detailed logging informationIronPdf.Logging.Logger.LoggingMode = IronPdf.Logging.Logger.LoggingModes.All
' Set the log file path, this can be a directory or a full file path
IronPdf.Logging.Logger.LogFilePath = "Default.log"
' Enable all logging modes for detailed logging information
IronPdf.Logging.Logger.LoggingMode = IronPdf.Logging.Logger.LoggingModes.All
Log files created by IronPDF are found in the /bin directory of your project where your DLLs are deployed:
Curtis Chau holds a Bachelor’s degree in Computer Science (Carleton University) and specializes in front-end development with expertise in Node.js, TypeScript, JavaScript, and React. Passionate about crafting intuitive and aesthetically pleasing user interfaces, Curtis enjoys working with modern frameworks and creating well-structured, visually appealing manuals.
