3CX Linux based Failed Latest update

[virtual3cx]

Hi My linux based 3CX is hosted in Microsoft AZURE and has been working perfectly since installation 3 months ago.
The last automatic update (yesterday) failed with the following significant messages in the error log file:

Err:4 http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release
404 Not Found [IP: 143.204.226.97 80]

E: The repository 'http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release' does no longer have a Release file.

Is resolution of this issue being already worked on by 3CX to auto update or do I need to do something on my side ?
Thanks / regards

 

[Evolute IT]

Hi My linux based 3CX is hosted in Microsoft AZURE and has been working perfectly since installation 3 months ago.
The last automatic update (yesterday) failed with the following significant messages in the error log file:

Err:4 http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release
404 Not Found [IP: 143.204.226.97 80]

E: The repository 'http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release' does no longer have a Release file.

Is resolution of this issue being already worked on by 3CX to auto update or do I need to do something on my side ?
Thanks / regards

https://www.3cx.com/community/threads/update-failing-saltstack-issue.74217/unread

 

[woodelf]

Same here... from the update log:

Hit:7 http://downloads-global.3cx.com/downloads/debian stretch InRelease
Ign:8 http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch InRelease
Err:10 http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release
404 Not Found [IP: 99.86.154.64 80]
Reading package lists...
E: The repository 'http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release' does no longer have a Release file.
--

I hope you can help us.

 

[complex1]

Try this one:
https://www.3cx.com/community/threads/update-failing-saltstack-issue.74217/#post-333990

 

[Evolute IT]

Guys, do some quick search on the forum. There's already 10 posts about that.

 

[AWS2P]

I found answer yesterday and applied with success, update is now working on instances where problem was same as yours