|
|
Rank: Newbie
Groups: Member
Joined: 10/10/2016
Posts: 8
|
We are currently updating our web applications to the new Eo.PDF Version (coming from the one-assembly-version).
All calls to local websites and resources are impossible now, which results in empty or wrong styles in the converted website.
Using the new version in Visual Studio on a local pc works though. As soon as it is deployed on our IIS Server on another machine, it stops working. Using the classic engine works; but now we have updated the page with new CSS styles etc., so this is no option.
I'm looking forward for an answer,
sincerely
Jan Fiedler
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi, Make sure you do not use ConvertUrl/ConvertHtml to callback to your own site. This can trigger ASP.NET deadlock and cause it fail to render dependency resources. If you use ConvertUrl/ConvertHtml, change it to ASPXToPDF/MVCToPDF. If you are still missing styles, see here for troubleshooting steps: https://www.essentialobjects.com/doc/web/aspxtopdf/troubleshoot.aspxIf it still does not work, then we may need to have access to your server so that we can investigate further. Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 10/10/2016
Posts: 8
|
It is working now. The problem was, Chromium now resolves "localhost" as [::1], not as 127.0.0.1 . Adding the ::1 as a binding to the local IIS fixes the problem!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Ah! [::1] is the IPV6 address for local host. Thank you very much for sharing!
|
|