fix

README.md

@@ -36,6 +36,12 @@ Chinese and English are both supported.
 
 https://github.com/oneclickvirt/oneclickvirt
 
+## 1Panel 第三方应用商店 / 1Panel Third-Party App Store
+
+[okxlin/appstore](https://github.com/okxlin/appstore) 已收录 OneClickVirt。已安装 1Panel 的用户可按该仓库说明添加或同步本地应用商店，然后在本地应用列表中选择 `oneclickvirt` 部署。
+
+[okxlin/appstore](https://github.com/okxlin/appstore) now includes OneClickVirt. If you already use 1Panel, add or synchronize that local app store, then deploy `oneclickvirt` from the local app list.
+
 ## PVE相关的各种一键脚本
 
 [https://github.com/oneclickvirt/pve](https://github.com/oneclickvirt/pve)

docs/en/guide/dashboard.md

@@ -30,6 +30,10 @@ Stars and forks are welcome. Everything listed here is open source. If you redis
 
 https://github.com/oneclickvirt/oneclickvirt
 
+## 1Panel Third-Party App Store
+
+[okxlin/appstore](https://github.com/okxlin/appstore) now includes OneClickVirt. If you already use 1Panel, follow that repository's instructions to add or synchronize the local app store, then deploy `oneclickvirt` from the local app list.
+
 ## PVE
 
 [https://github.com/oneclickvirt/pve](https://github.com/oneclickvirt/pve)

docs/en/guide/oneclickvirt/oneclickvirt_install.md

@@ -31,6 +31,10 @@ Hardware requirements include at least 1G of free memory and 2G of free disk spa
 | Dockerfile Self-Compilation | Suitable for source code updates and maintenance | Highly customizable | Requires Docker environment, lengthy compilation time |
 | One-Click Full-Stack Script | Bare-metal quick deployment | Fully automated: DB, reverse proxy, TLS, frontend & backend | Higher hardware requirements (10G disk/2G memory) |
 
+### Installation via the 1Panel Third-Party App Store
+
+[okxlin/appstore](https://github.com/okxlin/appstore) now includes OneClickVirt. This repository is an unofficial 1Panel app store adaptation repository. If you already use 1Panel, follow that repository's instructions to add or synchronize the local app store, then deploy `oneclickvirt` from the local app list.
+
 ### Installation via Pre-compiled Binary Files
 
 Two methods are distinguished here:
@@ -564,6 +568,6 @@ Admin123!@#
 
 During the initialization process, all image seed data is loaded into the database by default, but by default only ```debian``` and ```alpine``` related version images are enabled. This is to avoid user selection difficulties caused by too many enabled images.
 
-If you need additional types of images, you need to search by type, architecture, and version in the system image management interface under administrator privileges and enable them.
+If you need additional types of images, you need to search by type, architecture, and version in the system image management interface under administrator privileges and enable them. Windows, Android, macOS, and other non-Linux/BSD images are also imported as preset seeds, but they are disabled by default and have higher CPU, memory, and disk requirements to prevent accidental creation on low-end nodes. Before enabling these images, confirm that the target provider satisfies the required nested virtualization, disk space, KVM, or Docker special runtime conditions.
 
 After initialization, please immediately change the default administrator username and password, and disable or delete the default enabled test user ```testuser```. This can be done in the administrator's user management page.

docs/en/guide/oneclickvirt/oneclickvirt_precheck.md

@@ -57,7 +57,7 @@ No Port Mapping
 
 - Traffic Statistics: Integrates IP-level and network interface-level precise network traffic statistics. Forces traffic data synchronization during sensitive operations to ensure data accuracy
 
-- Monthly traffic usage statistics reset at the beginning of each month. Supports traffic statistics and limits at user, instance, and Provider levels
+- Traffic reset days can be configured per provider. Leaving the field empty follows the natural month and resets on the 1st day of each month. Supports traffic statistics and limits at user, instance, and Provider levels
 
 - Invitation Code System: Supports non-public registration invitation mechanism, with different resource quota limits based on user levels
 

docs/en/guide/oneclickvirt/oneclickvirt_usage.md

@@ -156,7 +156,7 @@ Not recommended to modify the mapping method unless you know what this setting d
 
 ![](./images/bw3.png)
 
-Simply put, this sets the maximum bandwidth for instances created on the node and the total available traffic calculated on a natural-month basis. Traffic monitoring and traffic statistics are not enabled by default.
+Simply put, this sets the maximum bandwidth for instances created on the node and the total available traffic quota. Traffic monitoring and traffic statistics are not enabled by default. The traffic cycle follows the natural month by default and resets on the 1st day of each month. You can also choose a monthly reset day in the Expiry Settings section later; if 29, 30, or 31 is selected, shorter months automatically use the last day of that month.
 
 #### agent (Recommended)
 
@@ -204,6 +204,8 @@ Only after enabling traffic control will the traffic monitoring management butto
 
 ![](./images/pcz.png)
 
+The traffic reset day affects current-cycle statistics, user/instance/provider traffic limit checks, and recovery queueing for instances automatically stopped because of traffic overuse. When a provider reaches its reset day, the system first clears that provider's traffic-limit state, then recalculates user and instance limits. Instances that are no longer over the limit and have no other freeze reason will automatically receive a start task.
+
 ### Level Restrictions (Required)
 
 ![](./images/level.png)
@@ -214,16 +216,30 @@ During the actual instance creation process, the node-level level restrictions w
 
 This setting is to specialize the configuration limits of instances that users of corresponding levels can create on the current node, avoiding situations where global limits are not suitable for the current node. Global limits can be set in system configuration and are generally used for user account-level resource usage restrictions.
 
-### Advanced Settings (Optional)
+### Expiry Settings (Optional)
 
 ![](./images/setmore1.png)
 
-![](./images/setmore2.png)
-
 Expiration time:
 
 Prevents users from continuing to operate expired nodes. Expired nodes will be automatically frozen, at which time corresponding instances will not allow any operations but will not be automatically deleted. If a node is frozen, please clean and delete it in time.
 
+Traffic reset day:
+
+Leave it empty to follow the natural month, which starts a new traffic cycle on the 1st day of each month. You can also set any day from 1 to 31. The system calculates the current cycle, next reset time, and traffic-overlimit recovery separately for each provider.
+
+Instance expiration handling:
+
+When an instance expires, it can be frozen, stopped, automatically extended, or left for cleanup according to the provider setting. If an instance was automatically stopped because it expired, a successful check-in renewal creates a start task automatically, so the administrator does not need to start it manually.
+
+Check-in renewal:
+
+The previous check-in renewal tab has been merged into Expiry Settings. Configure check-in availability, renewal days, consecutive check-in rewards, and related limits here. After a successful check-in extends the expiration time, the system also clears the freeze caused by expiration. If the instance was stopped only because of expiration, it enters the start queue automatically.
+
+### Advanced Settings (Optional)
+
+![](./images/setmore2.png)
+
 Task concurrency control:
 
 Default is single-threaded serial execution. At the same time, only one add/delete/modify task (corresponding to instance creation, deletion, and reset operations) will exist.
@@ -532,4 +548,4 @@ Detailed configuration for system log recording, based on the zap log library.
 - `show-line`: Whether to display the filename and line number of log calls
 - `stacktrace-key`: Key name for stack trace information
 
-Note: When debugging issues, `level` should be set to `debug` to obtain detailed log information.
+Note: When debugging issues, `level` should be set to `debug` to obtain detailed log information.

docs/guide/dashboard.md

@@ -34,6 +34,10 @@ PVE项目可能造成宿主机出现问题，如果你不会看Bug和修复系
 
 https://github.com/oneclickvirt/oneclickvirt
 
+## 1Panel 第三方应用商店
+
+[okxlin/appstore](https://github.com/okxlin/appstore) 已收录 OneClickVirt。已安装 1Panel 的用户，可以按该仓库说明添加或同步本地应用商店，然后在本地应用列表中选择 `oneclickvirt` 部署。收录来源见 [PR #3535](https://github.com/okxlin/appstore/pull/3535) 和维护者重建验证记录 [PR #4218](https://github.com/okxlin/appstore/pull/4218)。
+
 ## PVE
 
 [https://github.com/oneclickvirt/pve](https://github.com/oneclickvirt/pve)

docs/guide/oneclickvirt/oneclickvirt_install.md

@@ -31,6 +31,10 @@ outline: deep
 | Dockerfile自编译 | 适合源码更新维护 | 高度自定义 | 需要Docker环境，编译耗时长 |
 | 一键全栈安装脚本 | 裸金属快速部署 | 全自动安装数据库/反向代理/TLS/前后端 | 硬件要求较高(10G磁盘/2G内存) |
 
+### 通过 1Panel 第三方应用商店安装
+
+[okxlin/appstore](https://github.com/okxlin/appstore) 已收录 OneClickVirt，本仓库是 1Panel 应用商店的非官方应用适配库。已安装 1Panel 的用户，可以按该仓库说明添加或同步本地应用商店，然后在本地应用列表中选择 `oneclickvirt` 部署。
+
 ### 通过预编译二进制文件安装
 
 这里区分两种方式：
@@ -584,6 +588,6 @@ Admin123!@#
 
 初始化过程中，默认加载了所有的镜像种子数据到数据库中，但是默认仅启用了```debian```和```alpine```相关版本的镜像，这是为了避免过多镜像启用导致用户选择困难。
 
-如果你需要额外类型的镜像，需要在管理员权限下，在系统镜像管理界面按照类型、架构、版本搜索并进行启用。
+如果你需要额外类型的镜像，需要在管理员权限下，在系统镜像管理界面按照类型、架构、版本搜索并进行启用。Windows、Android、macOS 等非 Linux/BSD 镜像也会作为预设种子导入，但默认不启用，并且设置了更高的 CPU、内存和硬盘要求，避免用户在低配置节点上误开设。启用这些镜像前，请先确认对应节点已满足嵌套虚拟化、磁盘空间、KVM 或 Docker 特殊运行环境要求。
 
 初始化后请立即修改默认的管理员的用户名密码，并禁用或删除默认启用的测试用户```testuser```，这一部分可在管理员的用户管理页面进行操作。

docs/guide/oneclickvirt/oneclickvirt_precheck.md

@@ -57,7 +57,7 @@ NAT IPv4 + 独立IPv6
 
 - 流量统计：集成IP级和网络接口级进行精确的网络流量统计, 敏感操作时强制同步流量数据，确保数据准确性
 
-- 每月初统一重置用户流量使用统计，支持用户级、实例级、Provider级的流量统计和限制
+- 支持按节点配置流量重置日，留空时默认每月 1 日按自然月重置；支持用户级、实例级、Provider级的流量统计和限制
 
 - 邀请码系统：支持非公开注册邀请机制，根据用户等级设置不同的资源配额限制
 

docs/guide/oneclickvirt/oneclickvirt_usage.md

@@ -156,7 +156,7 @@ SSH超时配置是设计测试连通性和优化容错率的，也可以用来
 
 ![](./images/bw3.png)
 
-字面意思，设置节点开设出的实例的最大带宽和以自然月计算的可用流量总量，默认不自动启用流量监控和流量统计。
+字面意思，设置节点开设出的实例的最大带宽和可用流量总量，默认不自动启用流量监控和流量统计。流量周期默认跟随自然月在每月 1 日重置，也可以在后面的过期设置中指定每月几号重置；如果选择 29、30、31 号，短月份会自动按当月最后一天处理。
 
 #### agent(推荐)
 
@@ -204,6 +204,8 @@ SSH超时配置是设计测试连通性和优化容错率的，也可以用来
 
 ![](./images/pcz.png)
 
+流量重置日会影响当前周期统计、用户/实例/节点三级超限判断，以及因流量超限被自动停止的实例恢复排队。到达节点的重置日后，系统会先清理该节点的流量超限标记，再重新计算用户和实例层级限制，仍然未超限且没有其他冻结原因的实例会自动创建启动任务。
+
 ### 等级限制(必填)
 
 ![](./images/level.png)
@@ -214,16 +216,30 @@ SSH超时配置是设计测试连通性和优化容错率的，也可以用来
 
 这样设置是为了特殊化当前节点对应等级的用户可开设的实例的配置限制，避免有时候全局限制不适用当前节点，全局限制在系统配置中可设置，一般用于用户整个账户层面的使用资源限制。
 
-### 高级设置(可选)
+### 过期设置(可选)
 
 ![](./images/setmore1.png)
 
-![](./images/setmore2.png)
-
 过期时间：
 
 防止用户继续操作已经过期的节点，过期节点将自动冻结，此时对应的实例将不允许任何操作，但不会自动删除，如果冻结了节点请及时清理删除节点。
 
+流量重置日：
+
+留空时默认跟随自然月，每月 1 日自动进入新的流量周期。也可以设置为每月 1 到 31 号中的任意一天，系统会按照每个节点单独计算当前周期、下次重置时间和超限实例自动恢复逻辑。
+
+实例到期处置：
+
+实例到期后可以按节点配置冻结、停止、自动延长或等待清理。因为过期被自动停止的实例，在用户签到续期后会自动创建启动任务，不需要管理员手动补发。
+
+签到续期：
+
+原签到续期分页已合并到过期设置中，这里统一配置是否开启签到、签到奖励天数、连续签到奖励和相关限制。用户签到成功并延长过期时间后，系统会同步解除因过期造成的冻结；如果实例此前是因为过期被自动停止，会自动进入启动排队。
+
+### 高级设置(可选)
+
+![](./images/setmore2.png)
+
 任务并发控制：
 
 默认单线程串联执行，同一时刻，只会存在一个增删改的任务(对应实例的开设删除重置操作)。