Remote control port 2241 issue

[K5YE]

Changing subject... this is not really a pulling qrz data issue as far as I can tell.
something is not working with remote control.

The main UI stops pulling data after the first JTalert call sign I click on. The UI works until I do that.
errors below..
--------
remote control is not working from jtalert after upgrade to 2.3
did some more testing.
if I start log4om 2.3. I can enter call signs many times and it looks up external data and displays.

as soon as I click on a call sign now in JTalert it populates the call sign... this error shows up in the log4om2 log below... then no more call signs will look up external data..

02:37:43.706 Info: [#=zjsHcIffwc7hV9JTtLtnJHtc=] : ##### REMOTE CONTROL UDP MESSAGE RECEIVED ##### :<CALLSIGN>VE1CNS on UDP port 2241 from 127.0.0.1:56889#####
02:37:43.729 Debug: [#=zjsHcIffwc7hV9JTtLtnJHtc=][MoveNext] : Remote control callsign lookup: VE1CNS
02:37:43.754 Debug: [Countries][SearchCallsign] : Performing Search Callsign on call VE1CNS on date 2/12/2020 2:37:43 AM
02:37:43.782 Debug: [Countries][SearchCallsign] : Country internal analisys for VE1CNS(VE1CNS - ) returned: FullCallsign: Not found Prefix: Not found Callsign: Canada
02:37:44.037 Debug: * [#=z3AMERkGaC3KlBwXW6Q==][MoveNext][10270 ms] : Loading Awards items from database for multiple award codes
02:37:44.06 Debug: [#=zjsHcIffwc7hV9JTtLtnJHtc=][MoveNext] : Error ConnectionReset An existing connection was forcibly closed by the remote host on UDP port 2241

all I did was upgrade from 2.2 to 2.3. appears something is breaking when a call sign is sent from jtalert. then all external data pull stops.

thanks,
Will

[NN7D]

Will,

I have not been able to replicate this issue with v2.3.0.0. Can you please submit/Generate a Support request, and include a debug level log. Also, please check your settings for integrating with JTAlert in the latest version of the User's Manual dated 11/2/2020. Things have changed and you must use the most recent User's Manual.

73,
Doug - W7DRM

[K5YE]

Well, that fixed it. I went back through the new manual and set everything in log4om, JTalert, and WSJT-x per the new manual and its all working again.
I guess the way I had it set worked in 2.2 then after the upgrade it did not like my settings.
Thanks for the help..

Will
K5YE