• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved Error while updating

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...
 
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...
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
 
Back
Top