Level 1 and Level 2 deploys from the portal work again

Since late September, every Level 1 or Level 2 deploy from the portal failed with the message “body is not a .ee container”, so you couldn’t put an encrypted site online from the portal. The portal was writing more information at the start of each package than the space set aside for it, and the upload was refused. From 26 October, Level 1 and Level 2 deploys from the portal work again.

Level 0 deploys from the portal, and deploys at any level with ee-cdn-cli, were not affected.

Level 1 deploys now send your site’s integrity record

Gateways and browsers check every piece of a site that comes from an operator node against a record of the site’s content. Without that record, operator nodes never deliver the site, and it is served from the gateway only. Level 1 deploys from the portal now send this record as their last step.

• If the record isn’t accepted, your deploy still completes. Your site is online, and your key and link are shown as usual. A warning under the key says operator nodes won’t deliver the site until you deploy it again.
• If that happens after a network error, deploying again usually fixes it. Deploying again issues a new key and a new link, so share the new link.

Limits

• A Level 1 site with no domain of its own still can’t be opened from its share link. That is a separate fix, and it will have its own entry.

What you need to do

If a Level 1 or Level 2 deploy from the portal failed for you since late September, deploy that site again. Save the key when it is shown: it is shown once, and we can’t recover it.