PDF Stamper – Timeout error

[computercourage]

We’re in the process of moving our site over to WPEngine. The issue is that with the larger pdfs, the stamper will time out and generate a 502 Bad Gateway error. Is there any way to get the stamper to execute under 90 seconds, or do you have any other suggestions? Or is it at all possible to get the unencrypted code so that the WPEngine folks can maybe try their hand at it?

Thanks.

[admin]

If the server doesn’t have enough power to handle stamping of a large file then you will have this issue. Ideally it shouldn’t take more than 5-10 seconds to stamp a file if the server is powerful enough (the larger the file, the more power is needed). More details on this here:

http://www.tipsandtricks-hq.com/wp-pdf-stamper/minimum-requirements-for-the-wp-pdf-stamper-plugin-104

With that said, try the following options:

1) Uncheck the “Enable PDF File Encryption” option if you have it checked. PDF file encryption requires good CPU resources so turning that off can help.

2) Try using stamping method 2 for the “PDF Stamping Method” option.

3) Some more helpful discussions on this topic here:

https://support.tipsandtricks-hq.com/forums/topic/is-it-possible-to-speed-up-stamping-takes-30s

[computercourage]

1) “Enable PDF File Encryption” is unchecked.

2) Using method 2 doesn’t seem to make a difference.

WPEngine loads the site much faster than my old host, so I don’t really think it’s a server power issue, though they do have a pretty stringent timeout limit. They’re willing to help work out this issue, but can’t do it if the code is encrypted.

I have noticed that using the Manual Stamping in the Dashboard seems to have a higher success rate than using my custom code to generate the pdfs in the frontend. I’m using the suggested code here: http://www.tipsandtricks-hq.com/wp-pdf-stamper/third-3rd-party-integration-guide-10

Which actually seems to be outdated, and might be part of the problem. Do you have an updated version of this code? I know that for one, this line isn’t applicable anymore:

list ($status, $value) = explode (“n”, $returnValue);

[admin]

If the manual stamping works for this same file then it would be something do with the use of the API, otherwise manual stamping wouldn’t work either. The API requires the ability to do HTTP POST using CURL. I have a feeling this hosting provider has this option turned off. Ask them the following question:

“Do you allow HTTP POST on the same server using CURL?”

[computercourage]

A tech confirmed that HTTP POST is allowed on the same server as CURL.

He does ask:

“However, it’s possible that the timeout may not be with our server. Can you ask the plugin developers whether the stamping is done directly by the plugin, or whether it uses an API to the plugin server to do the stamping?”

In any case, do you have an updated example of the HTTP POST integration guide? I’ve discovered that even if the integration code manages to stamp, Acrobat isn’t able to open the file (this is after I upgraded the plugin, was working fine before), so I think there’s an issue with changed code in the updated plugin.

[admin]

I have checked the 3rd party integration documentation and verified that the given code is working correctly. I have sent you an email.

[Author]

Posts