Ubuntu Upgrade 16.04 -> 16.10 Fails with Forbidden IP Error
-
Hmmm... it might be that the file is missing from that mirror, but that alone would not give a 403 error.
-
This was the issue I believe I spent quite a bit of time on.
Solution. Forget it,... In my case it was a VM - and was the UniFi Controller. I made a back up, and started fresh.
However - You may not have that option.
-
@gjacobse I think in this case it's definitely doable for me to just start from scratch. It's a small web app that could be migrated easily but I was hoping to have this easy one to test the upgrade process before I moved on to some of the more complicated VM where doing a backup/restore is a bigger deal.
I'll keep poking at this one for a while and see if I can figure out why it's failing before giving up and moving to starting from scratch.
-
Do you have some sort of proxy?
Have you tried just doingapt-get upgraderather than do-release-upgrade? -
@momurda said in Ubuntu Upgrade 16.04 -> 16.10 Fails with Forbidden IP Error:
Do you have some sort of proxy?
Have you tried just doingapt-get upgraderather than do-release-upgrade?I did not think that upgrades from 16.04 to 16.10.
-
@JaredBusch
right, just to see if it can do updates at all or if it is only distribution upgrade that is failing -
@momurda Yes, I was able to successfully run sudo apt-get update and sudo apt-get upgrade without any issues so I'm sure it isn't a connectivity issue on this end.
-
Just summarizing this guide here. (assuming you don't want to be on the development release I've omitted it)
sudo apt update
sudo apt dist-upgrade
sudo apt-get install update-manager-core
sudo nano /etc/upgrade-manager/release-upgradesprompt=normalsudo do-release-upgradeShould do it for you.
-
@DustinB3403 said in Ubuntu Upgrade 16.04 -> 16.10 Fails with Forbidden IP Error:
Just summarizing this guide here. (assuming you don't want to be on the development release I've omitted it)
sudo apt update
sudo apt dist-upgrade
sudo apt-get install update-manager-core
sudo nano /etc/upgrade-manager/release-upgradesprompt=normalsudo do-release-upgradeShould do it for you.
Sadly, those are exactly the steps I've taken which got me to this point.
-
@NashBrydges Were you running the development version of 16.04 before?
-
@DustinB3403 16.04 LTS.
-
@NashBrydges said in Ubuntu Upgrade 16.04 -> 16.10 Fails with Forbidden IP Error:
@DustinB3403 16.04 LTS.
That's the first you mentioned LTS, and this is likely the culprit. The 16.10 upgrade isn't going to be in the repo's for 16.04 LTS.
-
@NashBrydges Try the steps outlined here for upgrading from LTS.
-
@DustinB3403 said in Ubuntu Upgrade 16.04 -> 16.10 Fails with Forbidden IP Error:
@NashBrydges Try the steps outlined here for upgrading from LTS.
Those are the exact same steps you've listed a few posts above. That's the process I followed where I got the error.
-
@DustinB3403 said in Ubuntu Upgrade 16.04 -> 16.10 Fails with Forbidden IP Error:
@NashBrydges said in Ubuntu Upgrade 16.04 -> 16.10 Fails with Forbidden IP Error:
@DustinB3403 16.04 LTS.
That's the first you mentioned LTS, and this is likely the culprit. The 16.10 upgrade isn't going to be in the repo's for 16.04 LTS.
Ummmm what? That is the point of telling it to use normal and not LTS.....
Also 16.04 is LTS in all versions whether you upgraded to it or installed it orgiinally.
-
@JaredBusch said in Ubuntu Upgrade 16.04 -> 16.10 Fails with Forbidden IP Error:
@DustinB3403 said in Ubuntu Upgrade 16.04 -> 16.10 Fails with Forbidden IP Error:
@NashBrydges said in Ubuntu Upgrade 16.04 -> 16.10 Fails with Forbidden IP Error:
@DustinB3403 16.04 LTS.
That's the first you mentioned LTS, and this is likely the culprit. The 16.10 upgrade isn't going to be in the repo's for 16.04 LTS.
Also 16.04 is LTS in all versions whether you upgraded to it or installed it orgiinally.
This I didn't realize, I thought there was a 16.04 and a 16.04 LTS my bad.
-
The 403 error is the issue. This is definitely something to do with the site not allowing the connection. The upgrade process itself is not moving forward because it cannot get the file(s) that it needs.
-
I've reversed the IP: yukinko.canonical.com.
I've accessed it via ftp on google chrome and everything seems in place. via ftp I'm also able to download the tar, here.
maybe they have fixed something in the while? -
@matteo-nunziati
That is interesting, ftp works but not http
He could try changing apt to use ftp instead of http in sources.list
