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

Usage behind a proxy #104

Open
arturo182 opened this Issue Oct 21, 2015 · 54 comments

Comments

Projects
None yet
@arturo182
Copy link

arturo182 commented Oct 21, 2015

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

This comment has been minimized.

Copy link

valeriocuscuna commented Oct 21, 2015

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

@sergiokopplin

This comment has been minimized.

Copy link

sergiokopplin commented Oct 21, 2015

+1

1 similar comment
@toXel

This comment has been minimized.

Copy link

toXel commented Oct 23, 2015

+1

@sergiokopplin

This comment has been minimized.

Copy link

sergiokopplin commented Oct 28, 2015

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

@buhe

This comment has been minimized.

Copy link

buhe commented Oct 29, 2015

great work!

@gutenye

This comment has been minimized.

Copy link

gutenye commented Oct 30, 2015

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

@sergiokopplin

This comment has been minimized.

Copy link

sergiokopplin commented Oct 30, 2015

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

@sboss

This comment has been minimized.

Copy link

sboss commented Nov 5, 2015

+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

This comment has been minimized.

Copy link

vincihu commented Nov 24, 2015

+1. sock5 proxy

@tonybenoy

This comment has been minimized.

Copy link

tonybenoy commented Dec 18, 2015

+1

@grinich

This comment has been minimized.

Copy link
Contributor

grinich commented Jan 8, 2016

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.

@grinich grinich closed this Jan 8, 2016

@mbilker

This comment has been minimized.

Copy link
Contributor

mbilker commented Jan 8, 2016

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

@edwinyzh

This comment has been minimized.

Copy link

edwinyzh commented Jan 14, 2016

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

@mbilker

This comment has been minimized.

Copy link
Contributor

mbilker commented Jan 14, 2016

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

@mbilker

This comment has been minimized.

Copy link
Contributor

mbilker commented Jan 14, 2016

I don't remember the specifics of the override.

@bonaldi

This comment has been minimized.

Copy link

bonaldi commented Jan 29, 2016

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.

@mbilker mbilker reopened this Jan 29, 2016

@lalitkapoor

This comment has been minimized.

Copy link

lalitkapoor commented Feb 26, 2016

@bengotow

This comment has been minimized.

Copy link
Contributor

bengotow commented Feb 26, 2016

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

This comment has been minimized.

Copy link

msmosso commented Feb 29, 2016

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

@mbilker

This comment has been minimized.

Copy link
Contributor

mbilker commented Feb 29, 2016

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).

@arrowrowe arrowrowe referenced this issue Mar 1, 2016

Closed

Weekly for 2016/03/02 #44

4 of 8 tasks complete
@ex0b1t

This comment has been minimized.

Copy link

ex0b1t commented Mar 4, 2016

+1

@brwolfgang

This comment has been minimized.

Copy link

brwolfgang commented May 3, 2016

You can follow up what is being developed on Waffle.
Filter the board using "proxy" to see where it is. Currently there's no one working on it =/

@cmmata

This comment has been minimized.

Copy link

cmmata commented May 5, 2016

+1

@jrm06

This comment has been minimized.

Copy link

jrm06 commented May 11, 2016

Nylas N1 is great but it's unusable at work. Please, add proxy support. Or maybe you know a software or a tips for Nylas N1 can force proxy.

@lalitkapoor

This comment has been minimized.

Copy link

lalitkapoor commented May 11, 2016

might be able to get away with something like this on the mac (they have windows version too) https://www.proxifier.com/mac/

@zaaack

This comment has been minimized.

Copy link

zaaack commented Jun 30, 2016

+1

@hallamoore

This comment has been minimized.

Copy link
Contributor

hallamoore commented Jul 8, 2016

@anxsec

This comment has been minimized.

Copy link

anxsec commented Aug 25, 2016

@arturo182 on linux, just run with --proxy-server param.

nylas --proxy-server=socks5://127.0.0.1:1080

@viveris-villeurbanne

This comment has been minimized.

Copy link

viveris-villeurbanne commented Sep 23, 2016

@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

This comment has been minimized.

Copy link

louisrubet commented Oct 4, 2016

+1

Still no progress on that ?

@jenghung

This comment has been minimized.

Copy link

jenghung commented Nov 1, 2016

+1

@wuairc

This comment has been minimized.

Copy link

wuairc commented Dec 8, 2016

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

@fffx

This comment has been minimized.

Copy link

fffx commented Jan 12, 2017

+1

@fffx

This comment has been minimized.

Copy link

fffx commented Jan 12, 2017

It works with proxychains

$ proxychains nylas # from terminal

@oikonomopo

This comment has been minimized.

Copy link

oikonomopo commented May 3, 2017

+1

1 similar comment
@m31271n

This comment has been minimized.

Copy link

m31271n commented May 19, 2017

+1

@nelsonhoover

This comment has been minimized.

Copy link

nelsonhoover commented May 24, 2017

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

@ConeyLiu

This comment has been minimized.

Copy link

ConeyLiu commented Jun 8, 2017

Any update on this ?

@NoZiL

This comment has been minimized.

Copy link

NoZiL commented Jun 20, 2017

+1

@Cris70

This comment has been minimized.

Copy link

Cris70 commented Jul 5, 2017

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

This comment has been minimized.

Copy link

Cris70 commented Jul 7, 2017

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

This comment has been minimized.

Copy link

Cris70 commented Jul 11, 2017

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

@karnikram

This comment has been minimized.

Copy link

karnikram commented Jul 21, 2017

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

@unkemptArc99

This comment has been minimized.

Copy link

unkemptArc99 commented Sep 10, 2017

+1

@livc

This comment has been minimized.

Copy link

livc commented Nov 11, 2017

@fffx awesome!! it works.

@livc

This comment has been minimized.

Copy link

livc commented Nov 11, 2017

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

@Cris70

This comment has been minimized.

Copy link

Cris70 commented Nov 12, 2017

@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

This comment has been minimized.

Copy link

rothn commented Dec 5, 2017

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"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment