Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

启动过程失败 #23

Closed
Dickxia opened this issue Jul 14, 2019 · 10 comments
Closed

启动过程失败 #23

Dickxia opened this issue Jul 14, 2019 · 10 comments
Labels
Documentations Something about the documentations platform/linux Issue related to Linux t/runtime Issue occured in runtime, not compile-time

Comments

@Dickxia
Copy link

Dickxia commented Jul 14, 2019

v2ray core faqt5ct: using qt5ct plugin
Loaded config file.
Loaded translations zh-CN
qt5ct: D-Bus system tray: yes
QMetaObject::connectSlotsByName: No matching signal for on_clbutton_clicked()
Now start a connection: 香港 1 * 2
v2ray core failed with exit code 255
Now start a connection: 香港 2 * 1.5
v2ray core failed with exit code 255

iled with exit code 255

@ghost
Copy link

ghost commented Jul 14, 2019

Can you provide your config file and Qv2ray settings Qv2ray.conf in your folder (~/.qv2ray for *nix, ./qv2ray.d for Windows) please? I'll try to re-trigger the bug.
It seems the final configuration generated is corrupted.

If you are in Windows, please DONOT add * to the name as the Windows does not allow paths containing special char *

@ghost ghost added the t/runtime Issue occured in runtime, not compile-time label Jul 14, 2019
@Dickxia

This comment has been minimized.

@ghost
Copy link

ghost commented Jul 15, 2019

Can you please provide your OS type? It's Linux, macOS or Windows? As well as your config file ( one of those named 香港 5* 1.5.qv2ray.json)
Please hide your server address and UUID with *

@Dickxia
Copy link
Author

Dickxia commented Jul 15, 2019

Can you please provide your OS type? It's Linux, macOS or Windows? As well as your config file ( one of those named 香港 5* 1.5.qv2ray.json)
Please hide your server address and UUID with *


The OS I use is manjaro gnome(a linux OS)
This problem only happen when I use the offical edition,it's well perform when I use the package in the AUR

{
"outbounds": [
{
"mux": {
"concurrency": 1,
"enabled": false
},
"protocol": "vmess",
"sendThrough": "0.0.0.0",
"settings": {
"vnext": [
{
"address": "****************",
"port": 443,
"users": [
{
"alterId": 2,
"id": "**************************************",
"level": 0,
"security": "auto"
}
]
}
]
},
"streamSettings": {
"dsSettings": {
"path": "/"
},
"httpSettings": {
"host": [
""
],
"path": ""
},
"kcpSettings": {
"congestion": false,
"downlinkCapacity": 20,
"header": {
"type": "none"
},
"mtu": 1350,
"readBufferSize": 1,
"tti": 20,
"uplinkCapacity": 5,
"writeBufferSize": 1
},
"network": "tcp",
"quicSettings": {
"header": {
"type": "none"
},
"key": "",
"security": ""
},
"security": "tls",
"sockopt": {
"mark": 0,
"tcpFastOpen": false,
"tproxy": "off"
},
"tcpSettings": {
"header": {
"request": {
"headers": {
},
"method": "GET",
"path": [
],
"version": "1.1"
},
"response": {
"headers": {
},
"reason": "OK",
"status": "200",
"version": "1.1"
},
"type": "none"
}
},
"tlsSettings": {
"allowInsecure": false,
"alpn": [
],
"certificates": [
],
"disableSystemRoot": false,
"serverName": ""
},
"wsSettings": {
"headers": {
"Host": ""
},
"path": ""
}
},
"tag": "outBound_PROXY"
}
]
}

@ghost
Copy link

ghost commented Jul 15, 2019

I'm sorry, I tried replacing your file content and the same file name, however, I could not re-generate the same bug. It seems strange.

$ v2ray --version          
V2Ray 4.20.0 (V2Fly, a community-driven edition of V2Ray.) Custom
A unified platform for anti-censorship.

You said:

This problem only happen when I use the offical edition,it's well perform when I use the package in the AUR

Do you mean you install the v2ray-bin in AUR and start the connection in Qv2ray and it works?

If so that should be an upstream bug. Because what Qv2ray does is simply generate a complete v2ray connection config and send it to the v2ray kernel (the /bin/v2ray as in your config file).

BTW, did you see any error messages (like some message pop-ups) before the v2ray core failed with exit code 255 appears in the terminal?

@ghost ghost added Bugs Something isn't working platform/linux Issue related to Linux Upstream Upstream Qt, v2ray-core, GLIBC or golang related bugs. labels Jul 15, 2019
@ghost
Copy link

ghost commented Jul 15, 2019

Qv2ray creates a final config.json inside the folder ~/.qv2ray/genrerated/config.gen.json
Please run v2ray self config test by inputting the commands below, AFTER you click Start in Qv2ray
v2ray --test --config ~/.qv2ray/genrerated/config.gen.json
And give me the output/

EDITED: Don't forget to set the V2RAY_LOCATION_ASSET env variable, it should be set to /etc/v2ray

so do this:
V2RAY_LOCATION_ASSET=/etc/v2ray v2ray --test --config ~/.qv2ray/genrerated/config.gen.json

@ghost
Copy link

ghost commented Jul 15, 2019

Did you have v2ray-domain-list-community and v2ray-geoip packages installed? They provide contents of /etc/v2ray, and it's required by Qv2ray.

FYI:
those two packages are at:
https://www.archlinux.org/packages/community/any/v2ray-domain-list-community/
https://www.archlinux.org/packages/community/any/v2ray-geoip/

@ghost ghost added Dependency and removed Upstream Upstream Qt, v2ray-core, GLIBC or golang related bugs. labels Jul 15, 2019
@ghost ghost pinned this issue Jul 17, 2019
ghost pushed a commit that referenced this issue Jul 18, 2019
Signed-off-by: Leroy.H.Y <lhy20010403@hotmail.com>
@ghost ghost added Documentations Something about the documentations help wanted Extra attention is needed and removed Bugs Something isn't working labels Jul 19, 2019
@ghost ghost added the DiscussionNeeded label Aug 5, 2019
@ghost
Copy link

ghost commented Aug 5, 2019

Is this thread still active?

@copurxia
Copy link

copurxia commented Aug 5, 2019

Is this thread still active?

I use the package in AUR instead of offical.So that I haven't care about it.

@ghost
Copy link

ghost commented Aug 5, 2019

So closed and mark as solved. There are already an update in README explaining this issue.

@ghost ghost closed this as completed Aug 5, 2019
@ghost ghost removed DiscussionNeeded help wanted Extra attention is needed labels Aug 5, 2019
@ghost ghost unpinned this issue Aug 6, 2019
@rubyKC rubyKC mentioned this issue Aug 24, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentations Something about the documentations platform/linux Issue related to Linux t/runtime Issue occured in runtime, not compile-time
Development

No branches or pull requests

2 participants