Hi,
Getting this error logged in watchdog table after submitting a form. No new lead registered in my SugarCRM, and my HTTP Request status jumps on fail in Statusreport when submitting a new webform. A confirming e-mail is correctly sent out with the entered data after submittal of the form.
Running a clean installed D6.19 with only Webform, Webform Validation and Webform2Sugar as additional modules enabled on top of the standard/clean set. Running hosted site. Doing the same thing from a XAMP/Drupal from my laptop works fine, so probably it is somewhere related to the hosting environment, though I am clueless on where to look for a solution.
This is the only module I am experiencing any difficulties with, which is why I am posting the issue here.
Thanks for any pointers,
Cheers
Ernst

Comments

rurri’s picture

rurri commented

Ernst,

Yeah, that obviously sounds like an issue with the setup of the hosting environment. I also noticed the error message was not correctly displaying the url you are posting to. I just checked in a fix for that in the dev branch of 6-x-4.0.

1) Are you posting to http or https? If it is https, there is another fix in the dev branch that was needed in order to make https work.

2) Does your hosting company have a firewall that is preventing you from connecting to your sugar box? Can you attempt to connect to your sugar machine from the command prompt of your hosted environment? "telnet www.mysugarurl.com 80"

Rurri

ejah’s picture

ejah commented

Hi Rurri,
Thanks. I will install the dev branch and see what happens and what I can find from the log files with the URL info in hand and report anything useful back here.
On 1: http
On 2: no shell access with this hoster, though as far as I know there is no such firewall. The Sugar runs as a subdomain of the Drupal domain, as the same user, and is via the web normal accessible (except than in this specific case ...). I will check my Plesk and see whether there are any switches I overlooked.
Any through the web tricks to verify communications?
Ernst

rurri’s picture

rurri commented

If the sugar site is running on the same installation as the drupal site, have you tried localhost or 127.0.0.1 as the url for the sugarCRM? Many hosts are not able to route back to themselves via the public IP and need to use the localhost to talk to themselves.

ejah’s picture

ejah commented

That could be a solution, though solely 'localhost' did not work, I think i need to be more specific, though something like localhost/../subdomains/crm/httpdocs or crm.localhost do not work either. Any suggestions?
b.t.w. where can I obtain the latest dev, as the one published on the site is from 20/11?

rurri’s picture

rurri commented

I think the new dev snapshot had just not been created yet. There is a dev version there listed as: 6.x-4.x-dev Download (11.82 KB) 2010-Dec-13

Although getting this version will only fix https and fix the error message so that it actually displays the url you are attempting to connect to. In the end it looks like a connectivity issue with your sugarcrm server. Without shell access this is pretty difficult to test without creating some sort of custom php script to do the connectivity testing.

I could see a nice feature for this module being one that checks the connectivity in the admin menu when the user enters the url.

Rurri

rurri’s picture

rurri commented
Status: Active » Closed (fixed)

No recent activity. Assuming support request is resolved.