|
@@ -7,6 +7,8 @@ body:
|
|
|
description: |-
|
|
|
Please check all of the following options to prove that you have read and understood the requirements, otherwise this issue will be closed.
|
|
|
options:
|
|
|
+ - label: I have read all the comments in the issue template and ensured that this issue meet the requirements.
|
|
|
+ required: true
|
|
|
- label: I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
|
|
|
required: true
|
|
|
- label: I provided the complete config and logs, rather than just providing the truncated parts based on my own judgment.
|
|
@@ -38,6 +40,8 @@ body:
|
|
|
### For config
|
|
|
Please provide the configuration files that can reproduce the problem, including the server and client.
|
|
|
Don't just paste a big exported config file here. Eliminate useless inbound/outbound, rules, options, this can help determine the problem, if you really want to get help.
|
|
|
+ After removing parts that do not affect reproduction, provide the actual running **complete** file.
|
|
|
+ meaning of complete: This config can be directly used to start the core, **not a truncated part of the config**. For fields like keys, use newly generated valid parameters that have not been actually used to fill in.
|
|
|
|
|
|
### For logs
|
|
|
Please set the log level to debug and dnsLog to true first.
|
|
@@ -46,42 +50,29 @@ body:
|
|
|
Provide the log of Xray-core, not the log output by the panel or other things.
|
|
|
|
|
|
### Finally
|
|
|
- After removing parts that do not affect reproduction, provide the actual running **complete** file, do not only provide inbound or outbound or a few lines of logs based on your own judgment.
|
|
|
- Put the content between the preset ```<details><pre><code>``` ```</code></pre></details>``` in the text box.
|
|
|
- If the problem is very clear that only related to one end (such as core startup failure/crash after correctly writing the config according to the documents), N/A can be filled in for unnecessary areas below.
|
|
|
+ The specific content to be filled in each of the following text boxes needs to be placed between ```<details><pre><code>``` and ```</code></pre></details>```, like this
|
|
|
+ ```
|
|
|
+ <details><pre><code>
|
|
|
+ (config)
|
|
|
+ </code></pre></details>
|
|
|
+ ```
|
|
|
- type: textarea
|
|
|
attributes:
|
|
|
label: Client config
|
|
|
- value: |-
|
|
|
- <details><pre><code>
|
|
|
-
|
|
|
- </code></pre></details>
|
|
|
validations:
|
|
|
required: true
|
|
|
- type: textarea
|
|
|
attributes:
|
|
|
label: Server config
|
|
|
- value: |-
|
|
|
- <details><pre><code>
|
|
|
-
|
|
|
- </code></pre></details>
|
|
|
validations:
|
|
|
required: true
|
|
|
- type: textarea
|
|
|
attributes:
|
|
|
label: Client log
|
|
|
- value: |-
|
|
|
- <details><pre><code>
|
|
|
-
|
|
|
- </code></pre></details>
|
|
|
validations:
|
|
|
required: true
|
|
|
- type: textarea
|
|
|
attributes:
|
|
|
label: Server log
|
|
|
- value: |-
|
|
|
- <details><pre><code>
|
|
|
-
|
|
|
- </code></pre></details>
|
|
|
validations:
|
|
|
required: true
|