Trying to upgrade Ubuntu from 18.04 to 18.10 and then 19.04failed to connect to...

How come there are so many candidates for the 2020 Democratic party presidential nomination?

Why was Germany not as successful as other Europeans in establishing overseas colonies?

What was the first Intel x86 processor with "Base + Index * Scale + Displacement" addressing mode?

Phrase for the opposite of "foolproof"

How would one muzzle a full grown polar bear in the 13th century?

How to stop co-workers from teasing me because I know Russian?

Is there an official tutorial for installing Ubuntu 18.04+ on a device with an SSD and an additional internal hard drive?

Please, smoke with good manners

Fizzy, soft, pop and still drinks

How to reduce LED flash rate (frequency)

Mac Pro install disk keeps ejecting itself

Why was the Spitfire's elliptical wing almost uncopied by other aircraft of World War 2?

US visa is under administrative processing, I need the passport back ASAP

How can the Zone of Truth spell be defeated without the caster knowing?

Is the 5 MB static resource size limit 5,242,880 bytes or 5,000,000 bytes?

How to solve constants out of the internal energy equation?

How much cash can I safely carry into the USA and avoid civil forfeiture?

What do the phrase "Reeyan's seacrest" and the word "fraggle" mean in a sketch?

Is there really no use for MD5 anymore?

How to get a plain text file version of a CP/M .BAS (M-BASIC) program?

Packing rectangles: Does rotation ever help?

Size of electromagnet needed to replicate Earth's magnetic field

Reducing vertical space in stackrel

Is there a way to get a compiler for the original B programming language?



Trying to upgrade Ubuntu from 18.04 to 18.10 and then 19.04


failed to connect to http://changelogs.ubuntu.com/meta-releaseBoot time takes more than 5 minutes after moving partitions in Ubuntu 18.04Ubuntu 18.04 boots to black screen without nvidia, tried lightdm, xfce, but nothing workedUbuntu 18.04 on login loop, even with correct passwordProblem trying add PPA's on ubuntu 18.04No internet after 16.04 LTS 18.04.01 UpgradeHP15 Ubuntu 18.04 freezesUpgrade from 16.04 to 18.04 has stopped scanner being found by Simple ScanUbuntu server 16.04 unable upgrade to 18.04Unable to add repository un Ubuntu 18.04Failed to fetch when building docker






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















Okay this should be easy but it seems unusually difficult. I have an Ubuntu 18.04 (Bionic) AWS EC2 instance which I want to upgrade. I realise that I'll have to do it in two steps but I'm having a few issues, as follows.



I've done quite a bit of research on this so here's what I've done:



sudo rm /var/lib/ubuntu-release-upgrader/release-upgrade-available

Edited /etc/update-manager/release-upgrades and set Prompt= from lts to normal.

sudo apt update
sudo apt upgrade
sudo apt dist-upgrade


Tried: sudo do-release-upgrade
Result: Checking for a new Ubuntu release
Failed to connect to https://changelogs.ubuntu.com/meta-release. Check your Internet connection or proxy settings
No new release found.



Tried: sudo do-release-upgrade -d
Result: Checking for a new Ubuntu release
Failed to connect to https://changelogs.ubuntu.com/meta-release-development. Check your Internet connection or proxy settings
Upgrades to the development release are only
available from the latest supported release.



I can curl to https://changelogs.ubuntu.com/meta-release-development with no problems.



I've restarted the Server a few times and tried to repeat the process, with no luck. I even found an article that recommended editing a dist-upgrade related Python file with an SSL related setting. This didn't fix the issue so I backed that edit out again.



I suspect that if 18.10 or 19.04 were recorded as LTS then I'd be able to upgrade to them but that doesn't help me at the moment.



Any ideas would be much appreciated. I'd rather not build a fresh Server at this stage (although I need to convert the build to IaC in the future).



Thank you.










share|improve this question









New contributor




