2.6.7
tobychui/zoraxy2.6.7Sep 26, 2023by tobychui
AI Summary
This release fixes a critical multidomain logic bug from version 2.6.6 while introducing a comprehensive static web server with integrated file management capabilities. It also adds support for custom blacklist/whitelist templates, preferred Certificate Authority configuration for ACME, and an optimized TLS/SSL management interface.
Key Highlights
- Fixed multidomain missing logic bug
- Added Static Web Server function with Web Directory Manager
- Support for custom blacklist/whitelist HTML templates
- Added default/preferred Certificate Authority (CA) features for ACME
- Optimized TLS/SSL page with dedicated ACME section
New Features
- Static Web Server function
- Web Directory Manager for file operations (rename, upload, download, copy/cut, delete)
- Custom blacklist/whitelist template support via HTML files in ./www/templates/
- Default/preferred CA configuration for ACME
- Service Expose Proxy dummy page
- Dedicated ACME section in TLS/SSL settings
Full Release Notes
## Updates 2.6.7 This version fixes bug in 2.6.6 and added the static web server features - Fixed multidomain missing logic (by @daluntw ) - Added Static Web Server function - Web Directory Manager - Added static web server and black / whitelist template - Added default / preferred Ca features - Added Service Expose Proxy dummy page - Optimized TLS/SSL page and added dedicated section for ACME related features ### Working with Templates To add templates to black / whitelist, create a html file under the blacklist / whitelist folder. By default, the templates should be placed at the following paths. ``` ./www/templates/blacklist.html ./www/templates/whitelist.html ``` If the template is not found, the build in one will be used. ### Static Web Server Notes Web directory can only be changed via startup parameter `-webroot` due to security reasons. You can manage your web directory and perform some basic file operations like rename, upload, download, copy / cut and delete via the web directory manager which is basically a trim down version of the ArozOS File Manager. If you do not want to expose your web directory to the web interface due to security concerns, use -webfm=false in your startup parameter to disable the feature. This will disable all api related to the file manager in the back-end server.