Unable to install or update plugins

Support
1

Hi,
Every time i try to install or update plugin from the .org repository it fails with error message " cURL error 28: Resolving timed out after 10527 milliseconds"
I am using lates Local for Mac.

Manual installation works.
Any advice?

2

Sometimes VirtualBox doesn’t set up the network device for outbound traffic so the best solution is to go to Help » Restart Local’s Machine and that should do the trick.

Sorry for the trouble!

3

Thank you for the information, but it is not working! I think I will get back to mamp or such thing never happened. Too bad that I have to move to many projects I have started from Flywheel to MAPM. This is a pain in the ass, very frustrating

4

I had this error today, along with something else which started yesterday, which was resources such as stylesheets, scripts and pics not loading over https.

I think I resolved it by prioritising my internet provider’s DNS settings (169.1.1.4 / 9) over Google’s.
(8.8.8.8 and 8.8.4.4, which I had added a few years ago).

…or something resolved it, but it did resolve at that point.

 > System Preferences > Network > Advanced > DNS

I imagine this must be a Chrome update enforcing HTTPS?

Update 1
yes, it was Chrome, and the fact that I’m using .dev domains which I’ll change.
(Doesn’t LBF default to .dev for new sites? Probs should change that…)

apache - How to stop Chrome from redirecting to HTTPS? - Stack Overflow

Chrome 63 forces .dev domains to HTTPS. The Internet Engineering Task Force RFC2606specified what top level domains should be used for local development, and .dev isn’t on that list.

Google owns the .dev top level domain and automatically redirects all .dev domain names to an HTTPs version of the site via preloaded HSTS.

You should use .test, .example, .invalid or .localhost TLDs instead.

Update 2

BackupBuddy was giving the familiar loopback / cURL error, so I disabled some plugins to see what what causing it.

It appears Really Simple SSL WordPress plugin was what resolved the issue with resources not loading, because with it disabled they stopped loading again… which makes sense in retrospect.