1.8 KiB
name | about |
---|---|
Bug report | Create a bug report to help us improve |
Please answer all the questions with enough information. All issues not following this template will be closed immediately. If you are not sure if your question is truely a bug in V2Ray, please discuss it here first.
-
What version of V2Ray are you using (If you deploy different version on server and client, please explicitly point out)?
-
What's your scenario of using V2Ray? E.g., Watching YouTube videos in Chrome via Socks/VMess proxy.
-
What did you see? (Please describe in detail, such as timeout, fake TLS certificate etc)
-
What's your expectation?
-
Please attach your configuration file (Mask IP addresses before submit this issue).
Server configuration:
// Please attach your server configuration here.
Client configuration:
// Please attach your client configuration here.
- 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.
- Please attach access log. Access log is usually at '/var/log/v2ray/access.log' on Linux.
// Please attach your server access log here.
-
Other configurations (such as Nginx) and logs.
-
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.
- If V2Ray service doesn't run, please attach journal log.
Usual command is journalctl -u v2ray
.
Please review your issue before submitting.