• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Error while updating

Dirk

Dirk

Basic Pleskian
Hi,

I keep getting this error message from plesk.
Could someone please give me a hint what to do? I read the message several times, but still don't know where to start :-(


Grund: 2019-11-17 03:45:20 INFO: pum is called with arguments: ['--update', '--json']
2019-11-17 03:45:23 ERROR: W:The repository 'Atomicorp xenial Release' does not have a Release file., W: Data from such a repository can't be authenticated and is therefore potentially dangerous to use., W:See apt-secure(8) manpage for repository creation and user configuration details., E:Failed to fetch http://updates.atomicorp.com/channels/tortix-common/debian/dists/xenial/main/binary-amd64/Packages 404 Not Found [IP: 46.105.121.84 80], E:Some index files failed to download. They have been ignored, or old ones used instead.
2019-11-17 03:45:23 ERROR: Exited with returncode 1.
 
This looks like an error in the Atomicorp repository configuration.

Their server seems to only work over https, while the repository configuration calls for a plain http conncetion.

As a first step I suggest altering the repository configuration on your side. When the updates start flowing again, see if this was perhaps fixed in a later repository update, if not, research further...
 
Ales said:
This looks like an error in the Atomicorp repository configuration.

Their server seems to only work over https, while the repository configuration calls for a plain http conncetion.

As a first step I suggest altering the repository configuration on your side. When the updates start flowing again, see if this was perhaps fixed in a later repository update, if not, research further...
Click to expand...
NO WAY!!! :)
I knew it had to be something simple...
Thanks for pointing me into the right direction. I simply changed:
deb http://updates.atomicorp.com/channels/tortix-common/debian xenial main
to
deb https://updates.atomicorp.com/channels/tortix-common/debian xenial main
in etc/apt/sources.list

Let's see if it will work this way next time - but I am pretty sure that it will.
Thank you, Ales
 
You must log in or register to reply here.

Similar threads

W
Issue Atomicorp repository - Debian 11 - NO_PUBKEY
Replies
2
Views
433
websb
W
N
Question Cannot update to 18.0.64
Replies
3
Views
680
Maarten
M
K
Issue centos2alma error
Replies
6
Views
991
kevinjansen
K
T
Issue Some problems occurred with the System Updates tool while installing new versions of system packages and third-party components
Replies
5
Views
1K
Sebahat.hadzhi
Sebahat.hadzhi
abanico
Resolved Error updating packages
Replies
11
Views
1K
marlon006
M
Back
Top