Doesn't work behind proxy

[fannheyward]

Doesn't work behind proxy

[fannheyward]

How is your proxy configured? The fetch used is not https://github.com/github/fetch, but fetch model provided by coc.nvim https://github.com/neoclide/coc.nvim/blob/master/src/model/fetch.ts

[cprn]

This I didn't expect. I have the same proxy configuration in both Gnome and environment variables. It usually works fine when applications support system-wide proxy settings.

Gnome:

~/.bashrc:

export http_proxy=http://proxiac:8080
export https_proxy=http://proxiac:8080
export ftp_proxy=http://proxiac:8080
export rsync_proxy=http://proxiac:8080
export all_proxy=http://proxiac:8080
export no_proxy="localhost,cy,127.0.0.1,127.0.0.1/8,::1,10.0.0.0/16,*.intra"

export HTTP_PROXY=$http_proxy
export HTTPS_PROXY=$https_proxy
export FTP_PROXY=$ftp_proxy
export RSYNC_PROXY=$rsync_proxy
export ALL_PROXY=$all_proxy
export NO_PROXY=$no_proxy

I also tried to replace our proxy hostname with IP but it didn't change anything. To make it even more interesting, :CocInstall works okay - my guess is it uses the same fetch implementation(?).

I've found out Intelephense (PHP Language Server) looks for proxy in process.env.https_proxy during license activation and it fails as well. Is this the same place coc-marketplace checks for proxy setting? Is the value logged somewhere? My guess is it's coc.nvim's issue on Linux even though calling :echo $https_proxy in VIM outputs the environment variable value.

[fannheyward]

This has been fixed on coc.nvim mater neoclide/coc.nvim@f4d9aca

[cprn]

The issue was never related to lower or upper case, I have all environment variables declared in both. I'll post it upstream, though.

[fannheyward]

Yes, both :CocInstall and coc-marketplace are using same fetch model.

You can try to add "http.proxy": "proxiac:8080" to coc-settings.json.

[fannheyward]

Can you see Using proxy from... from :CocOpenLog?

[cprn]

It's a false alarm... a tricky one I would never expect, but still, not an issue in coc-marketplace, I think, but rather coc.nvim::fetch does something our proxy config doesn't like. When I connect to http://registry.npmjs.com in the browser or with curl (through proxy) all works fine but when coc.nvim::fetch connects to that URL (through proxy) it gets 403 Forbidden. If by any chance it is anything that should be fixed on your end I'll let you know. I had the same issue with Intelephense when it was using built-in node.js module to activate the license and Ben Mewburn fixed it by switching to request module instead (and by implication fixed coc-phpls for me around version 1.3.7, see bmewburn/vscode-intelephense#915).

For the completeness sake - yes, I see proxy in the log:

   11 2020-01-03T16:21:15.095 INFO (pid:29407) [model-fetch] - fetch: http://registry.npmjs.com/-/v1/search?text=keywords:coc.nvim&size=200&from=0
   12 2020-01-03T16:21:15.095 INFO (pid:29407) [model-fetch] - Using proxy from: proxiac:8080

And I can confirm it's correctly read from coc-settings.json (when set) or from environment variable.

[cprn]

Few months passed and I still don't know why it doesn't work but I don't think it's something that concerns other users so I'm closing the issue. Have an awesome week, cheers!