Dashboard: "Today's Pathes" window opens and immediately closes on first click | Mudfish VPN v6.5.5, Windows

Steps

  1. Open the dashboard
  2. In Item Configuration, open the item’s menu and click Today’s Pathes.
  3. The window opens, then closes a fraction of a second later. Clicking it again right away keeps it open.

It happens whenever the RTT data has changed since the window was last opened, so usually on the first try.

Cause
In the dashboard page, showTodaysPathes_graphql(item) opens the window from its mxios_post(...).then() callback:

$("#showTodaysPathesModal").modal('toggle');

mxios_post (mudfish_axios_post.fire_main() in js/mudfish_20260502.js) can call that callback twice: once with the cached response from /do/axios/cache/get, and again with the fresh /graphql response when /do/axios/cache/put doesn’t return 304. The todayPathes RTT values change often, so the cache is usually out of date and the callback runs twice. The first toggle opens the window and the second closes it. On the next click the cache is current, cache/put returns 304, the callback runs once, and the window stays open.

Fix
In showTodaysPathes_graphql(), change .modal('toggle') to .modal('show'). Bootstrap’s show returns early if the modal is already open, so the second callback just updates the table with the fresh data.

I could be wrong about this, it’s just what I could observe from my side. I’m able to fix it by utilizing a userscript via Tampermonkey on my side but would probably be best to be fixed with a client update.

Thank you for the detailed report and suggested fix! The code is consistent with your analysis: cached and fresh responses can run the callback twice, toggling the window open and then closed. Using .modal('show') looks appropriate; we’ll review this for a client update. For now, reopening Today’s Pathes after it closes is a temporary workaround. Thanks for investigating!

1 Like

No problem! You all rock!

@weongyo Just saw the latest client update contains the fix! That was so fast! Thank you so much! It had been annoying me for months; I didn’t expect to have such a fast turnaround on the fix though (that’s why I installed Tampermonkey, glad I can remove the extension now XD).

You’re all rockstars! :folded_hands:

You’re very welcome! We’re glad the update has addressed the issue. Thank you for investigating it and sharing such a detailed report and suggested fix—it helped us resolve it quickly. We really appreciate your kind words and support!