Export to JMX Failing – BlazeMeter Converter Service Returning Whitelabel Error Page

1 view
Skip to first unread message

Kusum Gairola

unread,
Nov 20, 2025, 7:07:03 AM (4 days ago) Nov 20
to BlazeMeter Forum

Hello BlazeMeter Support Team,

I am facing an issue with the BlazeMeter Chrome Extension where the “Export to JMX” feature has stopped working. This was functioning normally yesterday, but starting today the export consistently fails.

To isolate the problem, I tested the converter endpoint directly:

URL tested:
https://converter.blazemeter.com

Instead of returning the expected health/JSON response, the service returns a Whitelabel Error Page (Spring Boot fallback):

  • Error Type: Not Found

  • Status: 404

  • Timestamp: (same as in displayed page)

  • Behavior: This error appears on every network: corporate network, VPN disabled, mobile hotspot, home Wi-Fi.

  • Conclusion: The issue appears to be on the BlazeMeter converter backend, not the client side.

I have attached a screenshot of the actual response from your converter service for your reference.

Troubleshooting steps already performed:

  • Cleared browser cache and reinstalled the BlazeMeter Chrome Extension

  • Logged out and logged back into BlazeMeter

  • Tested on different networks (VPN off, corporate network, mobile hotspot)

  • Verified DNS and proxy settings

  • Tried with and without corporate firewall

  • Tested from a different device

  • Accessed the converter URL on each network — same result

  • Chrome extension still fails to export to JMX

Since this behavior now appears consistently across devices and networks, it strongly suggests an outage or misconfiguration on the BlazeMeter Converter Service (converter.blazemeter.com).

Could you please investigate and let me know the current status of the converter backend and any ETA for resolution?

This is currently blocking our ability to export JMX files from recorded scripts, so your assistance is greatly appreciated.

Dmitri T

unread,
Nov 20, 2025, 1:57:30 PM (4 days ago) Nov 20
to BlazeMeter Forum
I cannot reproduce your issue either with https://converter.blazemeter.com/ or with Chrome Extension. May I ask you to repeat the test with browser developer tools enabled and inspect console and network tabs? 

Maybe it worth reaching out to BlazeMeter Support 
Reply all
Reply to author
Forward
0 new messages