What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If DinkToPdf creates one PDF and the next request returns HTTP 502, do not assume Azure requires a particular App Service tier. A 502 only says that the component serving the request stopped receiving a valid response. Find whether App Service or an upstream gateway generated it, correlate the failure with conversion time and resource use, then verify the native wkhtmltopdf files and architecture. Change hosting capacity or packaging only after that evidence points to it.
What the “works once, then 502” pattern means
DinkToPdf is a .NET wrapper around native wkhtmltopdf components. The first conversion can succeed while a later conversion exposes a process, dependency, resource, or gateway problem. Azure App Service guidance groups 502/503 failures into application-level causes such as long-running requests, high CPU or memory use, and exceptions that prevent the app from responding. That makes the symptom a starting point for diagnosis, not proof of a DinkToPdf-specific Azure limitation.
The exact cause depends on your operating system, process architecture, runtime, HTML, conversion duration, and network path. Historical DinkToPdf issue reports show native-library loading and x86/x64 mismatch failures, but they do not establish that every first-success-then-502 incident has the same cause.
1. Locate the component that generated the 502
Direct App Service request
Call the App Service URL directly, bypassing your reverse proxy, CDN, or Application Gateway. Record the UTC timestamp, response headers, body, and any request or correlation ID. Compare that request with App Service HTTP logs and application logs. If the direct call fails in the same way, continue with application and native-runtime checks.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Application Gateway or another proxy
If a gateway is in the path, a separate gateway-side 502 branch exists. Correlate gateway access logs and backend-health probe state with the App Service request. Microsoft’s gateway troubleshooting guidance specifically calls out backend health, host headers, SNI, and access restrictions. Check those only when a gateway actually handles the request; changing App Service code will not fix a gateway that cannot establish a valid backend connection.
2. Correlate conversion timing with app health
Instrument one conversion from start to finish. At minimum, log:
- a request ID and UTC start time;
- the time DinkToPdf is invoked and the time it returns;
- the final HTTP status and response length;
- the exception type, message, and inner exception;
- HTML size, asset count, and whether remote fonts, images, or scripts are used.
In the same time window, inspect App Service diagnostics or Kudu for request duration, CPU time, memory working set, restarts, and process failures. Microsoft describes troubleshooting as three sequential tasks: observe and monitor behavior, collect diagnostic data, then mitigate. A conversion that consistently runs until the request is terminated points toward duration or resource limits; a sudden process exit with a native-load message points elsewhere.
Use a controlled reproduction
- Send the same small, self-contained HTML document repeatedly.
- Send the production document once, then repeat it.
- Run one request at a time, then test limited concurrency.
- Compare a direct App Service call with the gateway URL.
This separates a document-specific failure from a process-lifetime or infrastructure problem. Do not infer a cause from a single historical report without matching logs.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →3. Verify native wkhtmltopdf deployment
Inspect the deployed App Service content, not just your local build output. Confirm that the expected libwkhtmltox file (or the Windows native library used by your package) is present beside the application or in the path your loader expects. Also verify its dependent native libraries are present and loadable.
Check operating-system and architecture alignment
- Identify whether the App Service is Windows or Linux.
- Identify whether the worker process is 32-bit or 64-bit.
- Use the native binary built for that OS and architecture.
- Ensure your .NET process architecture and DinkToPdf native asset agree.
On Linux, a diagnostic shell can report a binary’s architecture with file libwkhtmltox.so and show unresolved dependencies with ldd libwkhtmltox.so. On Windows, inspect the DLL architecture with a PE-binary inspection tool and check application startup logs for “bad image,” “incorrect format,” or entry-point errors. These checks identify packaging mistakes; they do not prove that a 502 is caused by them until the failure window contains the corresponding load error.
Confirm publish output and copy behavior
Make native files part of the published artifact and verify they survive deployment, trimming, or a container build. A common mistake is testing from a development machine where the DLL or shared object exists globally, then deploying an incomplete output directory. Log the absolute path passed to the native loader and the current process architecture at startup so a missing-file problem is unambiguous.
4. Check environment and sandbox constraints
wkhtmltopdf may require operating-system libraries and graphics-related support. If the failure appears only in Azure, compare the deployed environment with the one used locally: OS image, installed shared libraries, fonts, temporary-directory permissions, and available memory. Also check whether your HTML references resources that Azure cannot reach because of DNS, TLS, authentication, or outbound restrictions.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsA public Docker sample demonstrates running wkhtmltopdf in a Linux container that carries its dependencies. It is labeled a demo based on an older .NET Core version, so treat it as a packaging starting point, not a present-day compatibility guarantee. If you choose a container, build and scan the image, pin the wkhtmltopdf package you support, test it on the exact App Service Linux configuration, and document how native dependencies are updated.
Fonts, images, and remote assets
Replace remote assets with local test files to determine whether the renderer is waiting on an unreachable origin. A document that renders locally but hangs in Azure often contains a network dependency rather than an Azure PDF limit. Log the conversion URL and asset failures without exposing credentials.
5. Decide whether capacity is involved
Compare the failed request with CPU, memory, process restarts, and conversion duration. Large, image-heavy documents or concurrent conversions can exhaust a worker even when a small first PDF succeeds. Limit concurrency around the native converter, dispose converter objects according to your library’s lifecycle guidance, and avoid creating unbounded parallel conversions.
Scaling can be a mitigation when measurements show saturation, but it is not a diagnosis. One Stack Overflow report matching this symptom says its author resolved the problem by moving to a Basic plan. That is a single historical anecdote, not evidence that DinkToPdf requires Basic or that a plan change fixes every deployment. Test the smallest change that addresses an observed bottleneck and keep the before-and-after metrics.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match6. Gateway-specific checks
When Application Gateway is present, inspect backend health and probe responses first. Verify that the probe and forwarding configuration use the host name and TLS/SNI expected by App Service. Check access restrictions and whether the gateway’s source addresses are allowed. A gateway-generated 502 can occur even when the PDF code is healthy; conversely, a backend-returned 502 will still require App Service logs and native-runtime investigation.
Practical evidence checklist
| Question | Evidence to collect | What it suggests |
|---|---|---|
| Who emitted 502? | Gateway and App Service headers, logs, request ID | Chooses gateway or application branch |
| When does it fail? | Conversion start/end and request duration | Long request or renderer hang |
| Is the worker unhealthy? | CPU, memory, restarts, exceptions | Resource pressure or process crash |
| Can native code load? | Published files, architecture, dependency output | Missing or incompatible library |
| Does the document matter? | Small fixture versus production HTML | Asset, font, or content-specific issue |
Common failures and fixes
“The DLL has the wrong format”
Cause: native architecture does not match the worker process. Fix: deploy the matching x86 or x64 asset, align the process setting, and verify the published file rather than relying on local copies.
No native file found after deployment
Cause: the file was excluded from publish output or copied to a different directory. Fix: inspect the deployed directory, log the loader path, and adjust project packaging so the file is included.
Small HTML succeeds; production HTML times out
Cause: remote assets, scripts, fonts, unusually large images, or slow application endpoints. Fix: test with local assets, remove unnecessary scripts, measure each external request, and compare conversion duration with the failed request.
App Service logs show a process restart
Cause: crash, memory pressure, or an unhandled exception. Fix: capture the exception and resource metrics, reduce conversion concurrency, and only then evaluate a larger worker.
Direct App Service works but gateway URL fails
Cause: gateway backend health, host/SNI, probe, or access restriction configuration. Fix: correct the gateway path and confirm healthy probes before changing DinkToPdf.
Changing to Basic appears to help
Cause: the additional capacity or environment difference may have removed a bottleneck, but the tier itself is not a documented DinkToPdf requirement. Fix: retain the change only with supporting CPU, memory, duration, or restart evidence, and re-test after deployment changes.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If what you need is a clean image or PDF of a web page for diagnostics, documentation, or regression checks rather than server-side HTML-to-PDF conversion, ScreenshotNeo provides a single request. It accepts consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server exposes take_screenshot, get_page_info, and capture_pdf to Claude, Cursor, and other MCP clients.
Using cURL (see the ScreenshotNeo documentation):
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);Every plan includes its capture options, including full-page and element shots, device or custom viewports, PDF settings, custom CSS and JavaScript, waits, request blocking, cookies and headers, geolocation, caching, signed links, webhooks, bulk capture, and a usage API. The free plan includes 1,000 screenshots per month without a card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account.
Best Value
FAQ
Does a 502 prove Azure killed the request for taking too long?
No. Duration is one possible application-level cause. Confirm it with timestamps, request metrics, and logs, and rule out gateway and native-library failures.
Is Basic the minimum Azure plan for DinkToPdf?
No current universal minimum is established. The Basic-plan result is one historical user report, not a product requirement.
Should I move immediately to Linux containers?
Only when your team can maintain the image and your required wkhtmltopdf dependencies are compatible with the target App Service environment. Validate the sample’s older runtime assumptions first.
Frequently Asked Questions
Can I diagnose this without changing the App Service plan?
Yes. Start with boundary identification, correlated logs and metrics, native-file verification, and a controlled HTML fixture. Scale only when those measurements show a capacity problem.
Why does the first PDF succeed if the native library is wrong?
A first success does not rule out a deployment or lifecycle problem. Later requests may exercise a different code path, asset, concurrency level, or worker state; the logs and native-loader evidence decide which explanation fits.
The Bottom Line
Treat “one PDF works, then 502” as a boundary-and-evidence problem. Identify the component returning 502, correlate conversion timing with health metrics, verify native wkhtmltopdf files and architecture, investigate environment and gateway constraints, and change capacity only when the data supports it.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
