We've been hitting a wall with Mend's Jira integration for our on-prem Jira instance. The automated ticket creation just fails silently. Our logs show connection timeouts from the Mend side, even though our firewall rules are correct and the Jira API is accessible.
Has anyone else running an on-prem Jira setup gotten this to work reliably? We're stuck manually creating tickets for critical vulnerabilities, which defeats the purpose. Looking for any config tips or if we need to open specific ports beyond the standard API. Our security team is asking for a timeline and I have no good answers.
Always optimizing.
Classic. Timeouts on their side but you're checking your firewall? Mend's agent probably can't handle the latency or network hops to your data center. Their cloud-first design assumes everything's a public API endpoint.
Have you tried running a packet capture during the failure window? I bet you'll see the TCP handshake starts but their side gives up before your Jira even responds. That's a Mend timeout setting, not your ports.
Your security team asking for a timeline is the real problem. You can't give one because Mend treats on-prem as a legacy edge case. You're waiting on their engineering to maybe adjust timeouts, which is low priority. Start the procurement process for a replacement now.
Show me the logs.
You're looking at the wrong layer. If your Jira API is accessible and firewall rules are clean, the timeout is likely an application-level setting in Mend's integration agent. Their cloud service has hard-coded thresholds that don't account for on-prem network latency.
You won't fix this with port configurations. You need to open a ticket with Mend support and explicitly demand they review and increase the timeout and retry settings for their on-prem connector. Cite the specific error from your logs.
Don't let your security team's timeline pressure you into a wild goose chase. The answer is in Mend's court, and their SLA for on-prem support is probably abysmal. Start documenting the downtime for your vendor review.
Trust but verify — especially the fine print.
Welcome to the club of hoping an on-prem setup will be treated as a first-class citizen by a SaaS vendor. It rarely works out that way.
You're asking for config tips, but the real issue is expecting a cloud service's agent to handle your internal network's quirks. Their timeout is likely measured in milliseconds, and your on-prem latency is measured in coffee breaks. Even if you open every port, the agent will still bail before your Jira instance finishes its morning stretch.
Your security team wants a timeline? Give them the classic vendor two-step: open a high-priority support ticket, wait weeks for them to acknowledge it's a known issue, then watch it sit in their backlog while they build another feature for cloud customers.
Show me the data