Nylas-mail: With new N1, can't connect to sync engine

Created on 16 Jun 2016 · 12Comments · Source: nylas/nylas-mail

After upgrading N1 to the new 0.45 release, I can no longer connect to my locally installed sync-engine. Launching N1, I get a dialog to sign-up for a Nylas ID, and then an error that N1 can't connect to an onboarding page at localhost:5009. I've tried updating the sync-engine, but no luck.

Also, it continues to be impossible to change a password if you're using the local sync engine. You end up creating an entirely new account entry. Besides re-downloading everything, that also means there are then multiple account entries in the database with the same name, and API calls begin to fail for that reason.

What operating system are you using?

Ubuntu 16.04

What version of N1 are you using?

.45

Bug?

Do you have any third-party plugins installed?

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

Source

elbamos

👍4

Most helpful comment

@jackiehluo Well, its good to know you're working on it.

Going back to the old one isn't a great option. The reason I was so eager for the new one, is that I hoped it would fix the duplicate-account bug, where if you change a password you end up with two accounts with the same name, and then the API breaks, etc.

elbamos on 17 Jun 2016

👍3

All 12 comments

My Nylas N1 client receive mails and I can send it to another recipients. But currently it will not sync it to my google mail account. I think this issue is related with the reported issue from @elbamos :) Anyone have a solution for that?

xyNNN on 16 Jun 2016

Hey @xyNNN this is specifically with regards to a user hosting their own Sync Engine in Vagrant, etc. Are you doing that too?

Omeryl on 16 Jun 2016

No, then I will create my own issue. My problem is that I read, label or archive a mail and on my mobile client or dssktop google mail client it will show up the mails as unread and unlabled, anyone have this issue?

xyNNN on 16 Jun 2016

The issue I raised seems like it may be universal for those of us who sync locally. Hello?

elbamos on 17 Jun 2016

@elbamos We're working on it—we thought that people could add pretend Nylas IDs in config.json, but it's going to be a more complicated fix. For now, could you try rolling back to the last version of N1?

jackiehluo on 17 Jun 2016

🎉1

@jackiehluo Well, its good to know you're working on it.

elbamos on 17 Jun 2016

👍3

I am LOVING Nylas!!! You guys are my HEROES!!! I have to run it locally though (because we are a small startup and can't afford the hosting fees yet), but thats ok cause we are technical enough to set it all up :) (well mostly :P)

Anyway, we are also experiencing the same issue. I'm using the pro trial for now. It's free so can't complain or tell you to hurry, but would love to be able to run the local version as soon as we can. We are developing an internal system to manage ourselves i.e. work orders, support, sales staff and integrating with google calendar and mail etc. via the API looks so much simpler than trying to do it directly. Great work guys!!!

systemeintegratedsolutions on 20 Jun 2016

I am experiencing the same problem. @jackiehluo I hope it will fixed very soon :worried:

ersinpw on 3 Jul 2016

Is this fixed? Because I am still getting this error
screen shot 2016-07-15 at 11 40 49
Even when I change the ip address in config.json

It does not work

ersinpw on 15 Jul 2016

Still doesn't work.

miedzinski on 15 Jul 2016

@miedzinski @ersinpw Which commit are you running? The fix is in #2485, and you'll get it if you build from source. The releases still seem to be at 0.4.45.