Error updating Ubuntu Server from 16.04.1 LTS to 18.04.1 LTS [closed]
Clash Royale CLAN TAG#URR8PPP up vote
-1
down vote
favorite
I'm trying to update an Ubuntu Server 16.04.1 LTS to 18.04.1 LTS.
I've updated/upgraded everything before starting the migration progress with:
sudo do-release-upgrade -d
which I've already run successfully on other servers.
BTW, it's blocking somewhere in the middle, stating that:
Failed to fetch
http://security.ubuntu.com/ubuntu/pool/universe/w/webkit2gtk/libwebkit2gtk-4.0-37-gtk2_2.20.2-0ubuntu0.18.04.1_amd64.deb
Connessione non riuscita [IP: 91.189.91.23 80]
("Connessione non riuscita" means "Can't connect to")
The port is open, the IP is reachable, the telnet on port 80 is ok:
telnet 91.189.91.23 80
Trying 91.189.91.23...
Connected to 91.189.91.23.
Escape character is '^]'.
What could be the culprit?
Should I disable other PPAs as described in this answer?
apt server upgrade updates 18.04
edited May 17 at 18:03
Zanna
47.9k13119227
asked May 10 at 12:42
Andrea Ligios
6110
closed as off-topic by user535733, N0rbert, David Foerster, Zanna, Kevin Bowen May 18 at 5:12
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – user535733, N0rbert, David Foerster, Zanna, Kevin Bowen
add a comment |Â
up vote
-1
down vote
favorite
I'm trying to update an Ubuntu Server 16.04.1 LTS to 18.04.1 LTS.
I've updated/upgraded everything before starting the migration progress with:
sudo do-release-upgrade -d
which I've already run successfully on other servers.
BTW, it's blocking somewhere in the middle, stating that:
Failed to fetch
http://security.ubuntu.com/ubuntu/pool/universe/w/webkit2gtk/libwebkit2gtk-4.0-37-gtk2_2.20.2-0ubuntu0.18.04.1_amd64.deb
Connessione non riuscita [IP: 91.189.91.23 80]
("Connessione non riuscita" means "Can't connect to")
The port is open, the IP is reachable, the telnet on port 80 is ok:
telnet 91.189.91.23 80
Trying 91.189.91.23...
Connected to 91.189.91.23.
Escape character is '^]'.
What could be the culprit?
Should I disable other PPAs as described in this answer?
apt server upgrade updates 18.04
edited May 17 at 18:03
Zanna
47.9k13119227
asked May 10 at 12:42
Andrea Ligios
6110
closed as off-topic by user535733, N0rbert, David Foerster, Zanna, Kevin Bowen May 18 at 5:12
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – user535733, N0rbert, David Foerster, Zanna, Kevin Bowen
Why are you asking should you do what you've already found as the answer?
– L. D. James
May 10 at 15:57
@L.D.James the error was different, and I've somehow fixed it without doing what described in that answer :|
– Andrea Ligios
May 10 at 16:40
Great! Glad you were able to resolve your problem. Can share the solution, either by accepting the answer that resolved the issue, or adding an answer yourself so that others with a similar issue can easier find solutions.
– L. D. James
May 10 at 16:44
@L.D.James I've already did it (before getting any comment and answer :) Unluckily, it's not an answer that satisfies me, because I've not understood what's happened... probably some kind of "network problem" or whatever. BTW I've solved that way, maybe it'll help someone. Cheers
– Andrea Ligios
May 11 at 9:00
add a comment |Â
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I'm trying to update an Ubuntu Server 16.04.1 LTS to 18.04.1 LTS.
I've updated/upgraded everything before starting the migration progress with:
sudo do-release-upgrade -d
which I've already run successfully on other servers.
BTW, it's blocking somewhere in the middle, stating that:
Failed to fetch
http://security.ubuntu.com/ubuntu/pool/universe/w/webkit2gtk/libwebkit2gtk-4.0-37-gtk2_2.20.2-0ubuntu0.18.04.1_amd64.deb
Connessione non riuscita [IP: 91.189.91.23 80]
("Connessione non riuscita" means "Can't connect to")
The port is open, the IP is reachable, the telnet on port 80 is ok:
telnet 91.189.91.23 80
Trying 91.189.91.23...
Connected to 91.189.91.23.
Escape character is '^]'.
What could be the culprit?
Should I disable other PPAs as described in this answer?
apt server upgrade updates 18.04
edited May 17 at 18:03
Zanna
47.9k13119227
asked May 10 at 12:42
Andrea Ligios
6110
I'm trying to update an Ubuntu Server 16.04.1 LTS to 18.04.1 LTS.
I've updated/upgraded everything before starting the migration progress with:
sudo do-release-upgrade -d
which I've already run successfully on other servers.
BTW, it's blocking somewhere in the middle, stating that:
Failed to fetch
http://security.ubuntu.com/ubuntu/pool/universe/w/webkit2gtk/libwebkit2gtk-4.0-37-gtk2_2.20.2-0ubuntu0.18.04.1_amd64.deb
Connessione non riuscita [IP: 91.189.91.23 80]
("Connessione non riuscita" means "Can't connect to")
The port is open, the IP is reachable, the telnet on port 80 is ok:
telnet 91.189.91.23 80
Trying 91.189.91.23...
Connected to 91.189.91.23.
Escape character is '^]'.
What could be the culprit?
Should I disable other PPAs as described in this answer?
apt server upgrade updates 18.04
edited May 17 at 18:03
Zanna
47.9k13119227
asked May 10 at 12:42
Andrea Ligios
6110
edited May 17 at 18:03
Zanna
47.9k13119227
edited May 17 at 18:03
Zanna
47.9k13119227
edited May 17 at 18:03
Zanna
47.9k13119227
47.9k13119227
asked May 10 at 12:42
Andrea Ligios
6110
asked May 10 at 12:42
Andrea Ligios
6110
asked May 10 at 12:42
Andrea Ligios
6110
6110
closed as off-topic by user535733, N0rbert, David Foerster, Zanna, Kevin Bowen May 18 at 5:12
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – user535733, N0rbert, David Foerster, Zanna, Kevin Bowen
closed as off-topic by user535733, N0rbert, David Foerster, Zanna, Kevin Bowen May 18 at 5:12
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – user535733, N0rbert, David Foerster, Zanna, Kevin Bowen
Why are you asking should you do what you've already found as the answer?
– L. D. James
May 10 at 15:57
@L.D.James the error was different, and I've somehow fixed it without doing what described in that answer :|
– Andrea Ligios
May 10 at 16:40
Great! Glad you were able to resolve your problem. Can share the solution, either by accepting the answer that resolved the issue, or adding an answer yourself so that others with a similar issue can easier find solutions.
– L. D. James
May 10 at 16:44
@L.D.James I've already did it (before getting any comment and answer :) Unluckily, it's not an answer that satisfies me, because I've not understood what's happened... probably some kind of "network problem" or whatever. BTW I've solved that way, maybe it'll help someone. Cheers
– Andrea Ligios
May 11 at 9:00
add a comment |Â
Why are you asking should you do what you've already found as the answer?
– L. D. James
May 10 at 15:57
@L.D.James the error was different, and I've somehow fixed it without doing what described in that answer :|
– Andrea Ligios
May 10 at 16:40
Great! Glad you were able to resolve your problem. Can share the solution, either by accepting the answer that resolved the issue, or adding an answer yourself so that others with a similar issue can easier find solutions.
– L. D. James
May 10 at 16:44
@L.D.James I've already did it (before getting any comment and answer :) Unluckily, it's not an answer that satisfies me, because I've not understood what's happened... probably some kind of "network problem" or whatever. BTW I've solved that way, maybe it'll help someone. Cheers
– Andrea Ligios
May 11 at 9:00
Why are you asking should you do what you've already found as the answer?
– L. D. James
May 10 at 15:57
Why are you asking should you do what you've already found as the answer?
– L. D. James
May 10 at 15:57
@L.D.James the error was different, and I've somehow fixed it without doing what described in that answer :|
– Andrea Ligios
May 10 at 16:40
@L.D.James the error was different, and I've somehow fixed it without doing what described in that answer :|
– Andrea Ligios
May 10 at 16:40
Great! Glad you were able to resolve your problem. Can share the solution, either by accepting the answer that resolved the issue, or adding an answer yourself so that others with a similar issue can easier find solutions.
– L. D. James
May 10 at 16:44
Great! Glad you were able to resolve your problem. Can share the solution, either by accepting the answer that resolved the issue, or adding an answer yourself so that others with a similar issue can easier find solutions.
– L. D. James
May 10 at 16:44
@L.D.James I've already did it (before getting any comment and answer :) Unluckily, it's not an answer that satisfies me, because I've not understood what's happened... probably some kind of "network problem" or whatever. BTW I've solved that way, maybe it'll help someone. Cheers
– Andrea Ligios
May 11 at 9:00
@L.D.James I've already did it (before getting any comment and answer :) Unluckily, it's not an answer that satisfies me, because I've not understood what's happened... probably some kind of "network problem" or whatever. BTW I've solved that way, maybe it'll help someone. Cheers
– Andrea Ligios
May 11 at 9:00
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
1
down vote
accepted
After the nth retry, I've run
sudo apt-get dist-upgrade
and it completed the migration to 18.04 :|
I still don't know what happened.
answered May 10 at 13:11
Andrea Ligios
6110
add a comment |Â
up vote
1
down vote
Disable all PPA and Make sure that sourcelist /etc/apt/source.list contains only official repositories.
In Some cases if you are using firewall which block specific words in domain can block particular package from downloading ,you will stuck with that. Make sure that you allow traffic from that domain or you can whitelist particular URL.
answered May 10 at 13:16
Ketankumar Patel
9,66684364
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
After the nth retry, I've run
sudo apt-get dist-upgrade
and it completed the migration to 18.04 :|
I still don't know what happened.
answered May 10 at 13:11
Andrea Ligios
6110
add a comment |Â
up vote
1
down vote
accepted
After the nth retry, I've run
sudo apt-get dist-upgrade
and it completed the migration to 18.04 :|
I still don't know what happened.
answered May 10 at 13:11
Andrea Ligios
6110
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
After the nth retry, I've run
sudo apt-get dist-upgrade
and it completed the migration to 18.04 :|
I still don't know what happened.
answered May 10 at 13:11
Andrea Ligios
6110
After the nth retry, I've run
sudo apt-get dist-upgrade
and it completed the migration to 18.04 :|
I still don't know what happened.
answered May 10 at 13:11
Andrea Ligios
6110
answered May 10 at 13:11
Andrea Ligios
6110
answered May 10 at 13:11
Andrea Ligios
6110
answered May 10 at 13:11
Andrea Ligios
6110
6110
add a comment |Â
add a comment |Â
up vote
1
down vote
Disable all PPA and Make sure that sourcelist /etc/apt/source.list contains only official repositories.
In Some cases if you are using firewall which block specific words in domain can block particular package from downloading ,you will stuck with that. Make sure that you allow traffic from that domain or you can whitelist particular URL.
answered May 10 at 13:16
Ketankumar Patel
9,66684364
add a comment |Â
up vote
1
down vote
Disable all PPA and Make sure that sourcelist /etc/apt/source.list contains only official repositories.
In Some cases if you are using firewall which block specific words in domain can block particular package from downloading ,you will stuck with that. Make sure that you allow traffic from that domain or you can whitelist particular URL.
answered May 10 at 13:16
Ketankumar Patel
9,66684364
add a comment |Â
up vote
1
down vote
up vote
1
down vote
Disable all PPA and Make sure that sourcelist /etc/apt/source.list contains only official repositories.
In Some cases if you are using firewall which block specific words in domain can block particular package from downloading ,you will stuck with that. Make sure that you allow traffic from that domain or you can whitelist particular URL.
answered May 10 at 13:16
Ketankumar Patel
9,66684364
Disable all PPA and Make sure that sourcelist /etc/apt/source.list contains only official repositories.
In Some cases if you are using firewall which block specific words in domain can block particular package from downloading ,you will stuck with that. Make sure that you allow traffic from that domain or you can whitelist particular URL.
answered May 10 at 13:16
Ketankumar Patel
9,66684364
edited May 10 at 13:22
answered May 10 at 13:16
Ketankumar Patel
9,66684364
answered May 10 at 13:16
Ketankumar Patel
9,66684364
answered May 10 at 13:16
Ketankumar Patel
9,66684364
9,66684364
add a comment |Â
add a comment |Â
Why are you asking should you do what you've already found as the answer?
– L. D. James
May 10 at 15:57
@L.D.James the error was different, and I've somehow fixed it without doing what described in that answer :|
– Andrea Ligios
May 10 at 16:40
Great! Glad you were able to resolve your problem. Can share the solution, either by accepting the answer that resolved the issue, or adding an answer yourself so that others with a similar issue can easier find solutions.
– L. D. James
May 10 at 16:44
@L.D.James I've already did it (before getting any comment and answer :) Unluckily, it's not an answer that satisfies me, because I've not understood what's happened... probably some kind of "network problem" or whatever. BTW I've solved that way, maybe it'll help someone. Cheers
– Andrea Ligios
May 11 at 9:00