Radek's picture
Radek - Sun, 2016/01/31 - 16:06

hi all

I have just downloaded and imported into VirtualBox 4.3.22 on Win7 the latest WordPress turnkey - turnkey-wordpress-14.0-jessie-amd64.ova. I can connect to wp from the browser but I am not able to run

 

apt-get update
E: The method driver /usr/lib/apt/methods/https could not be found.

I searched the web but did not find any help.



 apt install apt-transport-https gives me error "unable to lacate package apt-transport-https"

any idea how to fix that?

Thank you

R

Forum: 
Support
Tags: 
apt-get
Jeremy Davis's picture

Jeremy Davis - Sun, 2016/01/31 - 23:51
There should not be any https entries in your sources list. My guess is that you have added an entry there and have made a mistake.

Please post the output of the following: 

cat /etc/apt/sources.list
ls -l /etc/apt/sources.list.d/
cat /etc/apt/sources.list.d/sources.list
/etc/apt/sources.list.d/security.sources.list
Radek's picture

Radek - Mon, 2016/02/01 - 14:20

Hi Jeremy

I did not change anything becuase I never had to and I wouldn't even know where to go. I already checked the files and yes, there is no https entry. Only http.

Where can I get older versions of Wordpress TKL?

Thank you

Radek


Jeremy Davis's picture

Jeremy Davis - Tue, 2016/02/02 - 10:39
I reckon your download must be corrupt. I have tested it multiple times and never come across that. The best way to check for corruption is to download the relevant '.sig" file (FWIW there is a link on the appliance page - but to make it easy here is a link to turnkey-wordpress-14.0-jessie-amd64.ova.sig). Then compare the MD5 or SHA1 hash in the sig file against the MD5 or SHA1 hash of the file that you have (you may need to download and/or install some third party tool to do that depending on your OS).

I know that it might be tempting to just download it again, but that won't actually prove anything if it still doesn't work. The mirror that you are connecting to may have a corrupt version of the file...

Let me know how you go...

Radek's picture

Radek - Sun, 2016/02/07 - 13:53

Hi all

the issue was that my VM was not online. It  was not connected to the internet. Yes, sounds sily but it was the cause. I did try ping to google.com and it worked but probly only for some time.

All solved now.

Thank you

 

R


Add new comment