When I try to use the live link it produces the following error. Error: connect ETIMEDOUT 34.121.54.145:443 at TCPConnectWrap.afterConnect [as oncomplete] (net.js: 1146:16)
Steps to reproduce
After starting site, enable live link.
After a minute, it throws the error
Environment Info
Describe your environment.
What Operating System are you using? Windows 10
What versions of site software (Nginx, Apache, PHP, MySQL) is used? nginx, 7.4.1, MySQL 8.0.16
What version of Local is installed? 6.4.2+6012
Supporting info
Please provide your Local Log. See this Community Forum post for instructions on how to do so:
Just a āme tooā, this AM I started getting this error:
Error: connect ECONNREFUSED 34.121.54.145:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
When I click on āenable live linkā, after a time I get the following error message:
āError: connect ETIMEDOUT 34.121.54.145:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)ā
It was working up until this morning (I think). I have no idea how to fix this, so I would appreciate any help that you can give - thanks.
Troubleshooting Questions
Does this happen for all sites in Local, or just one in particular? All sites
Are you able to create a new, plain WordPress site in Local and access it in a Browser? Yes
Replication
Describe the steps that others can take to replicate this issue. If you have screenshots that can help clarify what is happening, please include them!
System Details
Which version of Local is being used? 6.4.2
What Operating System (OS) and OS version is being used? Windows 10 Home
For example: macOS Catalina or Windows 10 Professional local-logs.zip (14.7 KB)
Attach the Local Log. See this Help Doc for instructions on how to do so:
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however thereās always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isnāt private info like passwords being displayed.
Hi all! Thank you for bringing this to our attention so quickly - I merged several different threads in the forums into here so that we keep conversation in the same place.
This is an initial āACKā to the issue. It looks like something changed on our remote infrastructure sometime this morning that started refusing connections.
The engineering team is on it, and I will post updates back here as I have them.
Updating here - weāre digging into some errors in our remote infrastructure that show the connection being refused. Based on the documentation, we think the issue lies in the API between Local and the remote server, but we havenāt pinpointed it yet. Weāre going to keep researching.
Sorry in advance for the down-time here! I understand the frustration.
Hello, Iāve a problem with starting Live Links. It started yesterday and when I click on Enable after 1 or 2 minutes, Local give me this error. It happens on all of my website installed. My connection works very well and I canāt figure out where is the problem. Someone can tell me something about and how to fix this?
When I click on āenable live linkā, after a time I get the following error message:
āError: connect ETIMEDOUT 34.121.54.145:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)ā
yesterday I wanted to continue working on the construction of my site locally, and impossible to activate live link. I imported the site, nothing.
Troubleshooting Questions
Does this happen for all sites in Local, or just one in particular? All sites
Are you able to create a new, plain WordPress site in Local and access it in a Browser? Yes
Describe the steps that others can take to replicate this issue. If you have screenshots that can help clarify what is happening, please include them!
System Details
Which version of Local is being used? 6.4.2
What Operating System (OS) and OS version is being used? Windows 10 Family
Attach the Local Log. See this Help Doc for instructions on how to do so:
Hey all - weāve worked with our remote infrastructure partner (Google), and traced the issue to a mismatch in some API versioning. Weāre getting this fixed up and should have an update here shortly.
