[SOLVED] Update issue from enterprise repo

[Shaaarnir]

We have subscriptions on 4 servers.
After 2021-01-06 we have issues with update.
The two servers have updated normally with "apt update" and no issues.
On other two servers I see errors:

Err:7 https://enterprise.proxmox.com/debian buster InRelease
401 Unauthorized [IP: 212.224.123.70 443]
Reading package lists...
E: Failed to fetch https://enterprise.proxmox.com/debian/dists/buster/InRelease 401 Unauthorized [IP: 212.224.123.70 443]
E: The repository 'https://enterprise.proxmox.com/debian buster InRelease' is not signed.
TASK ERROR: command 'apt-get update' failed: exit code 100

Can you help me with this?
Which information do you need for understand how resolving it?

 

[Moayad]

Hi,

could you please post the output of the following command
grep '' /etc/apt/sources.list.d/*
and full output of apt update as well

 

[tom]

Can you help me with this?

If you have issues with your subscription keys, please get in touch with the reseller and tell them which key has issues.

 

[Shaaarnir]

It is done.
Below you can find it.

/etc/apt/sources.list.d/*

# grep '' /etc/apt/sources.list.d/*
/etc/apt/sources.list.d/megacli.list:## LSI MegaCLI
/etc/apt/sources.list.d/megacli.list:deb http://hwraid.le-vert.net/debian buster main
/etc/apt/sources.list.d/pve-enterprise.list:deb https://enterprise.proxmox.com/debian buster pve-enterprise
/etc/apt/sources.list.d/pve-no-subscription.list:#deb http://download.proxmox.com/debian/pve buster pve-no-subscription
/etc/apt/sources.list.d/zabbix.list:deb http://repo.zabbix.com/zabbix/5.0/debian buster main
/etc/apt/sources.list.d/zabbix.list:deb-src http://repo.zabbix.com/zabbix/5.0/debian buster main

# apt update
Ign:1 http://hwraid.le-vert.net/debian buster InRelease
Hit:2 http://hwraid.le-vert.net/debian buster Release                                                                                                           
Err:3 https://enterprise.proxmox.com/debian buster InRelease                                                                                                     
  401  Unauthorized [IP: 212.224.123.70 443]
Hit:4 http://security.debian.org buster/updates InRelease                                                                                                       
Hit:5 http://ftp.debian.org/debian buster InRelease                                                                                                             
Hit:7 http://repo.zabbix.com/zabbix/5.0/debian buster InRelease
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/dists/buster/InRelease  401  Unauthorized [IP: 212.224.123.70 443]
E: The repository 'https://enterprise.proxmox.com/debian buster InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

 

[Shaaarnir]

If you have issues with your subscription keys, please get in touch with the reseller and tell them which key has issues.

How can I check it?
I don't see any issues with the Subscription tab.

 

[tom]

You need to tell us your key, but yes, do not post this in the forum, please contact your reseller so the key can be checked.

 

[Shaaarnir]

You need to tell us your key, but yes, do not post this in the forum, please contact your reseller so the key can be checked.

I contacted with our reseller. He regenerated my keys with issues. But it didn't help me.
I still see errors:

E: Failed to fetch https://enterprise.proxmox.com/debian/dists/buster/InRelease  401  Unauthorized [IP: 144.217.225.162 443]
E: The repository 'https://enterprise.proxmox.com/debian buster InRelease' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

What can I do else for resolving the issue?

 

[Shaaarnir]

Can you help me with update from Enterprise repo?
What is wrong with update on two our servers?

I don't understand why two servers have a correct update, and another two have issues. We bought licenses at the same time on 4 servers.

 

[tom]

Please read again my previous post.

 

[Shaaarnir]

I contacted with my reseller (ualinux) and he didn't help me.
He reissued two keys with problems and said he couldn't do anything else.

 

[tom]

Please contact again your reseller. The reseller has to assist here (with the help of Proxmox support) .

If you reseller is not able to assist, you should consider to choose another reseller.

 

[UALinux]

Please contact again your reseller. The reseller has to assist here (with the help of Proxmox support) .

If you reseller is not able to assist, you should consider to choose another reseller.

In terms of keys - we reissued them
and after contacting the client's server, the keys became active again.
The keys are ok
but if nothing changed on the client server
then most likely two keys are compromised (they were stolen)
and is being used by someone else.
But we, as a supplier, do not see from which IP addresses your repository is being accessed.
We believe that the problem can be solved
only revocation of two problematic keys and full re-issue (with new unique names)
or connecting to the client's server via SSH for a detailed clarification of the problem (perhaps the client has problems on the server itself, but he does not know about them).
But the customer did not purchase technical support

 

[tom]

Again, key issues cannot be solved via the community forum, so I cannot assist here.

@UALinux , please get in touch with our technical support via the well know private channels.

 

[Shaaarnir]

UALinyx is really bad reseller.
A few month months have passed and there is no solution. Many calls, many emails - nothing.
We will search a new reseller in Ukraine.

 

[UALinux]

UALinyx is really bad reseller.
A few month months have passed and there is no solution. Many calls, many emails - nothing.
We will search a new reseller in Ukraine.

the charges are unfounded.
problems on the client side, he got confused about his licenses.
the client did not purchase technical support, but requires a solution to his problem.
within the framework of his "Community" subscription - we did a re-release of his licenses and even several times.
we even went to a meeting with you and offered to solve your problem by gradually activating licenses in order to understand where you are making a mistake, but you refused our help.
if you are wrong somewhere and do not want to purchase technical support, this does not mean that you purchased from a bad reseller.

for all the time since 2011 - there have been no complaints about our work.
therefore we require:
or clear justified claims
or a formal apology from you.

 

[Shaaarnir]

The work on our side was not carried out on the servers before 2021-01-06. But update with our community license was broken.

You no one ask me about logs!
Maybe If you looked in logs maybe you tell me, that I didn't correct understand situation because...
But nothing!

So I believe that you wanted to sell us your additional services, which we don't need.
I only need a working key.
I paid for keys and UALinux broken my keys.

 

[UALinux]

You no one ask me about logs!
Maybe If you looked in logs maybe you tell me, that I didn't correct understand situation because...
But nothing!

this forum exists for your "Community"-subscription.
no one forbids you to publish your logs here
and ask the Community what your problem is.
what do we have to do with it?
we are not part of the technical support "Community"-subscription.

So I believe that you wanted to sell us your additional services, which we don't need.

we offered to upgrade your subscription to the Basic level so that you could contact the program developers with your problem within the framework of technical support.

So I believe that you wanted to sell us your additional services, which we don't need.
I only need a working key.
I paid for keys and UALinux broken my keys.

how do you imagine that ?
we can't break your key - it's a text string

your keys are fully functional.
which has been confirmed by proxmox.com

also proxmox.com reported that based on the logs from their servers: ", it looks like the end customer mixed something up,"

the problem is on your side, but you are trying to blame everyone - except yourself.

 

[Shaaarnir]

...

the problem is on your side, but you are trying to blame everyone - except yourself.

Problem with you, you don't competent that understand client position. I paid for key that didn't work.

What you want else?
I don't want work with you and the end.

 

[Shaaarnir]

UALinux don't want help me with key.

Can help me someone from Proxmox?
What do I need to do for resolving my problem? (logs, keys...).

 

[UALinux]

Problem with you, you don't competent that understand client position. I paid for key that didn't work.

you are trying to deceive everyone and contradict yourself.
you had a working key and worked until you broke something on 2021-01-06, after which it stopped working.
you wrote about it yourself.

I don't want work with you and the end.

with such an impudent deceiver as you - no one won't want to work

UALinux don't want help me with key.

we offered you FREE help, but you refused, with claims made up by you that your keys stopped working due to our fault.

Can help me someone from Proxmox?
What do I need to do for resolving my problem? (logs, keys...).

you have already been provided with an official answer from proxmox - that you have a confusion with licenses on your side.
but you stubbornly reject this, accusing us of the fact that your licenses stopped working.

this is a community forum,
and you will first apologize to us for the lies that you wrote, and then ask for help from others.