Md. Ashikur Rahman

Hello @theblueli,

We apologize for the delayed response.

The URL https://ci3.googleusercontent.com/meips/... is a proxy URL used by Gmail to cache and serve images. If the original image URL (https://mysite.com/wp-content/uploads/...) is not accessible, Gmail’s proxy cannot fetch it.

Please check the following:

1. Verify if the image URL is accessible directly by visiting it in your browser.
2. Ensure there are no issues with the file’s permissions. The image file should be publicly accessible (e.g., 644 permissions).

If the issue persists, you can also contact our support. Our team will look into this further for you.

Thank you!

Hello @indigetal,

Thank you for taking the time to share your experience and for your kind review!

We’re delighted to hear that FluentCRM is working well for you and that our support team was able to provide a helpful solution. Ensuring flexibility and offering reliable support are key priorities for us, so it’s great to know we met your expectations.

Wishing you all the best as you build and grow with FluentCRM.

Thank you!

Hi @hudsontek,

Since FluentCRM only has a single, global opt-in feature, our clients typically use the single opt-in option.

However, you can set up different page redirections based on tags. This allows you to redirect users to different URLs depending on the tag assigned to them. You can check the blog linked here and the provided screenshot. To set this navigate to Settings > Double Opt-in Settings page.

Thank you!

Hello @hudsontek,

Yes, I understand the usecase!

Currently, FluentCRM supports only a single global opt-in email, and it is not possible to customize multiple opt-in emails for different lead magnets or automations. Additionally, when a contact is in the “Pending” status, even if they hit an automation through a link click, the double opt-in process requires them to confirm their subscription. Automation will send the DOI and there is no option in FluentCRM to change their status to “Subscribed” through automation too.

Thank you for understanding!

Hello @hudsontek,

Unfortunately, it’s not possible to change the contact status from “Pending” to “Subscribed” directly through an automation in FluentCRM.

Pending contacts are typically those who are in a “double opt-in” process, meaning they must confirm their subscription by clicking the confirmation link in the opt-in email. Only after confirming their subscription will they be marked as “Subscribed,” and only then will they be eligible to enter your automation.

So, to send any lead mangnet offers you need make those contacts subscribed in FluentCRM.

Thank you!

Hello @wtpleo,

Apologies for the delayed respnse. FluentCRM requires an email address to create a contact, as it uses email as a unique identifier. This is why submissions without an email field aren’t collected. Adding an email field should resolve the issue.

Let us know if you need further assistance!

Thank you!

Hello @grindingly,

To get the build, please open a support ticket through our official support portal, and our team will assist you by sharing the build version.

Thanks for staying with us!

Thank you, @altimac, for taking the time to leave such an amazing and positive review!

We’re delighted to hear that FluentCRM has met your needs and provided an excellent experience across multiple sites. Offering a self-hosted and comprehensive CRM solution is at the core of what we do, and it’s great to know you’re getting value from the Pro version.

We’re also thrilled that you’ve had a positive experience with our support team—customer satisfaction is our top priority. We look forward to continuing to support your success with FluentCRM!

Thanks again for being a valued member of the FluentCRM community, and we’re excited to be part of your journey!

Hello @markninnims,

Thank you for the update! It’s great to hear that the issue was resolved after trying a different version of FluentCRM and that Flywheel has also made changes on their end.

If further assistance is needed, feel free to reach out, and we’ll be happy to help!

Best Regards,

Hello @kutatishh and @markninnims,

Could you please confirm if this has resolved the problem on your end? If the issue persists, we recommend contacting Flywheel to clear the server-side cache again and see if that helps. Once you’ve done that, please let us know if the problem is resolved or further assistance is needed.

Best Regards,

Hello @dragonfly-ca,

Could you please confirm if this has resolved the problem on your end? If the issue persists, we recommend contacting Flywheel to clear the server-side cache again and see if that helps. Once you’ve done that, please let us know if the problem is resolved or further assistance is needed.

Best Regards,

Thank you so much for your kind words, @bemediaza!

We greatly appreciate your feedback and are glad to hear that you’re finding FluentCRM’s functionality to be useful. It’s also wonderful to know that our support team was able to assist you promptly and accurately when you needed help.

We’re always here to ensure you have the best solution and support experience possible.

Thanks again for being a part of the FluentCRM community!

Hello?@kutatishh ,

Thank you for your detailed response and for bringing this to our attention.

We would like to clarify that there is no security vulnerability in our code. The usage of the X-HTTP-Method-Override header is quite common and widely accepted in web applications and WordPress plugins that work with REST APIs. This issue appears to be specific to Flywheel, as none of our users on other servers are encountering it.

We recommend enabling the X-HTTP-Method-Override header specifically for your website at the server level and configuring a Web Application Firewall (WAF) to restrict access to the FluentCRM API endpoints. This approach will help maintain security while addressing Flywheel’s concerns.

Additionally, if possible, we suggest excluding the FluentCRM REST API routes from Flywheel’s caching layer to prevent any potential issues.

We appreciate you sharing Flywheel’s response. In the meantime, please consider opening a support ticket with us so we can continue the conversation and address this matter more directly.

Thank you again for your cooperation and understanding.

Hello @dragonfly-ca,

Thank you for your detailed response and for bringing this to our attention.

We would like to clarify that there is no security vulnerability in our code. The usage of the X-HTTP-Method-Override header is quite common and widely accepted in web applications and WordPress plugins that work with REST APIs. This issue appears to be specific to Flywheel, as none of our users on other servers are encountering it.

We recommend enabling the X-HTTP-Method-Override header specifically for your website at the server level and configuring a Web Application Firewall (WAF) to restrict access to the FluentCRM API endpoints. This approach will help maintain security while addressing Flywheel’s concerns.

Additionally, if possible, we suggest excluding the FluentCRM REST API routes from Flywheel’s caching layer to prevent any potential issues. The routes to consider are:

/wp-json/fluent-crm/v2/subscribers/ , /wp-json/fluent-crm/v2/lists/, /wp-json/fluent-crm/v2/tags/,/wp-json/fluent-crm/v2/campaigns/, /wp-json/fluent-crm/v2/custom-fields/contacts

We appreciate you sharing Flywheel’s response and their contact information. We will reach out to discuss this further.

In the meantime, please consider opening a support ticket with us so we can continue the conversation and address this matter more directly.

Thank you again for your cooperation and understanding.

• This reply was modified 6 months ago by Md. Ashikur Rahman.
• This reply was modified 6 months ago by Md. Ashikur Rahman.

Hello @markninnims and @kutatishh,

Thank you for the updates. It’s great to hear that you’ve both reached out to Flywheel support regarding the issue, and we’re hopeful that it will be resolved soon.

@kutatishh, regarding your question about submitting a support ticket: while Pro users have access to priority support, you’re still welcome to submit a ticket even if you’re using the free version of FluentCRM. We do our best to assist all users regardless of the version. Feel free to reach out through our official support portal, and we’ll continue there.

Best regards,