Error: Request failed exit_code: 60
hoofcushion opened this issue · 10 comments
Hello, I been using this plugin for a while and it's a good work, but recently it's not working and I check the logfile, here's what it saids:
Verbose logging started: 2024-04-25 14:31:00
Log level: WARN
Calling process: /home/Hoofcushion/.local/share/bob/nightly-6725565/nvim-linux64/bin/nvim
Neovim version: {
buildtype = "RelWithDebInfo",
luajit = "2.1.1707061634",
nvim = "v0.10.0-dev-2295+g672556525"
}
Process ID: 169472
Parent process ID: 169470
OS: {
machine = "x86_64",
release = "6.8.7-arch1-1",
sysname = "Linux",
version = "#1 SMP PREEMPT_DYNAMIC Wed, 17 Apr 2024 15:20:28 +0000"
}
================================================================================
[ERROR] [2024-04-25 14:31:00.457] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
[ERROR] [2024-04-25 14:31:04.073] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
================================================================================
Verbose logging started: 2024-04-25 14:32:35
Log level: WARN
Calling process: /home/Hoofcushion/.local/share/bob/nightly-6725565/nvim-linux64/bin/nvim
Neovim version: {
buildtype = "RelWithDebInfo",
luajit = "2.1.1707061634",
nvim = "v0.10.0-dev-2295+g672556525"
}
Process ID: 169721
Parent process ID: 169718
OS: {
machine = "x86_64",
release = "6.8.7-arch1-1",
sysname = "Linux",
version = "#1 SMP PREEMPT_DYNAMIC Wed, 17 Apr 2024 15:20:28 +0000"
}
================================================================================
[ERROR] [2024-04-25 14:32:35.329] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
[ERROR] [2024-04-25 14:32:35.119] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
[ERROR] [2024-04-25 14:32:36.292] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
[ERROR] [2024-04-25 14:32:36.663] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
[ERROR] [2024-04-25 14:32:36.847] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
[ERROR] [2024-04-25 14:32:37.412] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
[ERROR] [2024-04-25 14:32:37.630] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
[ERROR] [2024-04-25 14:32:40.616] [fittencode.nvim] Request failed; exit_code: 28, error: { "" }
[ERROR] [2024-04-25 14:32:54.604] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
[ERROR] [2024-04-25 14:32:58.842] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
[ERROR] [2024-04-25 14:33:00.880] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
[ERROR] [2024-04-25 14:33:02.650] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
[ERROR] [2024-04-25 14:33:03.997] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
[ERROR] [2024-04-25 14:33:06.831] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
[ERROR] [2024-04-25 14:33:06.023] [fittencode.nvim] Request failed; exit_code: 60, error: { "" }
What does that means? is there a way to fix it?
FYI I tried to use old version of this plugin or Neovim, still not working. I guess it's the fittencode itself has some problem.
I also have the same problem after an update to the latest commit.
- Error code 28 means connection time out.
- Error code 60 means that cURL is not able to verify the SSL certificate.
Does cURL use a proxy server?
I guess you're right, it's probably network's problem. Cause now it's working. And I didn't see anything goes wrong.
I don't use proxy server. Currently, it also works for me without any changes in configuration.
- Error code 28 means connection time out.
- Error code 60 means that cURL is not able to verify the SSL certificate.
Does cURL use a proxy server?
The problem occurs again. After updating to the latest version, the output is more detailed.
As you mentioned, the problem is related to the SSL certificate. Following the log, I added the option of "--insecure" to the list of arguments.
It works perfectly now.
This is because the completion URLs have already been updated, and the old ones have expired.
Fixed by b3344ff
Please update to the latest commit.
Thanks, I will try!
fixed
I think everything is fine now, thank for your work!