| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109 |
- Please skip to the English section below if you don't write Chinese.
- 中文:
- 提交 Issue 之前请先阅读 [Issue 指引](https://github.com/v2ray/v2ray-core/blob/master/.github/SUPPORT.md),然后回答下面的问题,谢谢。
- 除非特殊情况,请完整填写所有问题。不按模板发的 issue 将直接被关闭。
- 1) 你正在使用哪个版本的 V2Ray?(如果服务器和客户端使用了不同版本,请注明)
- 2) 你的使用场景是什么?比如使用 Chrome 通过 Socks/VMess 代理观看 YouTube 视频。
- 3) 你看到的不正常的现象是什么?(请描述具体现象,比如访问超时,TLS 证书错误等)
- 4) 你期待看到的正确表现是怎样的?
- 5) 请附上你的配置(提交 Issue 前请隐藏服务器端IP地址)。
-
- 服务器端配置:
- ```javascript
- // 在这里附上服务器端配置文件
- ```
- 客户端配置:
- ```javascript
- // 在这里附上客户端配置
- ```
- 6) 请附上出错时软件输出的错误日志。在 Linux 中,日志通常在 `/var/log/v2ray/error.log` 文件中。
- 服务器端错误日志:
- ```
- // 在这里附上服务器端日志
- ```
- 客户端错误日志:
- ```
- // 在这里附上客户端日志
- ```
- 7) 请附上访问日志。在 Linux 中,日志通常在 `/var/log/v2ray/access.log` 文件中。
- ```
- // 在这里附上服务器端日志
- ```
- 8) 其它相关的配置文件(如 Nginx)和相关日志。
- 9) 如果 V2Ray 无法启动,请附上 `--test` 输出。
- 通常的命令为 `/usr/bin/v2ray/v2ray --test --config /etc/v2ray/config.json`。请按实际情况修改。
- 10) 如果 V2Ray 服务运行不正常,请附上 journal 日志。
- 通常的命令为 `journalctl -u v2ray`。
- 请预览一下你填的内容再提交。
- 如果你已经填完上面的问卷,请把下面的英文部份删除,再提交 Issue。
- Please remove the Chinese section above.
- English:
- Please read the [instruction](https://github.com/v2ray/v2ray-core/blob/master/.github/SUPPORT.md) and answer the following questions before submitting your issue. Thank you.
- Please answer all the questions with enough information. All issues not following this template will be closed immediately.
- 1) What version of V2Ray are you using (If you deploy different version on server and client, please explicitly point out)?
- 2) What's your scenario of using V2Ray? E.g., Watching YouTube videos in Chrome via Socks/VMess proxy.
- 3) What did you see? (Please describe in detail, such as timeout, fake TLS certificate etc)
- 4) What's your expectation?
- 5) Please attach your configuration file (**Mask IP addresses before submit this issue**).
- Server configuration:
- ```javascript
- // Please attach your server configuration here.
- ```
- Client configuration:
- ```javascript
- // Please attach your client configuration here.
- ```
- 6) Please attach error logs, especially the bottom lines if the file is large. Error log file is usually at `/var/log/v2ray/error.log` on Linux.
- Server error log:
- ```
- // Please attach your server error log here.
- ```
- Client error log:
- ```
- // Please attach your client error log here.
- ```
- 7) Please attach access log. Access log is usually at '/var/log/v2ray/access.log' on Linux.
- ```
- // Please attach your server access log here.
- ```
- Please review your issue before submitting.
- 8) Other configurations (such as Nginx) and logs.
- 9) If V2Ray doesn't run, please attach output from `--test`.
- The command is usually `/usr/bin/v2ray/v2ray --test --config /etc/v2ray/config.json`, but may vary according to your scenario.
- 10) If V2Ray service doesn't run, please attach journal log.
- Usual command is `journalctl -u v2ray`.
|