sudo apt update error: “Release file is not yet valid”
1
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 '18 at 2:47
zx485
1,45231114
asked Nov 28 '18 at 20:58
Rohan ChaudhariRohan Chaudhari
61
add a comment |
1
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 '18 at 2:47
zx485
1,45231114
asked Nov 28 '18 at 20:58
Rohan ChaudhariRohan 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 '18 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 '18 at 15:05
add a comment |
1
1
1
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 '18 at 2:47
zx485
1,45231114
asked Nov 28 '18 at 20:58
Rohan ChaudhariRohan 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 '18 at 2:47
zx485
1,45231114
asked Nov 28 '18 at 20:58
Rohan ChaudhariRohan Chaudhari
61
edited Nov 29 '18 at 2:47
zx485
1,45231114
asked Nov 28 '18 at 20:58
Rohan ChaudhariRohan Chaudhari
61
edited Nov 29 '18 at 2:47
zx485
1,45231114
edited Nov 29 '18 at 2:47
zx485
1,45231114
edited Nov 29 '18 at 2:47
zx485
1,45231114
1,45231114
asked Nov 28 '18 at 20:58
Rohan ChaudhariRohan Chaudhari
61
asked Nov 28 '18 at 20:58
Rohan ChaudhariRohan Chaudhari
61
asked Nov 28 '18 at 20:58
Rohan ChaudhariRohan 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 at 15:05
add a comment |
1 Answer
1
active
oldest
votes
0
Tested on ubuntu 18.04 server:
- check BIOS date-time, check also the coin cell in the motherboard and replace if needed.
- restart. Execute command
dateto verify that date time is correct. - execute
sudo apt updateagain. Problems are gone.
answered Jan 23 at 17:11
AngelitoAngelito
1
add a comment |
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
});
}
});
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
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
Tested on ubuntu 18.04 server:
- check BIOS date-time, check also the coin cell in the motherboard and replace if needed.
- restart. Execute command
dateto verify that date time is correct. - execute
sudo apt updateagain. Problems are gone.
answered Jan 23 at 17:11
AngelitoAngelito
1
add a comment |
0
Tested on ubuntu 18.04 server:
- check BIOS date-time, check also the coin cell in the motherboard and replace if needed.
- restart. Execute command
dateto verify that date time is correct. - execute
sudo apt updateagain. Problems are gone.
answered Jan 23 at 17:11
AngelitoAngelito
1
add a comment |
0
0
0
Tested on ubuntu 18.04 server:
- check BIOS date-time, check also the coin cell in the motherboard and replace if needed.
- restart. Execute command
dateto verify that date time is correct. - execute
sudo apt updateagain. Problems are gone.
answered Jan 23 at 17:11
AngelitoAngelito
1
Tested on ubuntu 18.04 server:
- check BIOS date-time, check also the coin cell in the motherboard and replace if needed.
- restart. Execute command
dateto verify that date time is correct. - execute
sudo apt updateagain. Problems are gone.
answered Jan 23 at 17:11
AngelitoAngelito
1
answered Jan 23 at 17:11
AngelitoAngelito
1
answered Jan 23 at 17:11
AngelitoAngelito
1
answered Jan 23 at 17:11
AngelitoAngelito
1
1
add a comment |
add a comment |
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.
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 '18 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 '18 at 15:05