• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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