Changelog
Page 2 of 3.
Signing in takes you to the part of the portal you use
Signing in on a new browser or device always opened Workloads, even for node operators. The portal now remembers your view with your account, and otherwise goes by what you chose at sign-up, so operators land on their dashboard.
evolvingedge.ai now runs on Evolving Edge
The Evolving Edge website is now served by the Evolving Edge CDN, like the blog and this changelog, so every public Evolving Edge site runs on the network it describes. Every old link still works.
Redirect old addresses with a _redirects file in your site
Ship a _redirects file with your site and matching requests get a 301 or 302, in the format Netlify and Cloudflare Pages use, so a site moving here can bring its redirects along. Works for Level 0 sites.
Nodes on systems without a machine ID now keep their identity
An edge node on a system with no machine ID came back as a brand new node every time it paired, and the key protecting its stored credentials came from its hostname alone. It now creates and keeps an identity of its own. Affected nodes pair once more after updating.
Your domain no longer lists what else an edge node has cached
Addresses such as /workloads and /discover on a customer's domain listed the content IDs of every site cached on that edge node, other customers' included. They now show only that site's own, and node diagnostics answer only on the node itself.
Publish any static site with ee-cdn-cli
ee-cdn-cli publishes a folder of static files to the CDN from the command line, so sites built with Hugo, Eleventy, Jekyll, Publii or by hand can deploy without a framework-specific integration.
The network map shows the gateway nodes in 47 U.S. markets
The public network map now marks each of the 47 U.S. markets where Evolving Edge will operate gateway nodes, alongside the live node counts.
Smaller changes — nav links, and a build link that no longer 404s
Two small portal changes, collected. The public leaderboard nav now links to the blog and the changelog, and the CI deploy card has stopped showing an alias URL that returned 404.
Videos and large files on your site can now be seeked and resumed
Files inside a site ignored range requests, so a video couldn't be seeked and Safari wouldn't play it at all. The edge now sends just the part of a file that was asked for. HTML pages are still always sent whole.
A node can now finish the enrollment it just performed
A node that enrolled successfully kept being rejected by the control plane and enrolled again, every forty seconds, without ever coming online. It affected Docker nodes worst, because nothing ever restarts them.
Deploy alias addresses now serve the deploy they name
Alias addresses of the form ee-name.cdn.3dge.app answered "domain not configured" for every deploy. They now serve the deploy they point to. Custom domains are unaffected and always take priority over an alias.
A manually forwarded port now counts toward gateway eligibility
Operators who had forwarded a port by hand were still told to forward one. The eligibility check only looked at endpoints discovered by UPnP, and ignored the address the control plane was already recording from every heartbeat.
The edge node's source is now public for review
The Node Core of the edge node is now readable at evolving-edge/edge-node-agent under MPL-2.0, published so security teams and operators can see for themselves what a node does with the content it serves.
The deploy preview link now points at a host that serves it
Every deploy without a custom domain showed a preview link that returned 404, because the link named the edge node rather than the control plane. Deploys with a domain were unaffected, which is why it went unnoticed.
A missing page no longer reveals where we store your files
A request for a page that doesn't exist used to answer with the internal storage path we had looked up, in unstyled plain text, with no cache headers at all. It now returns a branded page carrying no internal detail and an explicit cache policy.
Docker nodes keep their identity when the container is recreated
An edge node installed with Docker re-enrolled as a brand new node every time its container was recreated, resetting its Active Node Hours to zero. Updated Compose settings keep one identity across recreations. Existing Docker nodes reset once more as they pick this up.
Your site's own 404 page is now served
Ship a 404.html in your build and it is now served when someone asks for a page that doesn't exist, in your design, with a 404 status. Sites that don't ship one still get the branded fallback rather than plain text.
The monthly close now produces a statement, not a payment
The monthly close now works out what you earned and stops there, rather than moving money. Referral bonuses stay in your balance instead of being attached to a payout, and nothing is paid until a withdrawal is requested.
Level 1 and Level 2 key fixes reach the deploy CLI
The recent key-handling fixes have now been made in the deploy CLI and its Astro integration too, so every tool we maintain treats keys the same way. The CLI isn't published yet, so there is nothing for anyone to update.
Level 2 content now opens only for people you authorise
Level 2 exists so we can decrypt your content for people you have approved. It did not work — the key travelled inside the page and access checks refused everyone — so in practice anyone with the link could read it. Access is now granted one person at a time.
Revoking a deploy token now confirms it worked
Revoking a deploy token left you on a plain error page saying the token was not found, with no sign the revocation had worked. You are now returned to your tokens list with a message confirming which token was deleted.
Nodes no longer report monitors and management chips as GPUs
Node details listed a server's management chip or an attached monitor as a GPU, and Apple Silicon Macs reported no video memory. Nodes now report only real compute GPUs, and Apple Silicon reports its unified memory.
Decryption keys are wiped from memory after use
Level 2 workloads are decrypted on the edge node, so the node holds the content key while it serves a request. Edge nodes and the control plane now overwrite keys as soon as they are finished with them, instead of leaving them in memory until it is reclaimed.
The edge node now runs on 32-bit ARM
The edge node now builds for 32-bit ARM (armv7), covering the Raspberry Pi 2, 3 and 4 on a 32-bit operating system. Binary installs only for now; there is no container image for armv7 yet.
Level 1 decryption keys never reach our servers
Level 1 means only you, and whoever you share your link with, can read your content. Two faults broke that — one left the key on our servers, the other handed back no key at all. Both are fixed, and we now keep no copy of your key.
Subscribe: all products · CDN · Edge Node · CLI · Portal