Lucee Authorize.Net Timeout Fix
Budget: $10 – $100 USD
Our checkout used to run smoothly, but for a little over a week every Authorize.Net charge now dies with a connection-timeout. The stack trace supplied by Hostek pinpoints the exact Lucee/CFML line that stalls, yet the host can’t troubleshoot code, so I need the eyes of an experienced ColdFusion-Lucee developer.
Environment
• VPS at Hostek running Lucee 5 on Windows/IIS
• Codebase is classic CFML with Bootstrap and jQuery front-end hooks
• Gateway: Authorize.Net AIM/REST (no other providers configured)
What you’ll do
1. Review the error snippet and any related Lucee logs I provide.
2. Isolate the root cause of the timeout—whether it’s gateway credentials, cURL/TLS, firewall, or Lucee tag/function misuse.
3. Patch the code or server setting so a test transaction succeeds consistently.
4. Hand back the updated files or server instructions with a concise changelog.
Acceptance
• Live and sandbox charges process in under five seconds.
• No new errors appear in server or Authorize.Net reports for 48 hrs after deployment.
• I can roll the fix through Git/SVN or direct file copy in one step.
You’ll have RDP or SSH access (your preference) to a staging clone first, then production once tests pass. If this sounds straightforward to you, let’s get the gateway humming again today.
Environment
• VPS at Hostek running Lucee 5 on Windows/IIS
• Codebase is classic CFML with Bootstrap and jQuery front-end hooks
• Gateway: Authorize.Net AIM/REST (no other providers configured)
What you’ll do
1. Review the error snippet and any related Lucee logs I provide.
2. Isolate the root cause of the timeout—whether it’s gateway credentials, cURL/TLS, firewall, or Lucee tag/function misuse.
3. Patch the code or server setting so a test transaction succeeds consistently.
4. Hand back the updated files or server instructions with a concise changelog.
Acceptance
• Live and sandbox charges process in under five seconds.
• No new errors appear in server or Authorize.Net reports for 48 hrs after deployment.
• I can roll the fix through Git/SVN or direct file copy in one step.
You’ll have RDP or SSH access (your preference) to a staging clone first, then production once tests pass. If this sounds straightforward to you, let’s get the gateway humming again today.