Lsyx-Good
commented
5 days ago config and log file(level debug)
Open gee666 opened 5 days ago
Lsyx-Good
commented
5 days ago config and log file(level debug)
gee666
commented
5 days ago Here they are. First of all Codeium doens't work, I really need it. It works if I switch off and close v2rayN completely, but I need it too for my work.
Lsyx-Good
commented
5 days ago you sure that connect normal on turn off tun?or close your BT client can work?
Lsyx-Good
commented
5 days ago not found dns exchange failed on log file, but just found that connect closed or connect established failed
gee666
commented
5 days ago @Lsyx-Good here are two screenshots. One with tun mode disabled and codeium working perfectly The second with tun mode enabled and codeium doesn't work anymore So yes I am sure that it works without tun mode and it stops working when I enable it. though the key is working in general, myip.com shows the correct IP and location corresponding to the trojan key.
Also I try it through proxy in CLI and it seems to be working. At least it is a correct response from their API, not a connection timeout.
curl -x http://172.18.96.1:10809 https://unleash.codeium.com/api/client/features
{"error":"Not allowed to access"}It is still not working.
Lsyx-Good
commented
4 days ago existed same log content？ dns resolve failed？
gee666
commented
4 days ago (I think it is about the same)
And codeium output looks like this:
I0626 23:52:05.192694 16002 client.go:589] [DEBUG] GET https://server.codeium.com/exa.api_server_pb.ApiServerService/GetCompletions
2024-06-26 23:52:06.994 [ERROR]: fetch failed
2024-06-26 23:52:08.196 [INFO]: [Language Server (stderr)]:
I0626 23:52:08.195442 16002 client.go:646] [ERR] GET https://server.codeium.com/exa.api_server_pb.ApiServerService/GetCompletions request failed: Get "https://server.codeium.com/exa.api_server_pb.ApiServerService/GetCompletions": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
I0626 23:52:08.195485 16002 client.go:690] [DEBUG] GET https://server.codeium.com/exa.api_server_pb.ApiServerService/GetCompletions: retrying in 100ms (3 left)
2024-06-26 23:52:10.193 [INFO]: [Language Server (stderr)]:
I0626 23:52:10.192842 16002 client.go:646] [ERR] GET https://server.codeium.com/exa.api_server_pb.ApiServerService/GetCompletions request failed: Get "https://server.codeium.com/exa.api_server_pb.ApiServerService/GetCompletions": context deadline exceeded
W0626 23:52:10.192892 16002 proxy.go:128] proxy failed to connect: GET https://server.codeium.com/exa.api_server_pb.ApiServerService/GetCompletions giving up after 2 attempt(s): context deadline exceeded
.............................
E0626 23:53:12.193966 16002 unleash.go:60] Unleash error: Get "https://unleash.codeium.com/api/client/features": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
2024-06-26 23:53:12.195 [INFO]: [Language Server (stderr)]:
E0626 23:53:12.195028 16002 unleash.go:60] Unleash error: Post "https://unleash.codeium.com/api/client/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
2024-06-26 23:54:12.194 [INFO]: [Language Server (stderr)]:
E0626 23:54:12.193691 16002 unleash.go:60] Unleash error: Get "https://unleash.codeium.com/api/client/features": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
2024-06-26 23:54:12.194 [INFO]: [Language Server (stderr)]:
E0626 23:54:12.194771 16002 unleash.go:60] Unleash error: Post "https://unleash.codeium.com/api/client/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
try! disabled IPv6 address on tun mode settings and turn on routeonly on core basic settings, use that dns
{
"servers": [
{
"tag": "remote",
"address": "tls://8.8.8.8",
"detour": "proxy"
},
{
"tag": "local",
"address": "h3://223.5.5.5/dns-query",
"detour": "direct"
},
{
"tag": "block",
"address": "rcode://success"
}
],
"rules": [
{
"server": "block",
"rule_set": [
"geosite-category-ads-all"
]
},
{
"server": "remote",
"rule_set": [
"geosite-geolocation-!cn"
]
}
],
"final": "local"
}@Lsyx-Good when I disable ip v6 everything stops working completely, websites don't open, mailbox can't connect to imap etc but when I enable route only it seems to help. So with enabled route only and enabled ip v6 it seems to work now. Thank you. Hope it will keep working.
gee666
commented
4 days ago @Lsyx-Good also it's interesting that though internet and codeium now seem to be working normally, I still have this in the log, but it only appears when the log level is warning or error. When I switch to debug log level, these errors disappear. When I switch to error log level, they appear again. It might be some logging issue (?):
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for imap.gmail.com. IN A: context deadline exceeded
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for ipv6.msftconnecttest.com. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for unleash.codeium.com. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for unleash.codeium.com. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for ipv6.msftconnecttest.com. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for ipv4only.arpa. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for ipv4only.arpa. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for ipv6.msftconnecttest.com. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for www.msftconnecttest.com. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for ipv4only.arpa. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for www.msftconnecttest.com. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for ipv4only.arpa. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for ipv6.msftconnecttest.com. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for ipv4only.arpa. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR [1002142119 5.4s] dns: lookup failed for unleash.codeium.com: exchange4: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for ipv6.msftconnecttest.com. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR [1787435435 5.87s] dns: lookup failed for unleash.codeium.com: exchange6: context canceled | exchange4: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for ipv4only.arpa. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for www.msftconnecttest.com. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for ipv4only.arpa. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for www.msftconnecttest.com. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for ipv6.msftconnecttest.com. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR [1896685181 8.6s] dns: lookup failed for unleash.codeium.com: exchange4: context canceled
-0700 2024-06-27 00:28:16 ERROR [4173756479 8.74s] dns: lookup failed for unleash.codeium.com: exchange4: context canceled | exchange6: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for example.org. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for example.org. IN A: context canceled
-0700 2024-06-27 00:28:16 ERROR dns: exchange failed for detectportal.firefox.com. IN A: context deadline exceeded
-0700 2024-06-27 00:28:17 ERROR dns: exchange failed for imap.gmail.com. IN A: context deadline exceeded
-0700 2024-06-27 00:28:17 ERROR dns: exchange failed for mtalk.google.com. IN A: context canceled
-0700 2024-06-27 00:28:17 ERROR dns: exchange failed for go.microsoft.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:17 ERROR dns: exchange failed for clients4.google.com. IN A: context deadline exceeded
-0700 2024-06-27 00:28:17 ERROR dns: exchange failed for clients4.google.com. IN A: write tcp 192.168.1.102:58826->5.78.110.239:443: use of closed network connection
-0700 2024-06-27 00:28:17 ERROR dns: exchange failed for detectportal.firefox.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:17 ERROR dns: exchange failed for imap.gmail.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:17 ERROR dns: exchange failed for mtalk.google.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:18 ERROR dns: exchange failed for detectportal.firefox.com. IN A: context canceled
-0700 2024-06-27 00:28:18 ERROR [4021247525 9.42s] dns: lookup failed for vscode-sync.trafficmanager.net: exchange4: context canceled | exchange6: use of closed network connection
-0700 2024-06-27 00:28:18 ERROR dns: exchange failed for mtalk.google.com. IN A: context canceled
-0700 2024-06-27 00:28:18 ERROR dns: exchange failed for clients4.google.com. IN A: context canceled
-0700 2024-06-27 00:28:18 ERROR dns: exchange failed for imap.gmail.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:18 ERROR dns: exchange failed for imap.gmail.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:18 ERROR dns: exchange failed for detectportal.firefox.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:18 ERROR dns: exchange failed for detectportal.firefox.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:18 ERROR [3698287055 7.96s] dns: lookup failed for mobile.events.data.microsoft.com: exchange4: write tcp 192.168.1.102:58838->5.78.110.239:443: use of closed network connection | exchange6: use of closed network connection
-0700 2024-06-27 00:28:19 ERROR dns: exchange failed for mtalk.google.com. IN A: context canceled
-0700 2024-06-27 00:28:19 ERROR dns: exchange failed for mtalk.google.com. IN A: context canceled
-0700 2024-06-27 00:28:19 ERROR dns: exchange failed for clients4.google.com. IN A: context canceled
-0700 2024-06-27 00:28:19 ERROR dns: exchange failed for clients4.google.com. IN A: write tcp 192.168.1.102:58850->5.78.110.239:443: use of closed network connection
-0700 2024-06-27 00:28:20 ERROR dns: exchange failed for imap.gmail.com. IN A: context canceled
-0700 2024-06-27 00:28:20 ERROR dns: exchange failed for imap.gmail.com. IN A: context canceled
-0700 2024-06-27 00:28:20 ERROR dns: exchange failed for go.microsoft.com. IN A: write tcp 192.168.1.102:58887->5.78.110.239:443: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for detectportal.firefox.com. IN A: context canceled
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for mtalk.google.com. IN A: write tcp 192.168.1.102:58888->5.78.110.239:443: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for mtalk.google.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for detectportal.firefox.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for clients4.google.com. IN A: context canceled
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for clients4.google.com. IN A: write tcp 192.168.1.102:58889->5.78.110.239:443: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for go.microsoft.com. IN A: context canceled
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for client.wns.windows.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR [2795899301 15.81s] dns: lookup failed for www.google.com: exchange4: context canceled | exchange6: context canceled | upstream: context deadline exceeded
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for go.microsoft.com. IN A: context canceled
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for client.wns.windows.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for imap.gmail.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for go.microsoft.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for go.microsoft.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR [4111035970 3.15s] dns: lookup failed for mobile.events.data.microsoft.com: exchange6: context canceled | exchange4: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for edge-mqtt.facebook.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for us04logfiles.zoom.us. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for client.wns.windows.com. IN A: context canceled
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for client.wns.windows.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for client.wns.windows.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for imap.gmail.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for edge-mqtt.facebook.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for us04logfiles.zoom.us. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for imap.gmail.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for edge-mqtt.facebook.com. IN A: use of closed network connection
-0700 2024-06-27 00:28:21 ERROR dns: exchange failed for us04logfiles.zoom.us. IN A: use of closed network connection
-0700 2024-06-27 00:28:32 ERROR dns: exchange failed for server.codeium.com. IN A: context canceled
maybe you can search log file to found that error for log level debug
gee666
commented
4 days ago @Lsyx-Good codeium worked for 30 minutes and then stopped working again with the same symptoms. Even when it was working, it has some requests go through VPN, and some rejected with "context deadline exceeded". But eventually when most requests goes rejected, it says it reached the limit of failed connections and stops working.
I have no idea how to help it.
Lsyx-Good
commented
4 days ago you had above setting and dns on same time?
gee666
commented
4 days ago @Lsyx-Good I pasted it here, right? Yes, I have route only enabled and these dns settings like on the screenshot
Lsyx-Good
commented
4 days ago use that dns ,route only enabled and disable ipv6 address?That appear error?
Lsyx-Good
commented
4 days ago if have error, please provide log file( restart v2rayn after delete previous log file to collect log)
gee666
commented
3 days ago @Lsyx-Good eventually I don't manage to catch the error. Sometimes it works, sometimes it doesn't work with the same symptoms and logs I sent above. It doesn't depend on IP v6 and route only settings, and DNS settings. In all configurations it works sometimes, and sometimes not. I can't catch a pattern why the error occurs.
Lsyx-Good
commented
3 days ago other vps or procotol exist same problem? Can you send origin debug log file for above config(don't paste log)?
gee666
commented
1 day ago @Lsyx-Good here is the log file with these DNS settings, route only and IP v 6 disabled
and with these DNS settings internet is not working, it says ERR_NAME_NOT_RESOLVED
When I remove the DNS settings that you suggested internet starts working
gee666
commented
1 day ago @Lsyx-Good I have now more information about my problem
With "tun mode" activated almost all the requests from WSL return the error "deadline context exceeded"
Something's wrong with connections coming from WSL through the singbox tunnel. Maybe there is a way to set up singbox tun so it would not affect WSL connection? As far as I understand the address range of my WSL is 172.18.96.0/20 is there a way to tell singbox tun that these addresses are actually my local?
v2rayN is running on windows 11, the codeium is running under WSL in this same system
gee666
commented
1 day ago @Lsyx-Good it seems to be working finally!!! It started to work when I switched off the "strict route" option in tun settings.
预期情况
DNS exchange works
实际情况
DNS exchange failed and context deadline exceeded errors appear all the time in logs. Often internet doesn't work with the error ERR_NAME_NOT_RESOLVED
复现方法
I have
日志信息
额外信息
No response
我确认已更新至最新版本
我确认已查询历史issues