Re: Running in TH-D74 - no problems
Wait, USB?? I read somewhere that KISS didn't work over USB, only
Bluetooth.
Thanks, looking forward to seeing what cable you're using.? Once the
radio's TNC looks like a serial port, the rest should be easy.
Greg? KO6TH
Frank Koppe wrote:
toggle quoted message
Show quoted text
Hi Greg,
I connect the pi via USB . Not all USB-cables
work.
Then define the com port, ?i.e. ?/dev/ttyAMC0
1200bd, 8n1,....
Tomorrow i can send a document with all steps.
Hi Frank,
What is the secret to get the Pi-4B to talk to the D74
(presumably over Bluetooth)?? I tried, but seem to be
missing some protocol library.
Greg? KO6TH
Frank Koppe wrote:
YAAC
has been running on my Raspberry pi4 for several
days.? CPU utilization approx. 15% and 400MB RAM are
used.? Hardware: TH-D74 in kiss mode and weather
station, local weewx is also running.? Thanks for
the software - super job.
|
Re: Running in TH-D74 - no problems
Hi Greg, I connect the pi via USB . Not all USB-cables work.
Then define the com port, ?i.e. ?/dev/ttyAMC0 1200bd, 8n1,....
Tomorrow i can send a document with all steps.
Hi Frank,
What is the secret to get the Pi-4B to talk to the D74 (presumably
over Bluetooth)?? I tried, but seem to be missing some protocol
library.
Greg? KO6TH
Frank Koppe wrote:
YAAC has been
running on my Raspberry pi4 for several days.? CPU utilization
approx. 15% and 400MB RAM are used.? Hardware: TH-D74 in kiss
mode and weather station, local weewx is also running.? Thanks
for the software - super job.
|
Re: Running in TH-D74 - no problems
Hi Frank,
What is the secret to get the Pi-4B to talk to the D74 (presumably
over Bluetooth)?? I tried, but seem to be missing some protocol
library.
Greg? KO6TH
Frank Koppe wrote:
toggle quoted message
Show quoted text
YAAC has been
running on my Raspberry pi4 for several days.? CPU utilization
approx. 15% and 400MB RAM are used.? Hardware: TH-D74 in kiss
mode and weather station, local weewx is also running.? Thanks
for the software - super job.
|
Running in TH-D74 - no problems
YAAC has been running on my Raspberry pi4 for several days.? CPU utilization approx. 15% and 400MB RAM are used.? Hardware: TH-D74 in kiss mode and weather station, local weewx is also running.? Thanks for the software - super job.
|
Andrew
I would like to Thank You for all the great work you have done to produce a fantastic program. Having done some programming and writing of documents it is amazing how few problems you have had since I have been involved with YAAC. When you are writing software for pay it is one thing but when you do it as a hobby and it bites you it really must sting and suck at the same time. Again Thank You for a GREAT job and program!
-- Thank You and God Bless? Richard
Richard Beggs? ? ? ? ? ? N0EB? ? ? 449.975 1220 H Street Salida, Co. 81201 ?Cell 719-239-1788 LL 719-539-5435?
**
|
How to write a good bug report for YAAC
Greetings.
I appreciate all of you using my program YAAC, and sympathize that you occasionally find problems with it. To make life easier and smoother for all of us, here's how to help me help you with your problems:
1. Always tell me what version of YAAC you are using. There are way too many antique versions of YAAC on websites I have no control over; the only official sites are and . Also, since (unlike many other software vendors) I don't _force_ you to use the latest version, you could be running some old version where I have made incompatible changes in the newer code, map data, or plugins. So please report the version. It can be obtained from the title bar of the map window, the Help->About dialog box, or from the command line using the command
java -jar YAAC.jar -version:all
2. Always tell me what operating system and version thereof you are using. Windowed user interfaces behave totally differently on XWindows on a Linux distro compared to Microsoft Windows or Apple Macintosh OS X, and even between different releases of the same operating system (such as Microsoft Windows 7 versus Windows 11). So tell me the O/S name (and distro for Linux) and version.
3. Always tell me what version of the Java runtime you are using. I've had to drop support for older versions of Java because some of the third-party libraries YAAC is built on are compiled with newer Java versions, and using even newer versions of the Java runtime can introduce problems because of deprecation of older functionality. Java 8 (the common baseline before Java started changing regularly, and the version YAAC is built with) is now 10 (!) releases behind the latest Java release. YAAC is supposed to detect if you are using an obsolete (from YAAC's point of view) version of the Java runtime, but a bug has been found in recent versions of YAAC where it doesn't correctly and clearly report the error of using obsolete Java runtime at startup time, such that you may get the error later at an unexpected time.
4. Tell me _exactly_ what you were doing to get the problem to occur. If you can't tell me how to cause the problem myself, I won't be able to confirm my fix actually solves the problem.
5. Tell me _exactly_ what the error message is that you are getting. I went to considerable effort to ensure YAAC writes out definitive error messages that make it clear what happened and where in the code it happened (which is why errors that aren't user errors commonly appear as stack traces indicating exactly how YAAC got to the line of code where the problem occurred). Saying "I got an error" and not telling me what specific error it was is like telling a doctor "I don't feel good" and refusing to provide symptoms or answer the doctor's questions. And don't edit down the error message; if you knew that only one part of the message was significant, you could probably fix the problem yourself.
To help you with this, YAAC keeps a debugging log file called YAAC.out in your YAAC log files directory. This log file is independent of the APRS packet log files provided for regulatory logging. Instead, it traces what major operations you were performing in YAAC, and records all those ugly stack trace error messages. It also reports all those software version numbers each time you start YAAC. However, if you are going to send me the YAAC.out file (which is really appreciated), copy it right after the problem occurs. To keep from filling up your disk drive, YAAC only keeps the last 128Kb of data in the YAAC.out file, so if too many error messages are occurring, the "first cause" error message might have overflowed out of the file if you wait too long to copy it into an email or bug report. Note this log file generally does not send any personal information about you to me; the most personal data might be the locale your computer is configured to use, such as [for example] American English versus Swiss German, or specific invalid packets you received from someone else. The log file is plain text, so you can read it yourself if you are concerned about privacy issues. P.S. Don't paste the error messages into Microsoft Word or a similar word processing program; these programs will commonly "fix" the text to use the "correct" punctuation marks (according to the word processor's opinion), which can tend to destroy debugging information. Just send the YAAC.out file as-is.
Remember, I'm not lurking behind you watching over your shoulder as you use YAAC, so I don't know what you did to cause a problem to occur. Tell me, so I can help you get it fixed.
Andrew, KA2DDO
author of YAAC
|
Hello Andy,
Here are the error messages that you asked for.
See the attachments. I had to breakup the error message into two parts.
Thank you for your time and patience.
Sincerely,
Ernest Bazzinotti, KC1LKB
On Tuesday, February 22, 2022, 07:25:53 PM EST, Andrew P. <andrewemt@...> wrote:
Ah, do you think you could tell me exactly what that long Java error message is? :-) Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] < [email protected]> on behalf of Ernest Bazzinotti via groups.io <ebazz= [email protected]> Sent: Tuesday, February 22, 2022 7:12 PM Hello, I'm running the latest edition of YAAC. When go to configure a new port I never get to the config menu. I do get this long Java error message. I'm trying to configure Kiss over TCP. I have configured this setup before with no problem. When the server went down the other day that's when my troubles started. I am running YAAC with Direwolf. I do have Direwolf configured with the 8000 / 8001 ports enabled. Any ideas as to how I can fix this? Thank you in advance. Sincerely, Ernest Bazzinotti KC1LKB ebazz@...
|
Ah, do you think you could tell me exactly what that long Java error message is? :-) Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] < [email protected]> on behalf of Ernest Bazzinotti via groups.io <ebazz@...> Sent: Tuesday, February 22, 2022 7:12 PM Hello, I'm running the latest edition of YAAC. When go to configure a new port I never get to the config menu. I do get this long Java error message. I'm trying to configure Kiss over TCP. I have configured this setup before with no problem. When the server went down the other day that's when my troubles started. I am running YAAC with Direwolf. I do have Direwolf configured with the 8000 / 8001 ports enabled. Any ideas as to how I can fix this? Thank you in advance. Sincerely, Ernest Bazzinotti KC1LKB ebazz@...
|
Hello,
I'm running the latest edition of YAAC. When go to configure a new port I never get to the config menu.
I do get this long Java error message. I'm trying to configure Kiss over TCP.
I have configured this setup before with no problem. When the server went down the other day that's when my troubles started.
I am running YAAC with Direwolf. I do have Direwolf configured with the 8000 / 8001 ports enabled.
Any ideas as to how I can fix this? Thank you in advance.
Sincerely,
Ernest Bazzinotti KC1LKB
ebazz@...
|
Good from this side of the pond as well.?
Greg? KO6TH
Dave_G0WBX via groups.io wrote:
toggle quoted message
Show quoted text
Hi Andy.
ka2ddo.org is working now, ending up on your https site
home page.
Doing this via a VPN endpoint in London UK.? (The machine in
front of me is on my desk, not in London.)
73.
Dave G8KBV.
--
Created on and sent from a Unix like PC running and using free and open source software:
|
Hi Andy.
ka2ddo.org is working now, ending up on your https site
home page.
Doing this via a VPN endpoint in London UK.? (The machine in
front of me is on my desk, not in London.)
73.
Dave G8KBV.
--
Created on and sent from a Unix like PC running and using free and open source software:
|
OK, I just pushed the re-signed DNS zones for ka2ddo.org with a 3-month (plus 2 days) expiration period. And I'm putting in my calendar an event in 3-months minus 2 days to re-sign the zones again.
Within 24 hours, everyone should have the new-and-improved RRSIG records for ka2ddo.org, and life can go back to normal.
Andrew, KA2DDO
author of YAAC
toggle quoted message
Show quoted text
From: [email protected] on behalf of Kevin Ratcliff (KB9MQU) via groups.io
Sent: Sunday, February 20, 2022 5:03 PM
To: [email protected]
Subject: Re: [yaac-users] YAAC
The issue appears to be DNS, or more specifically DNSSEC on the ka2ddo.org domain. This would explain why it works for some and not others. Not all DNS revolvers support DNSSEC.
With DNSSEC disabled, ka2ddo.org resolves fine.
With DNSSEC enabled, ka2ddo.org doesn't resolve in DNS.
Andrew, I would suggest you verify the DNSSEC settings with your domain registrar and DNS provider to make sure everything matches up.
See also this site for troubleshooting:
Hope that information is helpful.
Kevin
KB9MQU
------- Original Message -------
On Sunday, February 20th, 2022 at 15:24, Andrew P. <andrewemt@...> wrote:
> OK, this is getting strange. I know I renewed my domain name and installed my new SSL certificate for the site. And (rather than use my house network where the server is connected), I used my AT&T mobile hotspot on a laptop to get Internet access, and over
that path I was able to see my website.
>
> So, something on the path of every user having difficulty accessing the site must be either:
>
> 1. not looking up the domain name correctly
>
> 2. caching the expired certificate so as to say the site isn't trusted.
>
> I did find it amusing to notice, during the 5 days the expired certificate was still in use, the only users who still successfully accessed my website were webcrawlers and attackers. Apparently both disable failing an SSL connection just because the server
certificate is expired.
>
> So here are the checks I'd like everyone who is having difficulties to do:
>
> 1. Try to look up my domain name with the nslookup command on your local computer. From a shell, DOS prompt, or Terminal window (depending on your O/S), enter the command
>
> nslookup .
>
> You should get an answer back of 71.162.157.26. If you don't, then someone is caching a negative lookup (because somehow the auto-renewal of my domain name was turned off, so there may have been a few hours when my domain name wasn't in service, although
there shouldn't have been).
>
> 2. Try browsing the URL
>
> This should get you to my website without using DNS or SSL. If that works, then there is caching of the bad certificate lookup that needs to be cleared. You should clear your browser cache and try the normal URL
again. If that fails, then you are using a proxy between you and the rest of the Internet that is caching the expired certificate lookup failure, rather than going to my webserver and trying again. Note that these proxies can be inserted
without your consent or knowledge; the most common sort is on a hotel's Wifi, to ensure you are a paying guest before being allowed to use their Internet service.
>
> Let me know what you find out with these tests.
>
> Also, if you are getting the failure within YAAC, shut down YAAC completely and restart it. The Java runtime has a cache, too, but the cache will be discarded when you stop the Java runtime.
>
> Hope this helps.
>
> Andrew, KA2DDO
>
> author of YAAC and webmaster of
>
> ________________________________________
>
> From: [email protected] [email protected] on behalf of Bob Evans bob9750@...
>
> Sent: Sunday, February 20, 2022 2:51 PM
>
> To: [email protected]
>
> Subject: Re: [yaac-users] YAAC
>
> Hi
>
> Just done a fresh install of YAAC on a new Ubuntu system and getting java error 'unable to receive files from server
......etc'
>
> Also can't access ka2ddo homepage from other systems with 'site can't be reached' error
>
> Bob
>
> On Sat, Feb 19, 2022 at 7:18 PM Andrew P. <andrewemt@...:andrewemt@...> wrote:
>
> Looks like you typed Kilo Alpha 2 Delta Delta Zero instead of Oscar. :-)
>
> The site is up; I checked from at least 3 places. However, if your browser or proxy server is caching the stale certificate, you might need to do a Shift-refresh of the page.
>
> Andrew, KA2DDO
>
> ________________________________________
>
> From: yaac-users@...: [email protected] <yaac-users@...: [email protected]> on behalf of Richard Beggs <richard.n0eb@...:richard.n0eb@...>
>
> Sent: Saturday, February 19, 2022 7:07 PM
>
> To: Andrew Pavlin
>
> Subject: [yaac-users] YAAC
>
> Still can not reach ka2dd0.orghttp://ka2dd0.orghttp://ka2dd0.org?
>
> --
>
> Thank You and God Bless []
>
> Richard
>
>
|
Thank you for finding this problem. The directions I followed for setting up DNSSEC didn't mention how short the default expiration period would be. So, I need to re-sign my DNS data with a newer start date and a longer expiration time (since I don't routinely
change the DNS for my domains). Hopefully, I'll have this resolved by tomorrow.
Andrew, KA2DDO
toggle quoted message
Show quoted text
From: [email protected] on behalf of Kevin Ratcliff (KB9MQU) via groups.io
Sent: Sunday, February 20, 2022 5:03 PM
To: [email protected]
Subject: Re: [yaac-users] YAAC
The issue appears to be DNS, or more specifically DNSSEC on the ka2ddo.org domain. This would explain why it works for some and not others. Not all DNS revolvers support DNSSEC.
With DNSSEC disabled, ka2ddo.org resolves fine.
With DNSSEC enabled, ka2ddo.org doesn't resolve in DNS.
Andrew, I would suggest you verify the DNSSEC settings with your domain registrar and DNS provider to make sure everything matches up.
See also this site for troubleshooting:
Hope that information is helpful.
Kevin
KB9MQU
------- Original Message -------
On Sunday, February 20th, 2022 at 15:24, Andrew P. <andrewemt@...> wrote:
> OK, this is getting strange. I know I renewed my domain name and installed my new SSL certificate for the site. And (rather than use my house network where the server is connected), I used my AT&T mobile hotspot on a laptop to get Internet access, and over
that path I was able to see my website.
>
> So, something on the path of every user having difficulty accessing the site must be either:
>
> 1. not looking up the domain name correctly
>
> 2. caching the expired certificate so as to say the site isn't trusted.
>
> I did find it amusing to notice, during the 5 days the expired certificate was still in use, the only users who still successfully accessed my website were webcrawlers and attackers. Apparently both disable failing an SSL connection just because the server
certificate is expired.
>
> So here are the checks I'd like everyone who is having difficulties to do:
>
> 1. Try to look up my domain name with the nslookup command on your local computer. From a shell, DOS prompt, or Terminal window (depending on your O/S), enter the command
>
> nslookup .
>
> You should get an answer back of 71.162.157.26. If you don't, then someone is caching a negative lookup (because somehow the auto-renewal of my domain name was turned off, so there may have been a few hours when my domain name wasn't in service, although
there shouldn't have been).
>
> 2. Try browsing the URL
>
> This should get you to my website without using DNS or SSL. If that works, then there is caching of the bad certificate lookup that needs to be cleared. You should clear your browser cache and try the normal URL
again. If that fails, then you are using a proxy between you and the rest of the Internet that is caching the expired certificate lookup failure, rather than going to my webserver and trying again. Note that these proxies can be inserted
without your consent or knowledge; the most common sort is on a hotel's Wifi, to ensure you are a paying guest before being allowed to use their Internet service.
>
> Let me know what you find out with these tests.
>
> Also, if you are getting the failure within YAAC, shut down YAAC completely and restart it. The Java runtime has a cache, too, but the cache will be discarded when you stop the Java runtime.
>
> Hope this helps.
>
> Andrew, KA2DDO
>
> author of YAAC and webmaster of
>
> ________________________________________
>
> From: [email protected] [email protected] on behalf of Bob Evans bob9750@...
>
> Sent: Sunday, February 20, 2022 2:51 PM
>
> To: [email protected]
>
> Subject: Re: [yaac-users] YAAC
>
> Hi
>
> Just done a fresh install of YAAC on a new Ubuntu system and getting java error 'unable to receive files from server
......etc'
>
> Also can't access ka2ddo homepage from other systems with 'site can't be reached' error
>
> Bob
>
> On Sat, Feb 19, 2022 at 7:18 PM Andrew P. <andrewemt@...:andrewemt@...> wrote:
>
> Looks like you typed Kilo Alpha 2 Delta Delta Zero instead of Oscar. :-)
>
> The site is up; I checked from at least 3 places. However, if your browser or proxy server is caching the stale certificate, you might need to do a Shift-refresh of the page.
>
> Andrew, KA2DDO
>
> ________________________________________
>
> From: yaac-users@...: [email protected] <yaac-users@...: [email protected]> on behalf of Richard Beggs <richard.n0eb@...:richard.n0eb@...>
>
> Sent: Saturday, February 19, 2022 7:07 PM
>
> To: Andrew Pavlin
>
> Subject: [yaac-users] YAAC
>
> Still can not reach ka2dd0.orghttp://ka2dd0.orghttp://ka2dd0.org?
>
> --
>
> Thank You and God Bless []
>
> Richard
>
>
|
The issue appears to be DNS, or more specifically DNSSEC on the ka2ddo.org domain. This would explain why it works for some and not others. Not all DNS revolvers support DNSSEC.
With DNSSEC disabled, ka2ddo.org resolves fine.
With DNSSEC enabled, ka2ddo.org doesn't resolve in DNS.
Andrew, I would suggest you verify the DNSSEC settings with your domain registrar and DNS provider to make sure everything matches up.
See also this site for troubleshooting:
Hope that information is helpful.
Kevin
KB9MQU
toggle quoted message
Show quoted text
------- Original Message ------- On Sunday, February 20th, 2022 at 15:24, Andrew P. <andrewemt@...> wrote: OK, this is getting strange. I know I renewed my domain name and installed my new SSL certificate for the site. And (rather than use my house network where the server is connected), I used my AT&T mobile hotspot on a laptop to get Internet access, and over that path I was able to see my website.
So, something on the path of every user having difficulty accessing the site must be either:
1. not looking up the domain name correctly
2. caching the expired certificate so as to say the site isn't trusted.
I did find it amusing to notice, during the 5 days the expired certificate was still in use, the only users who still successfully accessed my website were webcrawlers and attackers. Apparently both disable failing an SSL connection just because the server certificate is expired.
So here are the checks I'd like everyone who is having difficulties to do:
1. Try to look up my domain name with the nslookup command on your local computer. From a shell, DOS prompt, or Terminal window (depending on your O/S), enter the command
nslookup www.ka2ddo.org.
You should get an answer back of 71.162.157.26. If you don't, then someone is caching a negative lookup (because somehow the auto-renewal of my domain name was turned off, so there may have been a few hours when my domain name wasn't in service, although there shouldn't have been).
2. Try browsing the URL
This should get you to my website without using DNS or SSL. If that works, then there is caching of the bad certificate lookup that needs to be cleared. You should clear your browser cache and try the normal URL again. If that fails, then you are using a proxy between you and the rest of the Internet that is caching the expired certificate lookup failure, rather than going to my webserver and trying again. Note that these proxies can be inserted without your consent or knowledge; the most common sort is on a hotel's Wifi, to ensure you are a paying guest before being allowed to use their Internet service.
Let me know what you find out with these tests.
Also, if you are getting the failure within YAAC, shut down YAAC completely and restart it. The Java runtime has a cache, too, but the cache will be discarded when you stop the Java runtime.
Hope this helps.
Andrew, KA2DDO
author of YAAC and webmaster of
________________________________________
From: [email protected] [email protected] on behalf of Bob Evans bob9750@...
Sent: Sunday, February 20, 2022 2:51 PM
To: [email protected]
Subject: Re: [yaac-users] YAAC
Hi
Just done a fresh install of YAAC on a new Ubuntu system and getting java error 'unable to receive files from server ......etc'
Also can't access ka2ddo homepage from other systems with 'site can't be reached' error
Bob
On Sat, Feb 19, 2022 at 7:18 PM Andrew P. <andrewemt@...:andrewemt@...> wrote:
Looks like you typed Kilo Alpha 2 Delta Delta Zero instead of Oscar. :-)
The site is up; I checked from at least 3 places. However, if your browser or proxy server is caching the stale certificate, you might need to do a Shift-refresh of the page.
Andrew, KA2DDO
________________________________________
From: yaac-users@...:[email protected] <yaac-users@...:[email protected]> on behalf of Richard Beggs <richard.n0eb@...:richard.n0eb@...>
Sent: Saturday, February 19, 2022 7:07 PM
To: Andrew Pavlin
Subject: [yaac-users] YAAC
Still can not reach ka2dd0.org
--
Thank You and God Bless []
Richard
|
Andrew,
I think the long TTL of 1 day for your A record might be the issue.
When I lookup the authoritative NS records for your domain I get 204.69.234.1 and 204.74.101.1.
Both of those resolve your domain correctly:
masen@mf-mbp12-wifi ~ % dig @204.69.234.1 www.ka2ddo.org
; <<>> DiG 9.10.6 <<>> @204.69.234.1 www.ka2ddo.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17950
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.ka2ddo.org.??? ??? ??? IN??? A
;; ANSWER SECTION:
www.ka2ddo.org.??? ??? 86400??? IN??? A??? 71.162.157.26
;; AUTHORITY SECTION:
ka2ddo.org.??? ??? 86400??? IN??? NS??? udns1.ultradns.net.
ka2ddo.org.??? ??? 86400??? IN??? NS??? udns2.ultradns.net.
;; Query time: 46 msec
;; SERVER: 204.69.234.1#53(204.69.234.1)
;; WHEN: Sun Feb 20 15:35:12 PST 2022
;; MSG SIZE? rcvd: 111
However, google, cloudflare, and comcast haven't picked up the change...
dig @75.75.75.75
dig @8.8.8.8 www.ka2ddo.org
dig @1.1.1.1 www.ka2ddo.org
None of these return an answer...yet.
I suspect this will work itself out at-most in the next day, as everything propagates out.
If you expect the A record needs to change semi regularly, you might publish a shorter TTL to avoid downtime. I don't see a huge downside in a TTL of 3600 for example.
-Masen, KF7HVM
Excellent software BTW!
|
Hello,
I still can't reach your web site. YAAC can't reach it either. I ran the check from a dos prompt and didn't get the correct answer that you talk about. I did get in with the web address that you supplied in the e-mail, however the web site doesn't looking anything like it supposed to.
Hope this helps.
Sincerely,
Ernest Bazzinotti, KC1LKB
On Sunday, February 20, 2022, 06:21:18 PM EST, Matt Reynolds <nedheadd@...> wrote:
nslookup tells me that www.k2ddo.org is a non-existant domain.
:(
73
Matt Reynolds (KD0PYK)
On 2/20/2022 1:24 PM, Andrew P. wrote: > OK, this is getting strange. I know I renewed my domain name and installed my new SSL certificate for the site. And (rather than use my house network where the server is connected), I used my AT&T mobile hotspot on a laptop to get Internet access, and over that path I was able to see my website. > > So, something on the path of every user having difficulty accessing the site must be either: > 1. not looking up the domain name correctly > 2. caching the expired certificate so as to say the site isn't trusted. > > I did find it amusing to notice, during the 5 days the expired certificate was still in use, the only users who still successfully accessed my website were webcrawlers and attackers. Apparently both disable failing an SSL connection just because the server certificate is expired. > > So here are the checks I'd like everyone who is having difficulties to do: > > 1. Try to look up my domain name with the nslookup command on your local computer. From a shell, DOS prompt, or Terminal window (depending on your O/S), enter the command > > nslookup www.ka2ddo.org. > > You should get an answer back of 71.162.157.26. If you don't, then someone is caching a negative lookup (because somehow the auto-renewal of my domain name was turned off, so there may have been a few hours when my domain name wasn't in service, although there shouldn't have been). > > 2. Try browsing the URL > > This should get you to my website without using DNS or SSL. If that works, then there is caching of the bad certificate lookup that needs to be cleared. You should clear your browser cache and try the normal URL again. If that fails, then you are using a proxy between you and the rest of the Internet that is caching the expired certificate lookup failure, rather than going to my webserver and trying again. Note that these proxies can be inserted without your consent or knowledge; the most common sort is on a hotel's Wifi, to ensure you are a paying guest before being allowed to use their Internet service. > > Let me know what you find out with these tests. > > Also, if you are getting the failure within YAAC, shut down YAAC completely and restart it. The Java runtime has a cache, too, but the cache will be discarded when you stop the Java runtime. > > Hope this helps. > > Andrew, KA2DDO > author of YAAC and webmaster of > > ________________________________________ > From: [email protected] < [email protected]> on behalf of Bob Evans < bob9750@...> > Sent: Sunday, February 20, 2022 2:51 PM > To: [email protected]> Subject: Re: [yaac-users] YAAC > > Hi > > Just done a fresh install of YAAC on a new Ubuntu system and getting java error 'unable to receive files from server ......etc' > > Also can't access ka2ddo homepage from other systems with 'site can't be reached' error > > Bob > > > > On Sat, Feb 19, 2022 at 7:18 PM Andrew P. < andrewemt@...<mailto: andrewemt@...>> wrote: > Looks like you typed Kilo Alpha 2 Delta Delta Zero? instead of Oscar. :-) > > The site is up; I checked from at least 3 places. However, if your browser or proxy server is caching the stale certificate, you might need to do a Shift-refresh of the page. > > Andrew, KA2DDO > > ________________________________________ > From: [email protected]<mailto: [email protected]> < [email protected]<mailto: [email protected]>> on behalf of Richard Beggs < richard.n0eb@...<mailto: richard.n0eb@...>> > Sent: Saturday, February 19, 2022 7:07 PM > To: Andrew Pavlin > Subject: [yaac-users] YAAC > > Still can not reach ka2dd0.org<><>? > > -- > Thank You and God Bless [] > Richard > > > > > > > > > >
|
nslookup tells me that www.k2ddo.org is a non-existant domain.
:(
73
Matt Reynolds (KD0PYK)
toggle quoted message
Show quoted text
On 2/20/2022 1:24 PM, Andrew P. wrote: OK, this is getting strange. I know I renewed my domain name and installed my new SSL certificate for the site. And (rather than use my house network where the server is connected), I used my AT&T mobile hotspot on a laptop to get Internet access, and over that path I was able to see my website.
So, something on the path of every user having difficulty accessing the site must be either:
1. not looking up the domain name correctly
2. caching the expired certificate so as to say the site isn't trusted.
I did find it amusing to notice, during the 5 days the expired certificate was still in use, the only users who still successfully accessed my website were webcrawlers and attackers. Apparently both disable failing an SSL connection just because the server certificate is expired.
So here are the checks I'd like everyone who is having difficulties to do:
1. Try to look up my domain name with the nslookup command on your local computer. From a shell, DOS prompt, or Terminal window (depending on your O/S), enter the command
nslookup www.ka2ddo.org.
You should get an answer back of 71.162.157.26. If you don't, then someone is caching a negative lookup (because somehow the auto-renewal of my domain name was turned off, so there may have been a few hours when my domain name wasn't in service, although there shouldn't have been).
2. Try browsing the URL
This should get you to my website without using DNS or SSL. If that works, then there is caching of the bad certificate lookup that needs to be cleared. You should clear your browser cache and try the normal URL again. If that fails, then you are using a proxy between you and the rest of the Internet that is caching the expired certificate lookup failure, rather than going to my webserver and trying again. Note that these proxies can be inserted without your consent or knowledge; the most common sort is on a hotel's Wifi, to ensure you are a paying guest before being allowed to use their Internet service.
Let me know what you find out with these tests.
Also, if you are getting the failure within YAAC, shut down YAAC completely and restart it. The Java runtime has a cache, too, but the cache will be discarded when you stop the Java runtime.
Hope this helps.
Andrew, KA2DDO
author of YAAC and webmaster of
________________________________________
From: [email protected] <[email protected]> on behalf of Bob Evans <bob9750@...>
Sent: Sunday, February 20, 2022 2:51 PM
To: [email protected]
Subject: Re: [yaac-users] YAAC
Hi
Just done a fresh install of YAAC on a new Ubuntu system and getting java error 'unable to receive files from server ......etc'
Also can't access ka2ddo homepage from other systems with 'site can't be reached' error
Bob
On Sat, Feb 19, 2022 at 7:18 PM Andrew P. <andrewemt@...<mailto:andrewemt@...>> wrote:
Looks like you typed Kilo Alpha 2 Delta Delta Zero instead of Oscar. :-)
The site is up; I checked from at least 3 places. However, if your browser or proxy server is caching the stale certificate, you might need to do a Shift-refresh of the page.
Andrew, KA2DDO
________________________________________
From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Richard Beggs <richard.n0eb@...<mailto:richard.n0eb@...>>
Sent: Saturday, February 19, 2022 7:07 PM
To: Andrew Pavlin
Subject: [yaac-users] YAAC
Still can not reach ka2dd0.org<><>?
--
Thank You and God Bless []
Richard
|
Hi Andrew,
No joy here...
greg@localhost:~> nslookup
Server:???????? 10.30.1.1
Address:??????? 10.30.1.1#53
** server can't find : SERVFAIL
greg@localhost:~> nslookup 71.162.157.26
26.157.162.71.in-addr.arpa????? name =
static-71-162-157-26.phlapa.fios.verizon.net.
greg@localhost:~> ping 71.162.156.26
PING 71.162.156.26 (71.162.156.26) 56(84) bytes of data.
64 bytes from 71.162.156.26: icmp_seq=1 ttl=51 time=88.1 ms
64 bytes from 71.162.156.26: icmp_seq=2 ttl=51 time=92.1 ms
64 bytes from 71.162.156.26: icmp_seq=3 ttl=51 time=95.6 ms
^C
This is using (I think) the cable company ISP's DNS.? If I try a
ping from my cell phone (on T-Mobile cell data, not WiFi), it does
find with the correct IP, but pings don't respond.?
But pings from the IP from my PC respond fine.? I haven't tried
forcing Google's or IBM's DNS for the lookup (8.8.8.8, et al).
On my PC, going to the website with just the IP (and not S) works -
I can see the website.? Going there with https and the IP yields a
warning from Firefox, saying the certificate is not valid for the
IP, just the named sites (, et al), which I think is
proper.? The PC is new as of about a week ago, running OpenSuSE
Linux.? Tried with both Firefox and Konqueror (which doesn't force
the https).
So, yeah, a puzzle.? It does seem like the website is fine, if you
can get to it.? It's just the DNS propagation that is kind of messed
up.
Hope some of this helps,
Greg? KO6TH
Andrew P. wrote:
OK, this is getting strange. I know I renewed my domain name and installed my new SSL certificate for the site. And (rather than use my house network where the server is connected), I used my AT&T mobile hotspot on a laptop to get Internet access, and over that path I was able to see my website.
So, something on the path of every user having difficulty accessing the site must be either:
1. not looking up the domain name correctly
2. caching the expired certificate so as to say the site isn't trusted.
I did find it amusing to notice, during the 5 days the expired certificate was still in use, the only users who still successfully accessed my website were webcrawlers and attackers. Apparently both disable failing an SSL connection just because the server certificate is expired.
So here are the checks I'd like everyone who is having difficulties to do:
1. Try to look up my domain name with the nslookup command on your local computer. From a shell, DOS prompt, or Terminal window (depending on your O/S), enter the command
nslookup .
You should get an answer back of 71.162.157.26. If you don't, then someone is caching a negative lookup (because somehow the auto-renewal of my domain name was turned off, so there may have been a few hours when my domain name wasn't in service, although there shouldn't have been).
2. Try browsing the URL
This should get you to my website without using DNS or SSL. If that works, then there is caching of the bad certificate lookup that needs to be cleared. You should clear your browser cache and try the normal URL again. If that fails, then you are using a proxy between you and the rest of the Internet that is caching the expired certificate lookup failure, rather than going to my webserver and trying again. Note that these proxies can be inserted without your consent or knowledge; the most common sort is on a hotel's Wifi, to ensure you are a paying guest before being allowed to use their Internet service.
Let me know what you find out with these tests.
Also, if you are getting the failure within YAAC, shut down YAAC completely and restart it. The Java runtime has a cache, too, but the cache will be discarded when you stop the Java runtime.
Hope this helps.
Andrew, KA2DDO
author of YAAC and webmaster of
________________________________________
From: [email protected] <[email protected]> on behalf of Bob Evans <bob9750@...>
Sent: Sunday, February 20, 2022 2:51 PM
To: [email protected]
Subject: Re: [yaac-users] YAAC
Hi
Just done a fresh install of YAAC on a new Ubuntu system and getting java error 'unable to receive files from server ......etc'
Also can't access ka2ddo homepage from other systems with 'site can't be reached' error
Bob
On Sat, Feb 19, 2022 at 7:18 PM Andrew P. <andrewemt@...<mailto:andrewemt@...>> wrote:
Looks like you typed Kilo Alpha 2 Delta Delta Zero instead of Oscar. :-)
The site is up; I checked from at least 3 places. However, if your browser or proxy server is caching the stale certificate, you might need to do a Shift-refresh of the page.
Andrew, KA2DDO
________________________________________
From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Richard Beggs <richard.n0eb@...<mailto:richard.n0eb@...>>
Sent: Saturday, February 19, 2022 7:07 PM
To: Andrew Pavlin
Subject: [yaac-users] YAAC
Still can not reach ka2dd0.org?
--
Thank You and God Bless []
Richard
|
DNS is not resolving for me.
michael@Desk-3 ~ $ ping www.k2ddo.org
ping: unknown host www.k2ddo.org
michael@Desk-3 ~ $ ping k2ddo.org
ping: unknown host k2ddo.org
michael@Desk-3 ~ $ nslookup www.ka2ddo.org
Server: 127.0.1.1
Address: 127.0.1.1#53
** server can't find www.ka2ddo.org: SERVFAIL
michael@Desk-3 ~ $ nslookup ka2ddo.org
Server: 127.0.1.1
Address: 127.0.1.1#53
** server can't find ka2ddo.org: SERVFAIL
michael@Desk-3 ~ $
michael@Desk-3 ~ $ nslookup google.com
Server: 127.0.1.1
Address: 127.0.1.1#53
Non-authoritative answer:
Name: google.com
Address: 172.217.14.206
michael@Desk-3 ~ $ nslookup wa7skg.com
Server: 127.0.1.1
Address: 127.0.1.1#53
Non-authoritative answer:
Name: wa7skg.com
Address: 74.208.215.118
michael@Desk-3 ~ $
DNS is working, just not finding you.
Michael WA7SKG
Andrew P. wrote on 2/20/22 12:24 PM:
toggle quoted message
Show quoted text
OK, this is getting strange. I know I renewed my domain name and installed my new SSL certificate for the site. And (rather than use my house network where the server is connected), I used my AT&T mobile hotspot on a laptop to get Internet access, and over that path I was able to see my website.
So, something on the path of every user having difficulty accessing the site must be either:
1. not looking up the domain name correctly
2. caching the expired certificate so as to say the site isn't trusted.
I did find it amusing to notice, during the 5 days the expired certificate was still in use, the only users who still successfully accessed my website were webcrawlers and attackers. Apparently both disable failing an SSL connection just because the server certificate is expired.
So here are the checks I'd like everyone who is having difficulties to do:
1. Try to look up my domain name with the nslookup command on your local computer. From a shell, DOS prompt, or Terminal window (depending on your O/S), enter the command
nslookup www.ka2ddo.org.
You should get an answer back of 71.162.157.26. If you don't, then someone is caching a negative lookup (because somehow the auto-renewal of my domain name was turned off, so there may have been a few hours when my domain name wasn't in service, although there shouldn't have been).
2. Try browsing the URL
This should get you to my website without using DNS or SSL. If that works, then there is caching of the bad certificate lookup that needs to be cleared. You should clear your browser cache and try the normal URL again. If that fails, then you are using a proxy between you and the rest of the Internet that is caching the expired certificate lookup failure, rather than going to my webserver and trying again. Note that these proxies can be inserted without your consent or knowledge; the most common sort is on a hotel's Wifi, to ensure you are a paying guest before being allowed to use their Internet service.
Let me know what you find out with these tests.
Also, if you are getting the failure within YAAC, shut down YAAC completely and restart it. The Java runtime has a cache, too, but the cache will be discarded when you stop the Java runtime.
Hope this helps.
Andrew, KA2DDO
author of YAAC and webmaster of
________________________________________
From: [email protected] <[email protected]> on behalf of Bob Evans <bob9750@...>
Sent: Sunday, February 20, 2022 2:51 PM
To: [email protected]
Subject: Re: [yaac-users] YAAC
Hi
Just done a fresh install of YAAC on a new Ubuntu system and getting java error 'unable to receive files from server ......etc'
Also can't access ka2ddo homepage from other systems with 'site can't be reached' error
Bob
On Sat, Feb 19, 2022 at 7:18 PM Andrew P. <andrewemt@...<mailto:andrewemt@...>> wrote:
Looks like you typed Kilo Alpha 2 Delta Delta Zero instead of Oscar. :-)
The site is up; I checked from at least 3 places. However, if your browser or proxy server is caching the stale certificate, you might need to do a Shift-refresh of the page.
Andrew, KA2DDO
________________________________________
From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Richard Beggs <richard.n0eb@...<mailto:richard.n0eb@...>>
Sent: Saturday, February 19, 2022 7:07 PM
To: Andrew Pavlin
Subject: [yaac-users] YAAC
Still can not reach ka2dd0.org<><>?
--
Thank You and God Bless []
Richard
|
OK, this is getting strange. I know I renewed my domain name and installed my new SSL certificate for the site. And (rather than use my house network where the server is connected), I used my AT&T mobile hotspot on a laptop to get Internet access, and over that path I was able to see my website. So, something on the path of every user having difficulty accessing the site must be either: 1. not looking up the domain name correctly 2. caching the expired certificate so as to say the site isn't trusted. I did find it amusing to notice, during the 5 days the expired certificate was still in use, the only users who still successfully accessed my website were webcrawlers and attackers. Apparently both disable failing an SSL connection just because the server certificate is expired. So here are the checks I'd like everyone who is having difficulties to do: 1. Try to look up my domain name with the nslookup command on your local computer. From a shell, DOS prompt, or Terminal window (depending on your O/S), enter the command nslookup www.ka2ddo.org. You should get an answer back of 71.162.157.26. If you don't, then someone is caching a negative lookup (because somehow the auto-renewal of my domain name was turned off, so there may have been a few hours when my domain name wasn't in service, although there shouldn't have been). 2. Try browsing the URL This should get you to my website without using DNS or SSL. If that works, then there is caching of the bad certificate lookup that needs to be cleared. You should clear your browser cache and try the normal URL again. If that fails, then you are using a proxy between you and the rest of the Internet that is caching the expired certificate lookup failure, rather than going to my webserver and trying again. Note that these proxies can be inserted without your consent or knowledge; the most common sort is on a hotel's Wifi, to ensure you are a paying guest before being allowed to use their Internet service. Let me know what you find out with these tests. Also, if you are getting the failure within YAAC, shut down YAAC completely and restart it. The Java runtime has a cache, too, but the cache will be discarded when you stop the Java runtime. Hope this helps. Andrew, KA2DDO author of YAAC and webmaster of ________________________________________ From: [email protected] < [email protected]> on behalf of Bob Evans <bob9750@...> Sent: Sunday, February 20, 2022 2:51 PM To: [email protected]Subject: Re: [yaac-users] YAAC Hi Just done a fresh install of YAAC on a new Ubuntu system and getting java error 'unable to receive files from server ......etc' Also can't access ka2ddo homepage from other systems with 'site can't be reached' error Bob On Sat, Feb 19, 2022 at 7:18 PM Andrew P. <andrewemt@...<mailto:andrewemt@...>> wrote: Looks like you typed Kilo Alpha 2 Delta Delta Zero instead of Oscar. :-) The site is up; I checked from at least 3 places. However, if your browser or proxy server is caching the stale certificate, you might need to do a Shift-refresh of the page. Andrew, KA2DDO ________________________________________ From: [email protected]<mailto: [email protected]> < [email protected]<mailto: [email protected]>> on behalf of Richard Beggs <richard.n0eb@...<mailto:richard.n0eb@...>> Sent: Saturday, February 19, 2022 7:07 PM To: Andrew Pavlin Subject: [yaac-users] YAAC Still can not reach ka2dd0.org<><>? -- Thank You and God Bless [] Richard
|
Kevin Ratcliff
Michael WA7SKG