Hi, Phil.
Good to know that the SSL servers are coming back.
The problem you are having has nothing to do with SSL; you'd have the same problem with a passcode APRS-IS port. The issue is that the 'm' filter you are using tells the APRS-IS server to send packets for all stations within a certain radius of your beaconed position. However, your beacon is turned off, so the APRS-IS server will never _know_ your position to compute that radius circle and select those packets.
I've had several other people complain about this operator-error issue ("how come I'm not receiving any packets from the APRS-IS?"), so I recently added a check to YAAC to confirm that you are configured to send a beacon before you are allowed to use only an 'm' filter expression. If you don't want to beacon, I recommend using an 'r' filter expression (i.e., r/lat/lon/radius ) with your approximate decimal (N or E oriented) latitude and longitude.
Hope this helps.
Andrew, KA2DDO
author of YAAC
________________________________________
From: Phil Pacier - AD6NH <ad6nh@...>
Sent: Tuesday, January 28, 2020 12:51 PM
To: ka2ddo@...
Subject: YAAC SSL
Good day, Andrew! I hope you are doing well. We have revitalized the SSL connection to the Tier2 servers, and currently have two servers accepting connections on port 24580. The ssl.aprs2.net address has those two servers and it works fine now.
I have been trying to setup an SSL connection from YAAC but I am having difficulty. I requested an up-to-date key from ARRL and verified that it works with APRSDroid. Here are two screen shots, one of the settings, and one of the error message I get in YAAC:
[cid:part1.135C4A34.ECDA3791@...]
[cid:part2.22FBEF9B.EDC0FFE0@...]
Thank you for your assistance!
--
--
73 de Phil Pacier, AD6NH
APRS Tier2 Network Coordinator
D-Star Administrator: W6HRO & REF070