ChrisFNZ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.



























    0















    Okay this should be easy but it seems unusually difficult. I have an Ubuntu 18.04 (Bionic) AWS EC2 instance which I want to upgrade. I realise that I'll have to do it in two steps but I'm having a few issues, as follows.



    I've done quite a bit of research on this so here's what I've done:



    sudo rm /var/lib/ubuntu-release-upgrader/release-upgrade-available

    Edited /etc/update-manager/release-upgrades and set Prompt= from lts to normal.

    sudo apt update
    sudo apt upgrade
    sudo apt dist-upgrade


    Tried: sudo do-release-upgrade
    Result: Checking for a new Ubuntu release
    Failed to connect to https://changelogs.ubuntu.com/meta-release. Check your Internet connection or proxy settings
    No new release found.



    Tried: sudo do-release-upgrade -d
    Result: Checking for a new Ubuntu release
    Failed to connect to https://changelogs.ubuntu.com/meta-release-development. Check your Internet connection or proxy settings
    Upgrades to the development release are only
    available from the latest supported release.



    I can curl to https://changelogs.ubuntu.com/meta-release-development with no problems.



    I've restarted the Server a few times and tried to repeat the process, with no luck. I even found an article that recommended editing a dist-upgrade related Python file with an SSL related setting. This didn't fix the issue so I backed that edit out again.



    I suspect that if 18.10 or 19.04 were recorded as LTS then I'd be able to upgrade to them but that doesn't help me at the moment.



    Any ideas would be much appreciated. I'd rather not build a fresh Server at this stage (although I need to convert the build to IaC in the future).



    Thank you.










    share|improve this question









    New contributor




    ChrisFNZ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      Okay this should be easy but it seems unusually difficult. I have an Ubuntu 18.04 (Bionic) AWS EC2 instance which I want to upgrade. I realise that I'll have to do it in two steps but I'm having a few issues, as follows.



      I've done quite a bit of research on this so here's what I've done:



      sudo rm /var/lib/ubuntu-release-upgrader/release-upgrade-available

      Edited /etc/update-manager/release-upgrades and set Prompt= from lts to normal.

      sudo apt update
      sudo apt upgrade
      sudo apt dist-upgrade


      Tried: sudo do-release-upgrade
      Result: Checking for a new Ubuntu release
      Failed to connect to https://changelogs.ubuntu.com/meta-release. Check your Internet connection or proxy settings
      No new release found.



      Tried: sudo do-release-upgrade -d
      Result: Checking for a new Ubuntu release
      Failed to connect to https://changelogs.ubuntu.com/meta-release-development. Check your Internet connection or proxy settings
      Upgrades to the development release are only
      available from the latest supported release.



      I can curl to https://changelogs.ubuntu.com/meta-release-development with no problems.



      I've restarted the Server a few times and tried to repeat the process, with no luck. I even found an article that recommended editing a dist-upgrade related Python file with an SSL related setting. This didn't fix the issue so I backed that edit out again.



      I suspect that if 18.10 or 19.04 were recorded as LTS then I'd be able to upgrade to them but that doesn't help me at the moment.



      Any ideas would be much appreciated. I'd rather not build a fresh Server at this stage (although I need to convert the build to IaC in the future).



      Thank you.










      share|improve this question









      New contributor




      ChrisFNZ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      Okay this should be easy but it seems unusually difficult. I have an Ubuntu 18.04 (Bionic) AWS EC2 instance which I want to upgrade. I realise that I'll have to do it in two steps but I'm having a few issues, as follows.



      I've done quite a bit of research on this so here's what I've done:



      sudo rm /var/lib/ubuntu-release-upgrader/release-upgrade-available

      Edited /etc/update-manager/release-upgrades and set Prompt= from lts to normal.

      sudo apt update
      sudo apt upgrade
      sudo apt dist-upgrade


      Tried: sudo do-release-upgrade
      Result: Checking for a new Ubuntu release
      Failed to connect to https://changelogs.ubuntu.com/meta-release. Check your Internet connection or proxy settings
      No new release found.



      Tried: sudo do-release-upgrade -d
      Result: Checking for a new Ubuntu release
      Failed to connect to https://changelogs.ubuntu.com/meta-release-development. Check your Internet connection or proxy settings
      Upgrades to the development release are only
      available from the latest supported release.



      I can curl to https://changelogs.ubuntu.com/meta-release-development with no problems.



      I've restarted the Server a few times and tried to repeat the process, with no luck. I even found an article that recommended editing a dist-upgrade related Python file with an SSL related setting. This didn't fix the issue so I backed that edit out again.



      I suspect that if 18.10 or 19.04 were recorded as LTS then I'd be able to upgrade to them but that doesn't help me at the moment.



      Any ideas would be much appreciated. I'd rather not build a fresh Server at this stage (although I need to convert the build to IaC in the future).



      Thank you.







      18.04






      share|improve this question









      New contributor




      ChrisFNZ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      ChrisFNZ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited 14 hours ago







      ChrisFNZ













      New contributor




      ChrisFNZ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 14 hours ago









      ChrisFNZChrisFNZ

      12




      12




      New contributor




      ChrisFNZ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      ChrisFNZ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      ChrisFNZ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          1 Answer
          1






          active

          oldest

          votes


















          0














          as I read from this discussion




          /usr/lib/ubuntu-release-upgrader/release-upgrade-motd actually calls /usr/lib/ubuntu-release-upgrader/check-new-release.
          If you run /usr/lib/ubuntu-release-upgrader/check-new-release, that's the script that fails with the error message.




          some other user fixed the issue running




          All I did to make it go away was: sudo rm /var/lib/ubuntu-release-upgrader/release-upgrade-available




          The same problem was experienced with 17.10




          The script will only update the file every 24 hours. So if you wait long enough, the file will go stale and the script will update the file anyway. But,if you want to update it immediately, just remove /var/lib/ubuntu-release-upgrader/release-upgrade-available and run /etc/update-motd.d/91-release-upgrade and it should start working correctly.




          Happy to help you further






          share|improve this answer
























          • Thanks Fabrizio. Unfortunately that didn't work. The same issues remain. BTW per above I've already tried removing the release-upgrade-available file. Thank you anyway.

            – ChrisFNZ
            2 hours ago












          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',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          ChrisFNZ is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1138586%2ftrying-to-upgrade-ubuntu-from-18-04-to-18-10-and-then-19-04%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          as I read from this discussion




          /usr/lib/ubuntu-release-upgrader/release-upgrade-motd actually calls /usr/lib/ubuntu-release-upgrader/check-new-release.
          If you run /usr/lib/ubuntu-release-upgrader/check-new-release, that's the script that fails with the error message.




          some other user fixed the issue running




          All I did to make it go away was: sudo rm /var/lib/ubuntu-release-upgrader/release-upgrade-available




          The same problem was experienced with 17.10




          The script will only update the file every 24 hours. So if you wait long enough, the file will go stale and the script will update the file anyway. But,if you want to update it immediately, just remove /var/lib/ubuntu-release-upgrader/release-upgrade-available and run /etc/update-motd.d/91-release-upgrade and it should start working correctly.




          Happy to help you further






          share|improve this answer
























          • Thanks Fabrizio. Unfortunately that didn't work. The same issues remain. BTW per above I've already tried removing the release-upgrade-available file. Thank you anyway.

            – ChrisFNZ
            2 hours ago
















          0














          as I read from this discussion




          /usr/lib/ubuntu-release-upgrader/release-upgrade-motd actually calls /usr/lib/ubuntu-release-upgrader/check-new-release.
          If you run /usr/lib/ubuntu-release-upgrader/check-new-release, that's the script that fails with the error message.




          some other user fixed the issue running




          All I did to make it go away was: sudo rm /var/lib/ubuntu-release-upgrader/release-upgrade-available




          The same problem was experienced with 17.10




          The script will only update the file every 24 hours. So if you wait long enough, the file will go stale and the script will update the file anyway. But,if you want to update it immediately, just remove /var/lib/ubuntu-release-upgrader/release-upgrade-available and run /etc/update-motd.d/91-release-upgrade and it should start working correctly.




          Happy to help you further






          share|improve this answer
























          • Thanks Fabrizio. Unfortunately that didn't work. The same issues remain. BTW per above I've already tried removing the release-upgrade-available file. Thank you anyway.

            – ChrisFNZ
            2 hours ago














          0












          0








          0







          as I read from this discussion




          /usr/lib/ubuntu-release-upgrader/release-upgrade-motd actually calls /usr/lib/ubuntu-release-upgrader/check-new-release.
          If you run /usr/lib/ubuntu-release-upgrader/check-new-release, that's the script that fails with the error message.




          some other user fixed the issue running




          All I did to make it go away was: sudo rm /var/lib/ubuntu-release-upgrader/release-upgrade-available




          The same problem was experienced with 17.10




          The script will only update the file every 24 hours. So if you wait long enough, the file will go stale and the script will update the file anyway. But,if you want to update it immediately, just remove /var/lib/ubuntu-release-upgrader/release-upgrade-available and run /etc/update-motd.d/91-release-upgrade and it should start working correctly.




          Happy to help you further






          share|improve this answer













          as I read from this discussion




          /usr/lib/ubuntu-release-upgrader/release-upgrade-motd actually calls /usr/lib/ubuntu-release-upgrader/check-new-release.
          If you run /usr/lib/ubuntu-release-upgrader/check-new-release, that's the script that fails with the error message.




          some other user fixed the issue running




          All I did to make it go away was: sudo rm /var/lib/ubuntu-release-upgrader/release-upgrade-available




          The same problem was experienced with 17.10




          The script will only update the file every 24 hours. So if you wait long enough, the file will go stale and the script will update the file anyway. But,if you want to update it immediately, just remove /var/lib/ubuntu-release-upgrader/release-upgrade-available and run /etc/update-motd.d/91-release-upgrade and it should start working correctly.




          Happy to help you further







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 8 hours ago









          Fabrizio BertoglioFabrizio Bertoglio

          318




          318













          • Thanks Fabrizio. Unfortunately that didn't work. The same issues remain. BTW per above I've already tried removing the release-upgrade-available file. Thank you anyway.

            – ChrisFNZ
            2 hours ago



















          • Thanks Fabrizio. Unfortunately that didn't work. The same issues remain. BTW per above I've already tried removing the release-upgrade-available file. Thank you anyway.

            – ChrisFNZ
            2 hours ago

















          Thanks Fabrizio. Unfortunately that didn't work. The same issues remain. BTW per above I've already tried removing the release-upgrade-available file. Thank you anyway.

          – ChrisFNZ
          2 hours ago





          Thanks Fabrizio. Unfortunately that didn't work. The same issues remain. BTW per above I've already tried removing the release-upgrade-available file. Thank you anyway.

          – ChrisFNZ
          2 hours ago










          ChrisFNZ is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          ChrisFNZ is a new contributor. Be nice, and check out our Code of Conduct.













          ChrisFNZ is a new contributor. Be nice, and check out our Code of Conduct.












          ChrisFNZ is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1138586%2ftrying-to-upgrade-ubuntu-from-18-04-to-18-10-and-then-19-04%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

          Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

          Should I use Docker or LXD?How to cache (more) data on SSD/RAM to avoid spin up?Unable to get Windows File...