apt update: Could not handshake: An unexpected TLS packet was received

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
3
down vote

favorite
1












I had problem doing sudo apt update for manually added repositories (I had problem with nodejs and docker) with my Ubuntu 17.10 VM running in VirtualBox. The error I get is Could not handshake: An unexpected TLS packet was received.



The following are steps that I took when trying to add docker repository and the output. The same thing happened when I tried to add nodejs as well.



sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
OK
sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo apt-key fingerprint 0EBFCD88
pub rsa4096 2017-02-22 [SCEA]
9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88
uid [ unknown] Docker Release (CE deb) <docker@docker.com>
sub rsa4096 2017-02-22 [S]

sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
[sudo] password for sdnc-dev:
sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo apt update
Ign:1 https://download.docker.com/linux/ubuntu artful InRelease
Err:2 https://download.docker.com/linux/ubuntu artful Release
Could not handshake: An unexpected TLS packet was received.
Hit:3 http://us.archive.ubuntu.com/ubuntu artful InRelease
Get:4 http://security.ubuntu.com/ubuntu artful-security InRelease [78.6 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu artful-updates InRelease [78.6 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu artful-backports InRelease [72.2 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages [226 kB]
Get:8 http://us.archive.ubuntu.com/ubuntu artful-updates/main i386 Packages [222 kB]
Get:9 http://us.archive.ubuntu.com/ubuntu artful-updates/main Translation-en [101 kB]
Get:10 http://us.archive.ubuntu.com/ubuntu artful-updates/universe i386 Packages [91.9 kB]
Get:11 http://us.archive.ubuntu.com/ubuntu artful-updates/universe amd64 Packages [92.8 kB]
Get:12 http://us.archive.ubuntu.com/ubuntu artful-updates/universe Translation-en [52.9 kB]
Reading package lists... Done
E: The repository 'https://download.docker.com/linux/ubuntu artful Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.


Here is the details of my setup:



 VM: Ubuntu 17.10
VirtualBox 5.2.8 r121009 (Qt5.6.2)
I am behind corporate proxy.


Does anyone know how to fix this?










