bombz Posted July 11, 2021 Share Posted July 11, 2021 (edited) Hello, Attempting to use the trial key to test some hardware before purchase Prompted with: no connection and states cannot connect to the key server I am able to ping outside the network to public addresses with success here are the reoccurring logs Jul 8 15:11:36 Tower ntpd[3017]: ntpd [email protected] Tue Oct 20 18:42:21 UTC 2020 (1): Starting Jul 8 15:11:36 Tower ntpd[3017]: Command line: /usr/sbin/ntpd -g -u ntp:ntp Jul 8 15:11:36 Tower ntpd[3017]: ---------------------------------------------------- Jul 8 15:11:36 Tower ntpd[3017]: ntp-4 is maintained by Network Time Foundation, Jul 8 15:11:36 Tower ntpd[3017]: Inc. (NTF), a non-profit 501(c)(3) public-benefit Jul 8 15:11:36 Tower ntpd[3017]: corporation. Support and training for ntp-4 are Jul 8 15:11:36 Tower ntpd[3017]: available at https://www.nwtime.org/support Jul 8 15:11:36 Tower ntpd[3017]: ---------------------------------------------------- Jul 8 15:11:36 Tower ntpd[3019]: proto: precision = 0.042 usec (-24) Jul 8 15:11:36 Tower ntpd[3019]: basedate set to 2020-10-08 Jul 8 15:11:36 Tower ntpd[3019]: gps base set to 2020-10-11 (week 2127) Jul 8 15:11:36 Tower ntpd[3019]: Listen normally on 0 lo 127.0.0.1:123 Jul 8 15:11:36 Tower ntpd[3019]: Listen normally on 1 br0 10.1.0.108:123 Jul 8 15:11:36 Tower ntpd[3019]: Listen normally on 2 lo [::1]:123 Jul 8 15:11:36 Tower ntpd[3019]: Listening on routing socket on fd #19 for interface updates Jul 8 15:11:36 Tower ntpd[3019]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Jul 8 15:11:36 Tower ntpd[3019]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Jul 8 15:11:36 Tower root: Starting NTP daemon: /usr/sbin/ntpd -g -u ntp:ntp Jul 8 15:11:37 Tower emhttpd: error: get_limetech_time, 256: Invalid argument (22): -2 (60) Jul 8 15:11:37 Tower emhttpd: error: get_limetech_time, 256: Invalid argument (22): -2 (60) Jul 8 15:11:38 Tower emhttpd: error: get_limetech_time, 256: Invalid argument (22): -2 (60) Jul 8 15:11:39 Tower emhttpd: error: get_limetech_time, 256: Invalid argument (22): -2 (60) Jul 8 15:11:40 Tower emhttpd: error: get_limetech_time, 256: Invalid argument (22): -2 (60) Jul 8 15:11:43 Tower emhttpd: error: get_limetech_time, 256: Invalid argument (22): -2 (60) Jul 8 15:11:44 Tower emhttpd: error: get_limetech_time, 256: Invalid argument (22): -2 (60) Jul 8 15:11:45 Tower emhttpd: error: get_limetech_time, 256: Invalid argument (22): -2 (60) Any recommendations are welcome. Thank you, Edited July 13, 2021 by bombz Quote Link to comment
bombz Posted July 13, 2021 Author Share Posted July 13, 2021 I attempted to Deleting /boot/config/._Trial.key and Trial.key which allowed me to attempt to start the process over, same issue persists. Quote Link to comment
Frank1940 Posted July 13, 2021 Share Posted July 13, 2021 Are you pinging with IP addresses or URL's (google.com)? If IP addresses work but not URL's, you need to set up DNS service in the Settings >>> Network Settings page. Be sure to turn on 'Help' for this page. (One widely used DNS server is 8.8.8.8 ) If this does not provide the solution, post up the complete Diagnostics file in a new Post. Tools >>> Diagnostics Quote Link to comment
bombz Posted July 13, 2021 Author Share Posted July 13, 2021 Hey Frank, As always thanks for reaching out. I dug down into the firewall today and opened it up to test. Seems that was the concern. I will reach out if there are any further concerns. Thanks again! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.