Joe_Knighting
New Pleskian
Hi,
I am running wkhtmltopdf on one of my CentOS 6 boxes running Plesk 12.
I have used Plesk since version 10 and up until November 2014 this worked as expected.
Wkhtmltopdf is a tool that uses webkit to generate a PDF version of a web page using command line. It works as expected for all sites that are not hosted on the same server that it is running on. However for anything local it will always resolve the same file as a PDF. (/var/www/vhosts/default/htdocs/index.html)
I have tried adding the domain with loopback to /etc/hosts file as suggested on the wkhtmltopdf Github Issue tracker, however after pinging the domain, although this does change the domain from resolving the external IP of the server to the loopback address (127.0.0.1) the same page is always found and generated by wkhtmltopdf.
I'm sure this is an issue with Plesk's virtual hosts, but I'm not sure where to start to try to identify the problem? Does anyone have any ideas or could give me some advice please?
I am running wkhtmltopdf on one of my CentOS 6 boxes running Plesk 12.
I have used Plesk since version 10 and up until November 2014 this worked as expected.
Wkhtmltopdf is a tool that uses webkit to generate a PDF version of a web page using command line. It works as expected for all sites that are not hosted on the same server that it is running on. However for anything local it will always resolve the same file as a PDF. (/var/www/vhosts/default/htdocs/index.html)
I have tried adding the domain with loopback to /etc/hosts file as suggested on the wkhtmltopdf Github Issue tracker, however after pinging the domain, although this does change the domain from resolving the external IP of the server to the loopback address (127.0.0.1) the same page is always found and generated by wkhtmltopdf.
I'm sure this is an issue with Plesk's virtual hosts, but I'm not sure where to start to try to identify the problem? Does anyone have any ideas or could give me some advice please?