Winlink server not answering

37 views
Skip to first unread message

Greg

unread,
May 21, 2026, 11:21:19 AMMay 21
to DigiPi
I am running Digipi 2.0.1 with Digirig 1.11 and Digirig IC-2730 cable.  I used Audio to adjust the sound levels and I see it is at 62.

I have ferrites everywhere - radio power, antenna, pi powder, and digirig cables have ferrites.

My client winlink tries connecting, but the digipi never responds (no tx).

I ran APRS and webchat and can send receive messages.
--

I have tested with different radios (FT-65R, Anytone 878, baofeng, UV-Pro) and never get a winlink response.  APRS messaging works with these radios.

Also have reimaged the digipi and tried AIOC with the above radios and same result.

I have tested the digirig/cables/radio (IC-2730 and Baofeng cables/radio) with windows and they work as a winlink client as well as a rms packet gateway.

Please let me know what/where I should be looking at to solve the winlink email server issue.

Thank you

Scott Currie

unread,
May 21, 2026, 12:42:45 PMMay 21
to DigiPi
Not sure why it is not responding, but since you did not edit the configuration files manually, your Winlink Account is now corrupt and you are at risk of having the account removed:

Screenshot 2026-05-21 092939.png 
You need to update/correct the information in the following files in DigiPi to correct your account, or it will likely be locked out:
/etc/rmsgw/sysop.xml
/etc/rmsgw/channels.xml
Optionally:
/etc/rmsgw/banner

Craig-
Please FIX THIS! The Winlink Development Team does NOT ALLOW false information in the database records. DigiPi stuffs invalid account information into the Winlink record, this is a violation of the API terms, which further runs the risk of RMS Gateway being revoked. You MUST capture this information during initialize and update the gateway files, or prevent the gateway from starting if the files have not been updated.

-Scott, NS7C
WDT

Greg

unread,
May 21, 2026, 7:42:20 PMMay 21
to DigiPi
Thanks for the information Scott.  I have edited the files and restarted so it should have pushed correct information.
Reply all
Reply to author
Forward
0 new messages