github.com/v2fly/v2ray-core/v5@v5.16.2-0.20240507031116-8191faa6e095/.github/ISSUE_TEMPLATE/bug_en.md (about) 1 --- 2 name: Bug report 3 about: "Create a bug report to help us improve" 4 --- 5 6 <!-- 7 Please answer all the questions with enough information. All issues not following this template will be closed immediately. 8 If you are not sure if your question is truely a bug of V2Ray, please discuss it at https://github.com/v2fly/v2ray-core/discussions first. 9 --> 10 11 ## What version of V2Ray are you using? 12 13 <!-- If you deploy different versions of V2Ray on server and client, please explicitly point out --> 14 15 16 ## What's your scenario of using V2Ray? 17 18 <!-- E.g., watching YouTube videos in browsers via Socks/VMess proxy --> 19 20 21 ## What problems have you encountered? 22 23 <!-- Please describe in detail, such as timeout, fake TLS certificate, etc --> 24 25 26 ## What's your expectation? 27 28 29 30 ## Please attach your configuration here 31 32 <!-- Remember to mask your IP address or hostname --> 33 34 **Server configuration:** 35 36 ```javascript 37 // Please attach your server configuration here. 38 39 ``` 40 41 **Client configuration:** 42 43 ```javascript 44 // Please attach your client configuration here. 45 46 ``` 47 48 ## Please attach error logs here 49 50 <!-- 51 only trailing lines if the log file is large in size. 52 Error log file is usually at `/var/log/v2ray/error.log` on Linux. 53 --> 54 55 **Server error log:** 56 57 ```javascript 58 // Please attach your server error log here. 59 60 ``` 61 62 **Client error log:** 63 64 ```javascript 65 // Please attach your client error log here. 66 67 ``` 68 69 ## Please attach access log here 70 71 <!-- Access log is usually at '/var/log/v2ray/access.log' on Linux. --> 72 73 ```javascript 74 // Please attach your server access log here. 75 76 ``` 77 78 ## Other configurations (such as Nginx) and logs here 79 80 81 82 ## If V2Ray cannot start up, please attach output from `--test` command 83 84 85 86 ## If V2Ray service is abnormal, please attach journal log here 87 88 <!-- Usual command is `journalctl -u v2ray` --> 89 90 <!-- Please review your issue and check the format before submitting. -->