LTSpice - cannot sync

Status
This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.
Jump to Latest
B

bugbear

Member
Joined 2016
I've updated my machine to Lubuntu 20.

Reinstalled wine, and LTspice XVii. All good.

Tried to use

Tools->Sync Release

To download and install any available updates, and got an error;

"Trouble Parsing http://ltspice.linear.com/fieldsyncXVii/release.log.gz"

The message claimed this was normally due to trouble accessing the internet, which (with Wine involved) I could have believed.

However, reverting to the Linux command line I ran:

wget http://ltspice.linear.com/fieldsyncXVii/release.log.gz

And got the following complex result:
Code: 
wget [URL]http://ltspice.linear.com/fieldsyncXVii/release.log.gz[/URL]
--2020-10-06 12:46:50--  [URL]http://ltspice.linear.com/fieldsyncXVii/release.log.gz[/URL]
Resolving ltspice.linear.com (ltspice.linear.com)... 81.130.110.192, 81.130.110.152
Connecting to ltspice.linear.com (ltspice.linear.com)|81.130.110.192|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: [URL]https://ltspice.linear.com/fieldsyncXVii/release.log.gz[/URL] [following]
--2020-10-06 12:46:50--  [URL]https://ltspice.linear.com/fieldsyncXVii/release.log.gz[/URL]
Connecting to ltspice.linear.com (ltspice.linear.com)|81.130.110.192|:443... connected.
ERROR: no certificate subject alternative name matches
        requested host name ‘ltspice.linear.com’.
To connect to ltspice.linear.com insecurely, use `--no-check-certificate'.
So - is the update location offline? Is LTSpice now going for the wrong URL?


BugBear
 
X

ximikas

Member
Joined 2010
Hi ,looks like security changes from their side . Try in terminal to download that log.gz file ,add a mentioned command --no-check-certificate . If file download will sucessfull , then need to adjust ltspice settings ,server adress ,maybe update app manually.
 
B

bugbear

Member
Joined 2016
Removed the first level of "bounce", added --no-check-certificate. Not looking good.



Code: 
wget --no-check-certificate  [url]https://ltspice.linear.com/fieldsyncXVii/release.log.gz[/url]
--2020-10-06 14:11:06--  [url]https://ltspice.linear.com/fieldsyncXVii/release.log.gz[/url]
Resolving ltspice.linear.com (ltspice.linear.com)... 81.130.110.152, 81.130.110.192
Connecting to ltspice.linear.com (ltspice.linear.com)|81.130.110.152|:443... connected.
WARNING: no certificate subject alternative name matches
        requested host name ‘ltspice.linear.com’.
HTTP request sent, awaiting response... 404 Not Found
2020-10-06 14:11:11 ERROR 404: Not Found.
 
B

bugbear

Member
Joined 2016
Looks like they've updated something. Wget now does:

Code: 
wget [URL]http://LTspice.linear.com/fieldsyncXVII/release.log.gz[/URL]
--2020-10-14 11:04:18--  [URL]http://ltspice.linear.com/fieldsyncXVII/release.log.gz[/URL]
Resolving [URL="http://ltspice.linear.com"]ltspice.linear.com[/URL]<[URL]http://ltspice.linear.com[/URL]> ([URL="http://ltspice.linear.com"]ltspice.linear.com[/URL]<[URL]http://ltspice.linear.com[/URL]>)... 23.198.72.177
Connecting to [URL="http://ltspice.linear.com"]ltspice.linear.com[/URL]<[URL]http://ltspice.linear.com[/URL]> ([URL="http://ltspice.linear.com"]ltspice.linear.com[/URL]<[URL]http://ltspice.linear.com[/URL]>)|23.198.72.177|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: [URL]https://ltspice.linear.com/fieldsyncXVII/release.log.gz[/URL] [following]
--2020-10-14 11:04:18--  [URL]https://ltspice.linear.com/fieldsyncXVII/release.log.gz[/URL]
Connecting to [URL="http://ltspice.linear.com"]ltspice.linear.com[/URL]<[URL]http://ltspice.linear.com[/URL]> ([URL="http://ltspice.linear.com"]ltspice.linear.com[/URL]<[URL]http://ltspice.linear.com[/URL]>)|23.198.72.177|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 272017 (266K) [application/x-gzip]
Saving to: ‘release.log.gz’

release.log.gz          100%[==============================>] 265.64K  --.-KB/s    in 0.1s

2020-10-14 11:04:19 (1.75 MB/s) - ‘release.log.gz’ saved [272017/272017]

BugBear
 
X

ximikas

Member
Joined 2010
I just tried in browser ,both links to log.gz file works , http and https . Maybe you're right , app don't know how to handle 301 ...But if link to http working,there should be no 301 response . Is there any update server related settings in app config ? Or in other files in its folder ... According to your log , app looks for http , so if reference is found in settings or config files can be simply edited , you may give it a try to replace adress beginning http:// with https:// . Have you tried deleting old log.gz or cache ,if exists ?
 
Ultima Thule

Ultima Thule

Member
Joined 2004
Maybe this message may help?

LTspice@groups.io | updating ltspice problem

hi
ltspice on my laptop was giving message for updating ltspice.
when first time i pressed sync release, it showed the message in below, but in second times it did update. where was problem. i also had problem with update before.
message:
troubling parsing "http:/ltspice.linear.com/fieldsyncXVii/release.log.gz"
incrementally updating off the web failed. this is usually due to trouble with your internet connection. Ltspice uses http protocol for downloading binary files. the algorithm it uses can fail for some types of internet connections and firewalls.
you can alternatively download the newest version and reinstall.

with regards.
Click to expand...

ps. I don't have ltspice installed right now, so can only try download that sync file with browser but I get a failed connection too.
 
B

bugbear

Member
Joined 2016
After some googling I (with little true understanding) used tcpdump to monitor traffic to and from ltspice.linear.com=23.198.72.177.

I do not fully understand the messages I'm seeing, but what is perfectly simple and clear is that only 1 request is sent from LTspice, and only 1 response is received.

I interpret this as meaning the 301 response is NOT correctly handled, and hence the sync fails.


BugBear
 
Status
This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.
Top Bottom