share|improve this question

























    up vote
    3
    down vote

    favorite
    1












    I had problem doing sudo apt update for manually added repositories (I had problem with nodejs and docker) with my Ubuntu 17.10 VM running in VirtualBox. The error I get is Could not handshake: An unexpected TLS packet was received.



    The following are steps that I took when trying to add docker repository and the output. The same thing happened when I tried to add nodejs as well.



    sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
    OK
    sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo apt-key fingerprint 0EBFCD88
    pub rsa4096 2017-02-22 [SCEA]
    9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88
    uid [ unknown] Docker Release (CE deb) <docker@docker.com>
    sub rsa4096 2017-02-22 [S]

    sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
    [sudo] password for sdnc-dev:
    sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo apt update
    Ign:1 https://download.docker.com/linux/ubuntu artful InRelease
    Err:2 https://download.docker.com/linux/ubuntu artful Release
    Could not handshake: An unexpected TLS packet was received.
    Hit:3 http://us.archive.ubuntu.com/ubuntu artful InRelease
    Get:4 http://security.ubuntu.com/ubuntu artful-security InRelease [78.6 kB]
    Get:5 http://us.archive.ubuntu.com/ubuntu artful-updates InRelease [78.6 kB]
    Get:6 http://us.archive.ubuntu.com/ubuntu artful-backports InRelease [72.2 kB]
    Get:7 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages [226 kB]
    Get:8 http://us.archive.ubuntu.com/ubuntu artful-updates/main i386 Packages [222 kB]
    Get:9 http://us.archive.ubuntu.com/ubuntu artful-updates/main Translation-en [101 kB]
    Get:10 http://us.archive.ubuntu.com/ubuntu artful-updates/universe i386 Packages [91.9 kB]
    Get:11 http://us.archive.ubuntu.com/ubuntu artful-updates/universe amd64 Packages [92.8 kB]
    Get:12 http://us.archive.ubuntu.com/ubuntu artful-updates/universe Translation-en [52.9 kB]
    Reading package lists... Done
    E: The repository 'https://download.docker.com/linux/ubuntu artful Release' does not have a Release file.
    N: Updating from such a repository can't be done securely, and is therefore disabled by default.
    N: See apt-secure(8) manpage for repository creation and user configuration details.


    Here is the details of my setup:



     VM: Ubuntu 17.10
    VirtualBox 5.2.8 r121009 (Qt5.6.2)
    I am behind corporate proxy.


    Does anyone know how to fix this?










    share|improve this question























      up vote
      3
      down vote

      favorite
      1









      up vote
      3
      down vote

      favorite
      1






      1





      I had problem doing sudo apt update for manually added repositories (I had problem with nodejs and docker) with my Ubuntu 17.10 VM running in VirtualBox. The error I get is Could not handshake: An unexpected TLS packet was received.



      The following are steps that I took when trying to add docker repository and the output. The same thing happened when I tried to add nodejs as well.



      sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
      OK
      sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo apt-key fingerprint 0EBFCD88
      pub rsa4096 2017-02-22 [SCEA]
      9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88
      uid [ unknown] Docker Release (CE deb) <docker@docker.com>
      sub rsa4096 2017-02-22 [S]

      sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
      [sudo] password for sdnc-dev:
      sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo apt update
      Ign:1 https://download.docker.com/linux/ubuntu artful InRelease
      Err:2 https://download.docker.com/linux/ubuntu artful Release
      Could not handshake: An unexpected TLS packet was received.
      Hit:3 http://us.archive.ubuntu.com/ubuntu artful InRelease
      Get:4 http://security.ubuntu.com/ubuntu artful-security InRelease [78.6 kB]
      Get:5 http://us.archive.ubuntu.com/ubuntu artful-updates InRelease [78.6 kB]
      Get:6 http://us.archive.ubuntu.com/ubuntu artful-backports InRelease [72.2 kB]
      Get:7 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages [226 kB]
      Get:8 http://us.archive.ubuntu.com/ubuntu artful-updates/main i386 Packages [222 kB]
      Get:9 http://us.archive.ubuntu.com/ubuntu artful-updates/main Translation-en [101 kB]
      Get:10 http://us.archive.ubuntu.com/ubuntu artful-updates/universe i386 Packages [91.9 kB]
      Get:11 http://us.archive.ubuntu.com/ubuntu artful-updates/universe amd64 Packages [92.8 kB]
      Get:12 http://us.archive.ubuntu.com/ubuntu artful-updates/universe Translation-en [52.9 kB]
      Reading package lists... Done
      E: The repository 'https://download.docker.com/linux/ubuntu artful Release' does not have a Release file.
      N: Updating from such a repository can't be done securely, and is therefore disabled by default.
      N: See apt-secure(8) manpage for repository creation and user configuration details.


      Here is the details of my setup:



       VM: Ubuntu 17.10
      VirtualBox 5.2.8 r121009 (Qt5.6.2)
      I am behind corporate proxy.


      Does anyone know how to fix this?










      share|improve this question













      I had problem doing sudo apt update for manually added repositories (I had problem with nodejs and docker) with my Ubuntu 17.10 VM running in VirtualBox. The error I get is Could not handshake: An unexpected TLS packet was received.



      The following are steps that I took when trying to add docker repository and the output. The same thing happened when I tried to add nodejs as well.



      sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
      OK
      sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo apt-key fingerprint 0EBFCD88
      pub rsa4096 2017-02-22 [SCEA]
      9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88
      uid [ unknown] Docker Release (CE deb) <docker@docker.com>
      sub rsa4096 2017-02-22 [S]

      sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
      [sudo] password for sdnc-dev:
      sdnc-dev@sdncdev-VirtualBox:~/tools/idea-IC-173.4674.33/bin$ sudo apt update
      Ign:1 https://download.docker.com/linux/ubuntu artful InRelease
      Err:2 https://download.docker.com/linux/ubuntu artful Release
      Could not handshake: An unexpected TLS packet was received.
      Hit:3 http://us.archive.ubuntu.com/ubuntu artful InRelease
      Get:4 http://security.ubuntu.com/ubuntu artful-security InRelease [78.6 kB]
      Get:5 http://us.archive.ubuntu.com/ubuntu artful-updates InRelease [78.6 kB]
      Get:6 http://us.archive.ubuntu.com/ubuntu artful-backports InRelease [72.2 kB]
      Get:7 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages [226 kB]
      Get:8 http://us.archive.ubuntu.com/ubuntu artful-updates/main i386 Packages [222 kB]
      Get:9 http://us.archive.ubuntu.com/ubuntu artful-updates/main Translation-en [101 kB]
      Get:10 http://us.archive.ubuntu.com/ubuntu artful-updates/universe i386 Packages [91.9 kB]
      Get:11 http://us.archive.ubuntu.com/ubuntu artful-updates/universe amd64 Packages [92.8 kB]
      Get:12 http://us.archive.ubuntu.com/ubuntu artful-updates/universe Translation-en [52.9 kB]
      Reading package lists... Done
      E: The repository 'https://download.docker.com/linux/ubuntu artful Release' does not have a Release file.
      N: Updating from such a repository can't be done securely, and is therefore disabled by default.
      N: See apt-secure(8) manpage for repository creation and user configuration details.


      Here is the details of my setup:



       VM: Ubuntu 17.10
      VirtualBox 5.2.8 r121009 (Qt5.6.2)
      I am behind corporate proxy.


      Does anyone know how to fix this?







      apt virtualbox 17.10






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 14 at 19:24









      Phuong Hoang

      184




      184




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          5
          down vote



          accepted










          Check if the proxy is also set for https. Since curl is working with https, I assume, that somewhere in /etc/apt/apt.conf or /etc/apt/apt.conf.d/ is a proxy configuration. You need to specify the proxy for all protocols:



          # e.g. in file /etc/apt/apt.conf.d/05proxy
          Acquire::http::proxy "http://192.168.0.1:3128/";
          Acquire::https::proxy "http://192.168.0.1:3128/";
          Acquire::ftp::proxy "http://192.168.0.1:3128/";


          Also keep in mind, if the proxy configuration is only set for the sdnc-dev user, you need sudo -E to expose the environment to the root user.






          share|improve this answer




















          • I did set the https proxy in /etc/apt/apt.conf/ file. Turned out that the https` setting was set wrong. It was set it "ip:port/&quot; instead of "ip:port/&quot; (without the s character). I changed it and it works now. Not sure if this is the real cause, but at least I have a working apt now.
            – Phuong Hoang
            Mar 14 at 20:19










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "89"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1014973%2fapt-update-could-not-handshake-an-unexpected-tls-packet-was-received%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          5
          down vote



          accepted










          Check if the proxy is also set for https. Since curl is working with https, I assume, that somewhere in /etc/apt/apt.conf or /etc/apt/apt.conf.d/ is a proxy configuration. You need to specify the proxy for all protocols:



          # e.g. in file /etc/apt/apt.conf.d/05proxy
          Acquire::http::proxy "http://192.168.0.1:3128/";
          Acquire::https::proxy "http://192.168.0.1:3128/";
          Acquire::ftp::proxy "http://192.168.0.1:3128/";


          Also keep in mind, if the proxy configuration is only set for the sdnc-dev user, you need sudo -E to expose the environment to the root user.






          share|improve this answer




















          • I did set the https proxy in /etc/apt/apt.conf/ file. Turned out that the https` setting was set wrong. It was set it "ip:port/&quot; instead of "ip:port/&quot; (without the s character). I changed it and it works now. Not sure if this is the real cause, but at least I have a working apt now.
            – Phuong Hoang
            Mar 14 at 20:19














          up vote
          5
          down vote



          accepted










          Check if the proxy is also set for https. Since curl is working with https, I assume, that somewhere in /etc/apt/apt.conf or /etc/apt/apt.conf.d/ is a proxy configuration. You need to specify the proxy for all protocols:



          # e.g. in file /etc/apt/apt.conf.d/05proxy
          Acquire::http::proxy "http://192.168.0.1:3128/";
          Acquire::https::proxy "http://192.168.0.1:3128/";
          Acquire::ftp::proxy "http://192.168.0.1:3128/";


          Also keep in mind, if the proxy configuration is only set for the sdnc-dev user, you need sudo -E to expose the environment to the root user.






          share|improve this answer




















          • I did set the https proxy in /etc/apt/apt.conf/ file. Turned out that the https` setting was set wrong. It was set it "ip:port/&quot; instead of "ip:port/&quot; (without the s character). I changed it and it works now. Not sure if this is the real cause, but at least I have a working apt now.
            – Phuong Hoang
            Mar 14 at 20:19












          up vote
          5
          down vote



          accepted







          up vote
          5
          down vote



          accepted






          Check if the proxy is also set for https. Since curl is working with https, I assume, that somewhere in /etc/apt/apt.conf or /etc/apt/apt.conf.d/ is a proxy configuration. You need to specify the proxy for all protocols:



          # e.g. in file /etc/apt/apt.conf.d/05proxy
          Acquire::http::proxy "http://192.168.0.1:3128/";
          Acquire::https::proxy "http://192.168.0.1:3128/";
          Acquire::ftp::proxy "http://192.168.0.1:3128/";


          Also keep in mind, if the proxy configuration is only set for the sdnc-dev user, you need sudo -E to expose the environment to the root user.






          share|improve this answer












          Check if the proxy is also set for https. Since curl is working with https, I assume, that somewhere in /etc/apt/apt.conf or /etc/apt/apt.conf.d/ is a proxy configuration. You need to specify the proxy for all protocols:



          # e.g. in file /etc/apt/apt.conf.d/05proxy
          Acquire::http::proxy "http://192.168.0.1:3128/";
          Acquire::https::proxy "http://192.168.0.1:3128/";
          Acquire::ftp::proxy "http://192.168.0.1:3128/";


          Also keep in mind, if the proxy configuration is only set for the sdnc-dev user, you need sudo -E to expose the environment to the root user.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Mar 14 at 19:57









          Simon Sudler

          960111




          960111











          • I did set the https proxy in /etc/apt/apt.conf/ file. Turned out that the https` setting was set wrong. It was set it "ip:port/&quot; instead of "ip:port/&quot; (without the s character). I changed it and it works now. Not sure if this is the real cause, but at least I have a working apt now.
            – Phuong Hoang
            Mar 14 at 20:19
















          • I did set the https proxy in /etc/apt/apt.conf/ file. Turned out that the https` setting was set wrong. It was set it "ip:port/&quot; instead of "ip:port/&quot; (without the s character). I changed it and it works now. Not sure if this is the real cause, but at least I have a working apt now.
            – Phuong Hoang
            Mar 14 at 20:19















          I did set the https proxy in /etc/apt/apt.conf/ file. Turned out that the https` setting was set wrong. It was set it "ip:port/&quot; instead of "ip:port/&quot; (without the s character). I changed it and it works now. Not sure if this is the real cause, but at least I have a working apt now.
          – Phuong Hoang
          Mar 14 at 20:19




          I did set the https proxy in /etc/apt/apt.conf/ file. Turned out that the https` setting was set wrong. It was set it "ip:port/&quot; instead of "ip:port/&quot; (without the s character). I changed it and it works now. Not sure if this is the real cause, but at least I have a working apt now.
          – Phuong Hoang
          Mar 14 at 20:19

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1014973%2fapt-update-could-not-handshake-an-unexpected-tls-packet-was-received%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          pylint3 and pip3 broken

          Missing snmpget and snmpwalk

          How to enroll fingerprints to Ubuntu 17.10 with VFS491