Skip to content
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

"Unable to reach api.nylas.com, retrying" message on connecting to different WiFi network #2243

Open
saligrama opened this issue May 16, 2016 · 10 comments
Labels

Comments

@saligrama
Copy link

I'm a student, and therefore I travel from home to school every day. When I get to school after having Nylas work properly at home, I get the error message here (https://i.imgur.com/G2kIAl8.png). However, it works fine after a suspend cycle at home or at school. Same deal coming home from school in the afternoon, leading me to believe it's a problem with switching networks.

What operating system are you using?

I'm using Arch Linux with kernel 4.5.4-1-ck, and GNOME desktop environment.

What version of N1 are you using?

I'm using n1 0.4.33-1 (the binary version from the AUR), which is the latest version.

Bug?

Do you have any third-party plugins installed?

None other than themes

Is the issue related to a specific email provider (Gmail, Exchange, etc.)?

I don't believe so, this looks like a Nylas server issue. I use a school Google Apps for Education account and a personal Gmail account.

Is the issue reproducible with a particular attachment, message, signature, etc?

Here's a screenshot of the message: https://i.imgur.com/G2kIAl8.png

@jackiehluo
Copy link
Contributor

@saligrama Hm... that sounds like it might just be the brief lack of connectivity when you've switched networks, not an error. Does it persist?

@saligrama
Copy link
Author

@jackiehluo It persists, and gives me the same message after trying again. If you killall the process and restart it then it works.

@fish22
Copy link

fish22 commented May 17, 2016

Having exactly the same problem here also. Had to kill the process and restart. I checked my internet connection and all was good. Other applications could connect. The only thing that happened was that the wifi access point changed when I went from home to the office.

I am also on archlinux and no plugins installed in n1.

@saligrama
Copy link
Author

It's also worth mentioning that if reconnecting to the same SSID after a disconnection (i.e., a sleep/wake cycle) it works as expected. Problem only arises after connecting to a different network.

@bengotow
Copy link
Contributor

Hmm - @fish22 are you experiencing this on Linux as well? This may b an issue with the way the network interface is exposed to NodeJS. N1 just tries to make an HTTPS request to our servers. If it works properly when reconnecting to the same SSID, but doesn't work when connecting to a different one, it may be something pretty low-level.

@bengotow bengotow added the linux label May 19, 2016
@2xG
Copy link

2xG commented May 21, 2016

Archlinux too, same problem. I'm switching between two WiFi networks and LAN wired connection. Also I'm using Network Manager to switch connections.

@zetzrn
Copy link

zetzrn commented Aug 31, 2016

Got the same problem… Manjaro Linux (Arch based)
Everytime I switch from Univesity to Home Wifi Nylas won't sync.
its super annoying -.-

@Bergg
Copy link

Bergg commented Sep 18, 2016

killall
Same problem here - Fedora24 and N1 0.4.52

Have to issue a 'killall nylas' to propertly stop N1, and then a panel pops up two times before I can launch it again.

@ghost
Copy link

ghost commented Oct 23, 2016

Ugh, same problem. Just ran across it setting up an Amazon Echo, when you have to connect to the devices wifi and then switched back to home network.

Used System Monitor to kill all Nylas functions, reopened Nylas, seems to work for now.

Antergos (Arch Linux)

@TheSinding
Copy link

I do too.
Hoped you fixed it when you moved from N1 -> Mail 2.0..
But it seems its just a repacked N1 client, because all the bugs that was with the N1 client still exist in this version.
Eg
This pullrequest #3238 which fixes #3219 #2809 with the signature editor.
This #2243 #3015 #1146 connectivity bug.

Is there a roadmap, or a timeline on how soon you are gonna fix it ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants