by Fanatical Labs

Save Your Team Countless Hours. SugarChimp syncs your lists in both directions so you can work in your preferred app. Segment and group your Mailchimp subscribers based on Sugar data so you can market to the right people at the right time. Compatible with all versions and editions of Sugar and SuiteCRM. Created by Fanatical Labs, 2023 SugarCRM Partner Award Winner.

Free 30 day trial
Try it Now

By clicking you consent to share your profile with the developer

#3362 - Network / Firewall problem in highly secured environment

Closed Installation created by ITS4U Verified Purchase 6 years ago

Dear team, We're currently setting up SugarChimp on a Sugar 7.9 on premise instance. The server is tightly secured and we get an error wessage during the prechecks: "Unable to reach Mailchimp, code 0, time out... " We suspect that the Sugar server cannot reach both Sugaroutfitters for license validation and Mailchimp for account setup.

Would you be so kind as to specify the specific firewall configuration that is recommended? Whitelisted URLs, ports...

Thanks in advance, Damien & the ITS4U team

  1. fanatical_jon member avatar

    Jon S Provider

    6 years ago

    Hello Damien,

    Thanks for reaching out. As you've said, it seems that you are unable to reach MailChimp for api calls, and possibly SugarOutfitters for licensing. You need to be able to send outbound requests to: - ..mailchimp.com - *.sugaroutfitters.com

    That should let you get through the setup steps appropriately. However, you will also need to be able to receive inbound requests from MailChimp webhooks. Per their support, they have an ip range for those calls that include: - 205.201.140.14 - 104.196.50.52 - 104.196.213.130 - 104.196.139.222

    Are you behind a proxy of any kind? We have special proxy configuration if that is the case. We can discuss that as well. Let me know how far that gets you.

    Kind Regards, Jon

  2. ITs4U member avatar

    ITS4U Verified Purchase

    6 years ago

    Hello Jon,

    Thanks for the info! The outbound requests are already allowed to *.mailchimp.com & *.sugaroutfitters.com, but we are indeed behind a proxy. I was not aware of any extra configuration for SugarChimp, I configured the proxy using SugarCRM administration->System Settings, but I'm still getting this error.

    Can you describe me the special configuration that needs to be done? In the meantime I will ask the IT team to grant access to the IP you mentioned, and allow them to perform inbound requests.

    Thanx again,

    Christopher & the ITs4U Team

    • fanatical_jon member avatar

      Jon S Provider

      6 years ago

      Hello Christopher,

      We are working on updating some documentation on this process as it is becoming more and more necessary. Are the outbound requests going through the proxy, or inbound requests are hitting a proxy before coming to Sugar? These settings are only for outbound proxy setups. You can update the config quickest through the browser console. In SugarCRM, just right-click and inspect the page. From the console tab, run this command:

      SUGAR.App.api.call('get',SUGAR.App.api.buildURL('SugarChimp/setting/outbound_proxy/192.168.1.1:8080'),{},{});

      Change the "192.168.1.1:8080" to the appropriate outbound proxy and you should get to the outside world.

      If that still does not get what you need, then check that .mailchimp.com works the same as *..mailchimp.com. I've seen where the double asterisks were needed, even though it seems counter-intuitive. Let me know how it goes.

      Best Regards, Jon

  3. fanatical_jon member avatar

    Jon S Provider

    6 years ago

    Hello again,

    I've just noticed that markdown is ruining my asterisks. If you are still not working, I was going to suggest trying to add: "asterisk".*asterisk".mailchimp.com to your acceptable domains.

    Let me know.

    Jon

  4. fanatical_jon member avatar

    Jon S Provider

    6 years ago

    Hello Christopher,

    I know that you've got another support case above that is related to a secured customer instance.

    I am going to close this case out now. If you have any further questions you are welcome to reply here or to your new support case.

    Cheers! Jon

This case is public. Please leave out any sensitive information such as URLs, passwords, etc.
Saving Comment Saving Comment...
Rating
Rating
  • "The team is always proactive in assisting with any questions. Keep up the great work! Great product and great support!"

    Read More Reviews