Solved Sorry, you have been blocked for v18 update 31

[Senõr Engineer]

I have some on-prem Windows based v20s systems that are not updating as the URL is being blocked. Previous posts suggest the public IP of the 3CX server that is not the issue, it's the endpoint where the update is coming from.

Oddly I have a number of systems that have successfully update over the weekend without issue and I'm left with 2 that keep getting the blocked message when looking at the event log:

EventId: 0
SpanId: XXXXXXXXXXXXXX
TraceId: XXXXXXXXXXXXXXXXXXXXXXXXXXX
ParentId: 0000000000000000
ConnectionId: XXXXXXXXXXXXX
RequestId: XXXXXXXXXXXXX:00000003
RequestPath: /xapi/v1/GetUpdates()
ActionId: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
ActionName: XAPI.UpdatesController.GetUpdates (XAPI)

Request to https://downloads-global.3cx.com/downloads/v180/hotfixes/hotfixes.xml has failed with message $Server returned 'Forbidden' when 'https://downloads-global.3cx.com/downloads/v180/hotfixes/hotfixes.xml' was requested.

Can someone confirm if the issue is at the 3CX downloads side?

 

[TheodorosG_3CX]

Is the PBX able to activate?

 

[bitn2]

Windows based

Windows based systems need to reinstal with backup and restore.

 

[TheodorosG_3CX]

Sorry i missed the Windows. Yes the upgrade path is only for the Debian installations.
Furthermore as per blog post below the Windows installer for V20 is released in Alpha state:
• https://www.3cx.com/blog/releases/v20-windows-alpha/

 

[Senõr Engineer]

@TheodorosG_3CX, there are several v18 installation on Windows for this customer that have already updated to v18 update 31 as per https://www.3cx.com/blog/releases/v18-update9a so this both Debian and Windows specific for the push certificates.

All that said I checked these 2 instance just now and they've now "mysteriously" now updated - so no further action required.

 

[TheodorosG_3CX]

Glad to know the issue is resolved now.