sudo apt update error: “Release file is not yet valid”
up vote
1
down vote
favorite
I keep getting this error every time I try to sudo apt update:
Hit:1 ubuntu bionic InRelease
Ign:3 linux/chrome/deb stable InRelease
Get:2 /ubuntu bionic-updates InRelease [88.7 kB]
Get:5 /linux/chrome/deb stable Release [943 B]
Get:6 http://dl.google.com/linux/chrome/deb stable Release.gpg [819 B]
Get:4 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:7 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
Reading package lists... Done
E: Release file for http://dl.google.com/linux/chrome/deb/dists/stable/Release is not valid yet (invalid for another 2h 45min 28s). Updates for this repository will not be applied.
E: Release file for http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease is not valid yet (invalid for another 4h 34min 33s). Updates for this repository will not be applied.
E: Release file for http://us.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease is not valid yet (invalid for another 1h 22min 16s). Updates for this repository will not be applied.
E: Release file for http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease is not valid yet (invalid for another 4h 32min 36s).
Updates for this repository will not be applied.
I've reset my timezone to UTC, but that didn't work.
I also found a different answer where they said I should try
sudo apt-get -o Acquire::Check-Valid-Until=false update
but that didn't work either.
I got the same error both times.
apt updates
edited Nov 29 at 2:47
zx485
1,45231114
asked Nov 28 at 20:58
Rohan Chaudhari
61
add a comment |
up vote
1
down vote
favorite
I keep getting this error every time I try to sudo apt update:
Hit:1 ubuntu bionic InRelease
Ign:3 linux/chrome/deb stable InRelease
Get:2 /ubuntu bionic-updates InRelease [88.7 kB]
Get:5 /linux/chrome/deb stable Release [943 B]
Get:6 http://dl.google.com/linux/chrome/deb stable Release.gpg [819 B]
Get:4 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:7 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
Reading package lists... Done
E: Release file for http://dl.google.com/linux/chrome/deb/dists/stable/Release is not valid yet (invalid for another 2h 45min 28s). Updates for this repository will not be applied.
E: Release file for http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease is not valid yet (invalid for another 4h 34min 33s). Updates for this repository will not be applied.
E: Release file for http://us.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease is not valid yet (invalid for another 1h 22min 16s). Updates for this repository will not be applied.
E: Release file for http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease is not valid yet (invalid for another 4h 32min 36s).
Updates for this repository will not be applied.
I've reset my timezone to UTC, but that didn't work.
I also found a different answer where they said I should try
sudo apt-get -o Acquire::Check-Valid-Until=false update
but that didn't work either.
I got the same error both times.
apt updates
edited Nov 29 at 2:47
zx485
1,45231114
asked Nov 28 at 20:58
Rohan Chaudhari
61
1
Did you compare your current timestamp against the actual UTC time? Do you dual boot? Have you done a time sync up yet to make sure your computer clock is in sync? If you dual boot, it's possible Windows has altered the system clock (also check the time zone in your desktop settings)
– Thomas Ward♦
Nov 28 at 21:04
I dual boot with Windows 10 home and I just time-synced to make ubuntu use local time. Tried updating again but it's still the exact same error unfortunately. Any ideas?
– Rohan Chaudhari
Nov 29 at 15:05
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I keep getting this error every time I try to sudo apt update:
Hit:1 ubuntu bionic InRelease
Ign:3 linux/chrome/deb stable InRelease
Get:2 /ubuntu bionic-updates InRelease [88.7 kB]
Get:5 /linux/chrome/deb stable Release [943 B]
Get:6 http://dl.google.com/linux/chrome/deb stable Release.gpg [819 B]
Get:4 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:7 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
Reading package lists... Done
E: Release file for http://dl.google.com/linux/chrome/deb/dists/stable/Release is not valid yet (invalid for another 2h 45min 28s). Updates for this repository will not be applied.
E: Release file for http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease is not valid yet (invalid for another 4h 34min 33s). Updates for this repository will not be applied.
E: Release file for http://us.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease is not valid yet (invalid for another 1h 22min 16s). Updates for this repository will not be applied.
E: Release file for http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease is not valid yet (invalid for another 4h 32min 36s).
Updates for this repository will not be applied.
I've reset my timezone to UTC, but that didn't work.
I also found a different answer where they said I should try
sudo apt-get -o Acquire::Check-Valid-Until=false update
but that didn't work either.
I got the same error both times.
apt updates
edited Nov 29 at 2:47
zx485
1,45231114
asked Nov 28 at 20:58
Rohan Chaudhari
61
I keep getting this error every time I try to sudo apt update:
Hit:1 ubuntu bionic InRelease
Ign:3 linux/chrome/deb stable InRelease
Get:2 /ubuntu bionic-updates InRelease [88.7 kB]
Get:5 /linux/chrome/deb stable Release [943 B]
Get:6 http://dl.google.com/linux/chrome/deb stable Release.gpg [819 B]
Get:4 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:7 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
Reading package lists... Done
E: Release file for http://dl.google.com/linux/chrome/deb/dists/stable/Release is not valid yet (invalid for another 2h 45min 28s). Updates for this repository will not be applied.
E: Release file for http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease is not valid yet (invalid for another 4h 34min 33s). Updates for this repository will not be applied.
E: Release file for http://us.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease is not valid yet (invalid for another 1h 22min 16s). Updates for this repository will not be applied.
E: Release file for http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease is not valid yet (invalid for another 4h 32min 36s).
Updates for this repository will not be applied.
I've reset my timezone to UTC, but that didn't work.
I also found a different answer where they said I should try
sudo apt-get -o Acquire::Check-Valid-Until=false update
but that didn't work either.
I got the same error both times.
apt updates
apt updates
edited Nov 29 at 2:47
zx485
1,45231114
asked Nov 28 at 20:58
Rohan Chaudhari
61
edited Nov 29 at 2:47
zx485
1,45231114
asked Nov 28 at 20:58
Rohan Chaudhari
61
edited Nov 29 at 2:47
zx485
1,45231114
edited Nov 29 at 2:47
zx485
1,45231114
edited Nov 29 at 2:47
zx485
1,45231114
1,45231114
asked Nov 28 at 20:58
Rohan Chaudhari
61
asked Nov 28 at 20:58
Rohan Chaudhari
61
asked Nov 28 at 20:58
Rohan Chaudhari
61
61
1
Did you compare your current timestamp against the actual UTC time? Do you dual boot? Have you done a time sync up yet to make sure your computer clock is in sync? If you dual boot, it's possible Windows has altered the system clock (also check the time zone in your desktop settings)
– Thomas Ward♦
Nov 28 at 21:04
I dual boot with Windows 10 home and I just time-synced to make ubuntu use local time. Tried updating again but it's still the exact same error unfortunately. Any ideas?
– Rohan Chaudhari
Nov 29 at 15:05
add a comment |
1
Did you compare your current timestamp against the actual UTC time? Do you dual boot? Have you done a time sync up yet to make sure your computer clock is in sync? If you dual boot, it's possible Windows has altered the system clock (also check the time zone in your desktop settings)
– Thomas Ward♦
Nov 28 at 21:04
I dual boot with Windows 10 home and I just time-synced to make ubuntu use local time. Tried updating again but it's still the exact same error unfortunately. Any ideas?
– Rohan Chaudhari
Nov 29 at 15:05
1
1
Did you compare your current timestamp against the actual UTC time? Do you dual boot? Have you done a time sync up yet to make sure your computer clock is in sync? If you dual boot, it's possible Windows has altered the system clock (also check the time zone in your desktop settings)
– Thomas Ward♦
Nov 28 at 21:04
Did you compare your current timestamp against the actual UTC time? Do you dual boot? Have you done a time sync up yet to make sure your computer clock is in sync? If you dual boot, it's possible Windows has altered the system clock (also check the time zone in your desktop settings)
– Thomas Ward♦
Nov 28 at 21:04
I dual boot with Windows 10 home and I just time-synced to make ubuntu use local time. Tried updating again but it's still the exact same error unfortunately. Any ideas?
– Rohan Chaudhari
Nov 29 at 15:05
I dual boot with Windows 10 home and I just time-synced to make ubuntu use local time. Tried updating again but it's still the exact same error unfortunately. Any ideas?
– Rohan Chaudhari
Nov 29 at 15:05
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1096930%2fsudo-apt-update-error-release-file-is-not-yet-valid%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
1
Did you compare your current timestamp against the actual UTC time? Do you dual boot? Have you done a time sync up yet to make sure your computer clock is in sync? If you dual boot, it's possible Windows has altered the system clock (also check the time zone in your desktop settings)
– Thomas Ward♦
Nov 28 at 21:04
I dual boot with Windows 10 home and I just time-synced to make ubuntu use local time. Tried updating again but it's still the exact same error unfortunately. Any ideas?
– Rohan Chaudhari
Nov 29 at 15:05