This is due to a temporary issue related to the extension manager server being upgraded. The workaround process is described here: