Usage behind a proxy

[arturo182]

Hi,

I'm trying to use N1 behind a corporate proxy. I'm using Ubuntu and have both $http_proxy and $https_proxy set.

I set up my private gmail acount and that part worked, but I cannot send any emails, I get the "Your draft could not be sent. Please check your connection and try again" error. I'm also trying to setup Exchange account and I get "Tunneling socket could not be established, cause=write EPROTO".
Also for Exchange, shouldn't there be an option supplying EWS URL?

Thanks!

[valeriocuscuna]

+1.
I would like to have the option to manually set proxy / use system settings (reloaded without reloading N1).
Thanks
Valerio

[sergiokopplin]

+1

[toXel]

+1

[sergiokopplin]

it's working after the last update! o//

[buhe]

great work!

[gutenye]

+1 It's very important for users in China.
@sergiokopplin What are the steps to use it?

[sergiokopplin]

@gutenye for me, just the update was enough. Nothing more.

[sboss]

+1 this would be great for when people travel to networks that aren't their own and have to work behind a proxy server (like visiting corporate clients).

[vincihu]

+1. sock5 proxy

[tonybenoy]

+1

[grinich]

Sounds like this is fixed so I'm going to close! We generally recommend setting up your OS's networking configuration to use the desired proxy settings.

[mbilker]

@grinich World this work for NylasAPI requests which are made through the node request module?

[edwinyzh]

What a pity! I wouldn't be able to use it in China until it supports proxy.

[mbilker]

@edwinyzh If you want to implement the feature, you can override the request module to use a proxy.

[mbilker]

I don't remember the specifics of the override.

[bonaldi]

Can this be reopened, @grinich? Doesn't seem to be fixed, at least for me, and also for some others going by the new tickets @mbilker and others are rolling into this one.

[lalitkapoor]

maybe helpful: https://www.npmjs.com/package/global-tunnel

[bengotow]

Thanks for the link @lalitkapoor. It looks like that'd do the trick, but we may try to rewrite our HTTP request logic to use XMLHTTPRequest instead of the request library. Chromium does some really nice auto-detection of system proxy settings, and we'd like to be able to use that rather than making users provide proxy settings, or trying to read them on each platform ourselves. Stay tuned!

[msmosso]

+1 for manually proxy configuration. I'm running N1 on Windows, behind a corporate proxy, and it doesn't reach the api.

[mbilker]

This is in development.
On Mon, Feb 29, 2016 at 8:34 AM Matheus Mósso notifications@github.com
wrote:

+1 for manually proxy configuration. I'm running N1 on Windows, behind a
corporate proxy, and it doesn't reach the api.

—
Reply to this email directly or view it on GitHub
#104 (comment).

[ex0b1t]

+1

[viveris-villeurbanne]

@anxsec

• option --proxy-server param does not work for me
• neither does http_proxy and https_proxy correctly set

-> still a proxy problem for me ! (OS Kubuntu 16.04)
Are you guys still facing this proxy problem ?

[louisrubet]

+1

Still no progress on that ?

[jenghung]

+1

[wuairc]

+1, can not use it reliably without proxy for work

[fffx]

It works with proxychains

$ proxychains nylas # from terminal

[oikonomopo]

+1

[ghost]

+1

[nelsonhoover]

No proxy means it's unusable for me on some networks behind firewalls.

[ConeyLiu]

Any update on this ?

[NoZiL]

+1

[Cris70]

I'm having this problem too, I think.
When I try to add an Office365 account, it wait for a few seconds with the "Adding account..." caption on the button, the it stops and shows a red message: "Greeting never received".
However, I know the account works because I can connect without problems with Wavebox.

This is what I get in the log file:

{"host":"xmper8q3.gcv.dom","timestamp":"2017-07-05T11:10:12.734Z","payload":"Error\n    at new APIError (/src/flux/errors.es6:57:19)\n    at Request._callback (/src/flux/nylas-api-request.es6:75:26)\n    at Request.self.callback (/usr/share/nylas-mail/resources/app.asar/node_modules/request/request.js:186:22)\n    at emitTwo (events.js:106:13)\n    at Request.emit (events.js:191:7)\n    at Request.<anonymous> (/usr/share/nylas-mail/resources/app.asar/node_modules/request/request.js:1081:10)\n    at emitOne (events.js:96:13)\n    at Request.emit (events.js:188:7)\n    at IncomingMessage.<anonymous> (/usr/share/nylas-mail/resources/app.asar/node_modules/request/request.js:1001:12)\n    at IncomingMessage.g (events.js:286:16)\n    at emitNone (events.js:91:20)\n    at IncomingMessage.emit (events.js:185:7)\n    at endReadableNT (_stream_readable.js:974:12)\n    at _combinedTickCallback (internal/process/next_tick.js:74:11)\n    at process._tickDomainCallback (internal/process/next_tick.js:122:9)"}
{"host":"xmper8q3.gcv.dom","timestamp":"2017-07-05T11:10:12.737Z","payload":{"fingerprint":["{{ default }}","api error","http://localhost:2578/auth",500,"Greeting never received"],"rateLimit":{"ratePerHour":30,"key":"APIError:http://localhost:2578/auth:500:Greeting never received"},"pluginIds":[]}}
{"host":"xmper8q3.gcv.dom","timestamp":"2017-07-05T11:10:12.764Z","payload":"{ Error\n    at new APIError (/src/flux/errors.es6:57:19)\n    at Request._callback (/src/flux/nylas-api-request.es6:75:26)\n    at Request.self.callback (/usr/share/nylas-mail/resources/app.asar/node_modules/request/request.js:186:22)\n    at emitTwo (events.js:106:13)\n    at Request.emit (events.js:191:7)\n    at Request.<anonymous> (/usr/share/nylas-mail/resources/app.asar/node_modules/request/request.js:1081:10)\n    at emitOne (events.js:96:13)\n    at Request.emit (events.js:188:7)\n    at IncomingMessage.<anonymous> (/usr/share/nylas-mail/resources/app.asar/node_modules/request/request.js:1001:12)\n    at IncomingMessage.g (events.js:286:16)\n    at emitNone (events.js:91:20)\n    at IncomingMessage.emit (events.js:185:7)\n    at endReadableNT (_stream_readable.js:974:12)\n    at _combinedTickCallback (internal/process/next_tick.js:74:11)\n    at process._tickDomainCallback (internal/process/next_tick.js:122:9)\n  name: 'APIError',\n  error: null,\n  body: { message: 'Greeting never received', type: 'api_error' },\n  requestOptions: \n   { url: 'http://localhost:2578/auth',\n     method: 'POST',\n     json: true,\n     timeout: 180000,\n     path: '/auth',\n     body: \n      { provider: 'office365',\n        email: 'guadagnino.cristiano@AMENDEDt',\n        name: 'Cristiano Guadagnino',\n        settings: [Object] } },\n  statusCode: 500,\n  message: 'Greeting never received',\n  errorType: 'api_error' } { pluginIds: [] }\n"}
{"host":"xmper8q3.gcv.dom","timestamp":"2017-07-05T11:10:13.028Z","payload":"undefined\n"}
{"host":"xmper8q3.gcv.dom","timestamp":"2017-07-05T11:10:13.029Z","payload":"undefined\n"}
{"host":"xmper8q3.gcv.dom","timestamp":"2017-07-05T11:10:13.029Z","payload":"undefined\n"}

I tried to proxify nylas-mail with proxychains-ng but it did not work (nylas-mail or proxychains hangs).

Any suggestion?

TIA
Cris

p.s. I did not say it before, but I'm behind an enterprise firewall too

[Cris70]

Instead of using the proxychains-ng executable available in openSUSE's repos (which is v4.11), I compiled it myself (v4.12).

proxychains-ng itself worked ok after compiling my private copy, but nylas-mail did not.

Apparently nylas-mail is always trying to connect to this address: http://localhost:2578/auth, which does not seems correct to me.
It is doing this both when I launch it alone and when I proxify it through proxychains-ng.

Any ideas?

TIA
Cris

[Cris70]

Replying to myself: adding localnet 127.0.0.0/255.0.0.0 to my proxychains.conf file made nylas-mail work!!

[karnikram]

Not able to get it to work through proxychains. Can anyone help?

[unkemptArc99]

+1

[livc]

@fffx awesome!! it works.

[livc]

Sorry, in my situation, it only can log into Gmail but can not send emails with proxychains.

[Cris70]

@livc are you sure you cannot?
In my case, sending takes a long time (about a minute) but in the end it succeeds.
Don't know why it takes so long, though.

[rothn]

I can't use nylas at all -- I have the http_proxy, https_proxy, and no_proxy env vars set properly in my environment. No matter what I try to configure, it fails with some type of error. For GMail it says "Could not establish tunneling socket"