返回更新日志
面板后端

v1.0.596

补丁 发布于 2026年11月14日

Sites that could not be reached over IPv6, archives created on Windows extracted into unusable files, and two repairs that run at startup.

错误修复

9
  • Every customer site bound to an address listened on IPv4 only, while the default server does listen on IPv6. A visitor arriving over IPv6 was served the panel's default page instead of the site, and Let's Encrypt — which prefers AAAA — got a 404 on validation while the same path over IPv4 returned 200. This affected every domain on a server with a bindable public IPv4 address, not only domains with a dedicated address.
  • Assigning an IPv6 address to a domain used to remove its IPv4 listener, so the site answered with the wrong page over IPv4. A site binds an IPv4 address and is served over IPv6 through the wildcard listener.
  • A ZIP file created on Windows was extracted into single flat files whose names contained backslashes, with no directory created at all, and the operation reported success. Both the file manager and the Node.js code upload now read such an archive correctly.
  • A hosting account can no longer be turned into an administrator or a reseller, or back. Promoting a hosting account emptied its own panel: its sites, mailboxes and databases disappeared from it, because a management account is listed through the created_by chain instead of owning its own records.
  • Reaching a plan limit for Node.js, Python or Laravel applications answers 409 Conflict instead of 500. The message was correct, but the status made a plan limit look like a server failure to the panel and to anything monitoring it.
  • Kernel disk quotas are no longer rewritten on every enforcement pass. The kernel keeps limits in whole blocks, so a byte-exact comparison never matched and the same values were written again every minute, once per domain of the account, with a log line each time. Both ext4 and XFS were affected.
  • A server whose hostname is a bare IP address no longer produces nameservers such as ns1.38.236.238 — a name that resolves nowhere, which went into the SOA record and the nameserver set of every zone while the per-domain glue records were dropped. New zones use ns1.<domain> again, and a startup repair clears the stored value on servers that already have one.
  • /tmp is restored to its standard permissions at startup when something has taken world access away, and the panel no longer stages files there at all when writing on a customer's behalf. On a server whose /tmp was not world-traversable, creating a domain failed at its first log file, the MySQL sockets published there were unreachable for customer processes, and PHP sessions failed silently.
  • A domain's IP address field no longer accepts a value that is not an address.
查看演示