Joplin: Synchronization does not support proxy

[gibboni]

Operating system

• [X ] Windows 7
• [X ] Windows 10

Application

• [X ] Desktop

Error

The desktop-app does not support proxy or it fails to use system-wide proxy settings. When the synchronise-button is pressed, nothing seem to happen. There is no visible error message. The error, ECONNREFUSED, is however logged properly into the log file.

[laurent22]

I'm wondering, is it the application that fails to use the proxy, or OneDrive that is refusing connections via this proxy? Does the native OneDrive client work in this setup?

[gibboni]

Native OneDrive works just fine. Based on the log, the app tries to connect directly to graph.microsoft.com. Are there any environment or command line settings I could try?

[laurent22]

It seems Node indeed does not use the system proxy settings by default - https://stackoverflow.com/a/27825729/561309 So this will need to be implemented

[jogi4github]

Is there a way to tackle this on windows systems. On Linux I guess an export of http[s]_proxy will work - but what about Windows? I was not able to find a hack for the proxy issue here...

[artelse]

I get the same reason: connect ECONNREFUSED error when trying to connect to a local webdav server. Is there a workaround/solution?

[aksdb]

On Linux I also get ECONNREFUSED, even though I have http[s]_proxy set.

[crequill]

Same problem here on linux: with http[s]_proxy set, I get network timeout error with desktop application and nextcloud synchronization.

[cossio]

Same problem here. Trying to setup Dropbox sync, but it gets stuck in the "Enter the code provided by Dropbox" dialog.

I am on Linux, with $http_proxy set.

[PyroP]

Same problem here in Windows 10.

[think-nice-things]

Hi -- any update on this?
I'm on windows 7 and the system proxy isn't recognized :-(

[garzy]

same problem too. Windows version must have a dialog for configure proxy setttiongs.

Thanks!

[Wildbill-Z]

Is there any way to handle that manually? I'm using the portable app with Windows 7 and just got stuck as it is not recognizing the system-wide settings for the proxy server which is used here at the side.
Would be good to get this solved as now Joplin is a bit of useless here at my place of work.

Nevertheless, on Android and my private Linux its just amazing. :+1:

Greets, Jürgen

[jogi4github]

Hello Jürgen,

I got it working by installing the NextCloud client, syncing the folder with the md files and configuring a file system snyc in Joplin.
Not sure if this is the best way, but at least it works for me.

• Jogi

[Wildbill-Z]

Hi,

yeah, that would be an idea but just a bit of overkill. Instead of installing an further app to sync files it would be great if Joplin could handle proxy settings by its own or just use the system settings.
But thanks. I think this will be fixed in the future and until then, your idea is a nice workaround. I just don't want to install any file sync tool as thats not wanted here at the place but could sync files manually. :-)

Greets, Jürgen

[laurent22]

Implemented there: https://github.com/laurent22/joplin/commits/proxy_test but there are issues with timeout when the provided proxy URL is incorrect (the requests never time out) so that still needs to be fixed. The underlying network lib unfortunately doesn't allow controlling timeout properly so not sure what the fix is at this point.

[dimpflmoser]

Excellent, is there a binary / AppImage to test it?
The effect of requests that don't time out also exist today if you run the App behind a proxy, so it's no step backwards only one forward.

[laurent22]

No binary yet as I consider it's not stable enough for release. If you think it could be use, I can add it to the next release anyway and mark it as "Alpha" for instance.

[dimpflmoser]

It's definitely a valuable feature. Currently I use Android-Only (NextCloud) Notes by Stefan Niedermann, however it's markdown capabilities are rather limited. On the other hand editing Notes, especially migrating my existing notes on your Android client is a pain, so I would like to do it on the desktop. At work I'm caught behind a firewall and a proxy I cannot use it right now.

Sure a fallback if the proxy is not reachable would be great, however I'd regard that as the second step.

[aksdb]

I would also be happy about that feature - even if marked as "alpha" or "use at your own risk".

[dimpflmoser]

There have been a few releases since the last update on this issue, however I haven't seen an option in those updates. Is there an option to test to connect-via-proxy feature without compilation from source?

[laurent22]

The branch I had seemed to be working, at least with the local Squid proxy I had setup. But I've later tried with a regular proxy on the web and it didn't work. I'm not sure it works at all actually so it won't released for now.

[dimpflmoser]

What a shame, anyway thanks for your effort. - Still waiting (impatiently). :-)

[janLo]

This must be a regression as it seemed to have worked a while ago.

I use joplin behind a proxy. It synchronized a while ago (to nextcloud) but today I discovered that it stopped. This renders it completely useless for me. Other electron-apps (like Signal, Spotify, ..) work fine in this environment.

[bhlevca]

It appears there is a way to force node.js apps to go through a proxy with global-tunnel-ng

var globalTunnel = require('global-tunnel-ng');

globalTunnel.initialize({
    host: '10.0.0.10',
    port: 8080,
    proxyAuth: 'userId:password', // optional authentication
    sockets: 50 // optional pool size for each http and https
});

Link

Perhaps this is the way to go.

[dimpflmoser]

Am I wrong to believe this issue has been abandoned?

[bhlevca]

It is not OneDrive only, all sync methods fail behind proxy

On Mon, 3 Dec 2018 at 16:40, dimpflmoser [e-mail] wrote:

Am I wrong to believe this issue has been abandoned?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/laurent22/joplin/issues/164#issuecomment-443880456,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALI3l9urSwweyDIBQr-6xgNb_DHFCazks5u1ZpDgaJpZM4Rea4k
.

[SolomonSklash]

I'm also eagerly watching this issue, hoping for a fix. I'm using Windows 10, syncing to Nextcloud, and I have to use a proxy to hit it.

[laurent22]

I could not find a satisfying solution so for now it's more or less on hold. Main issue is that if connection or anything doesn't work with the proxy, it's not possible to get proper errors (connection never times out). So often I don't know if it's the app or the proxy or something else that's not working.

Because in-depth work and specialist knowledge is needed for this feature, perhaps a bounty or some form of crowdfunding would help find someone to look into it and submit a pull request.

[bhlevca]

I posted in one of the forums a request and a proposal that uses node.js
capability to work with a proxy. Joplin is not the only node.js app that
has this issue. Others have looked into this already. On the Signal for
desktop forum there is an entire thread about it.

On Mon, Dec 3, 2018, 19:18 Laurent Cozic <[email protected] wrote:

I could not find a satisfying solution so for now it's more or less on
hold. Main issue is that if connection or anything doesn't work with the
proxy, it's not possible to get proper errors (connection never times out).
So often I don't know if it's the app or the proxy or something else that's
not working.

Because in-depth work and specialist knowledge is needed for this feature,
perhaps a bounty or some form of crowdfunding would help find someone to
look into it and submit a pull request.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/laurent22/joplin/issues/164#issuecomment-443920899,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALI3kn_GQGk-3vIo2zMx3_DI0Qt4Iqmks5u1b9SgaJpZM4Rea4k
.

[dimpflmoser]

@laurent22 As far as I know it's the same issue with firefox: If your proxy accepts your request but doesn't deliver data Firefox hangs forever. Of course this is crap, but I guess it's the price we have to pay to have a crap proxy.

[think-nice-things]

yeah, I'm also "eagerly" watching this topic.
Didn't succed in building the proxy test version myself to test.
If someone would provide a binary test version (windows) I'd be happy to do some beta testing :-)

[SolomonSklash]

I'm also willing to test on Windows.

[davidlauhn]

Still...

[0x7878]

So sad... I'm using Joplin on my mobile phone and would be really glad If i could using it behind a Corporate Proxy. So please fix it.

[theslash]

Any news on this? It's the one feature that's missing for me

[StefanTT]

Too bad that there is no solution for the proxy problem. Otherwise Joplin would be nearly perfect for my needs. Unfortunately a show stopper for me.

[nikosvaggalis]

That's true.I can't access my notes from work because I'm behind an NTLM proxy.Isn't there a work around like with using cntlm, or does Jopplin not work with a proxy at all,that is, not even accept a proxy as a an option?

[StefanTT]

I tried the typical environment variables for setting a proxy without success. And I think it simply does not work as the comments above in this thread state.

The use of an external sync tool is possible, of course.

[kenden]

To make this bug easier to find from google:
the error message received when trying to sync joplin with dropbox on a mac is:

Could not authorise application:

request to https://api.dropboxapi.com/oauth2/token failed, reason: connect ETIMEDOUT 170.135.66.9:443

Please try again.

[g4c]

Hi, thanks for the app :-)

Also missing the proxy feature.

As a workaround I use sockscap64 on Windows. It has also a portable version

[jmleroy]

I also have this problem at my office when working behind a corporate proxy.
I thought I could bypass the problem by using instead the filesystem sync on the joplin folder in my nextcloud folder, but my Joplin instances don't seem to be synced.

[0x7878]

@jmleroy I made a similar experience with syncing on the Filesystem, mainly when you use another device that syncs normally.

@g4c Are you behind a Corporate socks proxy? I mean, I know Sockscap, but it didn't work on HTTP Proxies (at least not for me).

[kleinfelter]

OK. If sync doesn't work through a proxy, how well does Joplin work with epically delayed sync?

e.g. If I use Joplin at work (with a proxy, and sync fails) one day, and I use Joplin at home the next day (and sync works), what sorts of problems am I going to run into:

1. With no concurrent updates to the same file?
2. With concurrent updates to the same file?

[g4c]

@0x7878 Yes, corporate http proxy on port 80, no authorisation. Will give you more details how to configure once in the office.

[g4c]

@0x7878 Ok, that's easy. I did it long time ago and completely forgot - just using daily and that's it.
You just need to click Proxy to start Proxy Manager. Then just insert row and fill Proxy Address, Port (80), SOCKS Type (choose HTTP). Good luck!

[stale[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "backlog" and I will leave it open. Thank you for your contributions.

[g4c]

Nope, it has not been fixed and I'm still waiting for a solution not requiring workarounds (using third party software)
Regards
GC

[kenden]

Related/duplicate: https://github.com/laurent22/joplin/issues/1117

Edit: fixed the link

[indirection]

Again for another duckduckgo.com (or google) search result, my error message:

FetchError: request to https://public.dm.files.1drv.com failed, reason: unable to get local issuer certificate
at ClientRequest. (/Applications/Joplin.app/Contents/Resources/app/node_modules/node-fetch/index.js:133:11)

[indirection]

Thank you for Joplin!

I've tried every work around that I could find.

Completed: 2020-04-06 8:27 PM
Last error: FetchError: request to https://public.dm.files.1drv.com/-snip-/version.txt failed, reason: unable to get local issuer certificate

This example is behind the Cisco Umbrella proxy.

Spotify and Signal work without issue.

[bhlevca]

As far as I know the code to work with proxy has not been implemented yet.
I posted some suggedtions and someone has succeded to do it in a kludgy
way. The promlem is that node.js is not too friendly with proxies.

Bogdan

On Mon., Apr. 6, 2020, 8:33 p.m. indirection, [e-mail]
wrote:

Thank you for Joplin!

I've tried every work around that I could find.

Completed: 2020-04-06 8:27 PM
Last error: FetchError: request to https://public.dm.files.1drv.com//version.txt
failed, reason: unable to get local issuer certificate

This example is behind the Cisco Umbrella proxy.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/laurent22/joplin/issues/164#issuecomment-610107194,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABMRXVSACWZSHKTRXCQGM3RLJYGXANCNFSM4ELZVYSA
.

[stale[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[bhlevca]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

As far as I know no work has been done on this. I think that it needs a fix not a closure.

[wangyongcong]

I have the same problem on MacOS. Joplin seems not respect system proxy setting when sync to Dropbox or checking update. This problem make Joplin hard to use in some country.

[zicklag]

If you use Nextcloud for the note sync, an easy solution that bypasses the proxy problem is to install the Nextcloud Desktop client and synchronize a Nextcloud folder to your local drive, then use the Joplin local filesystem synchronization mode.

[stale[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[gibboni]

This needs a proper fix.
Lack of proxy support prevented me using Joplin so I had to move on and use other editors for note taking. But I hope this is some day fixed so I could use it again.

[stale[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[bhlevca]

Still hoping for a fix ...

[g4c]

Actually it's even worse. I installed the new version (portable) yesterday and the nasty workaround with sockscap64 stopped working. Joplin just hangs and that's it. I cannot move to the previous version as the db has been migrated to the new format 😭
When I disconnect vpn works ok.
Guys, please upvote or advise how to raise priority of this issue...

[nokoa77]

@g4c argh I wanted to try also sockscap on Monday at work !
This feature is really missing, it make me very difficult to sync when I’m at work; I have to switch network several times a day to make it work and to always have an alternative WiFi network working in parallel of my enterprise WiFi network !! It’s really annoying.
And the « local sync + nextcloud folder » alternative doesn’t work : the sync is partial, it’s explained somewhere else in the forum ; local sync is not compatible with multi device sync.
I hope this feature can be implement even in alpha state if it can work on some situations

[nokoa77]

@gibboni as the OP, could you please rename the issue « sync fails when behind a proxy » ? As it is true for at least Nextcloud also ? Thanks

[g4c]

@nokoa77 Thanks for saving me stress with local sync I was planning to test. Now I know it's poinless 🙁

[g4c]

@gibboni yes, @nokoa77 is right, I use nextloud. Also add windows 10 please. Maybe this will make this thread more visible for @laurent22. It's over 2.5 years old 😭

[zicklag]

I use nextloud.

@g4c I am behind a proxy and I use Nextcloud's desktop client to synchronize the files to the local filesystem and then tell Joplin to use the Nextcloud-synced dir. It works really well, and Nextcloud sync supports the proxy. Definitely agree that this is in the workaround category and it only works with nextcloud which is unfortunate.

[nokoa77]

Hi @zicklag thank your testimonial, and sorry @g4c if I misinformed you by ignorance. In fact I tried for several weeks to sync using "local sync + nextcloud folder", and I counldn't make it work. I remember I saw in the joplin forum that it was a known bug, but apparently I was mistaken, maybe my conf was bad. I will try again. If @g4c you are more successfull than me, I'm interested !!

[g4c]

@nokoa77 no problem. I will let you know if any progress. But, honestly, I'm a bit tired by this waiting for any feedback with some kind of info and preferably deadline. I appreciate all the work invested in this app, really. But maybe it's time to search for some other solution. I've never faced any app having this kind of network problem. Keeping nextcloud folder synced locally opens new opportunities for using other apps.

[stale[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[zicklag]

Thank you kind @stale bot, but we'd rather keep replying to this issue than let it get closed. :wink:

Edit: Oops, apparently the bot isn't actually an account you can @ mention. Sorry whoever I pinged!

[nokoa77]

Hi, I confirm this feature is still an open issue for Joplin to work properly on all configurations, including when one is using it "at work" in a corporate company where proxy is the standard. There seems to be workarounds (like 1/ sync on file and 2/ sync this file with nextcloud or dropbox...) but it is not very efficient : I tried for several weeks and had to stop because of too many sync errors and fails.

[onatbas]

Hey guys, I appreciate the efforts put into Joplin, I truly do! But at the same time I can't believe how proxy support can be dismissed for so long. I believe you're underestimating the amount of people who direly needs proxy support. This is a major hurdle for some (including me.)

[laurent22]

It's not a ignored, I've spent quite a bit of time tried to get it working but failed. I'd gladly accept a pull request for it but it would have to be rock solid or supported by a company or very motivated contributor, because I won't be able to fix any issue with it (setting up a proxy is too much hassle and when things don't work it's very hard to debug).

[g4c]

@laurent22 Thanks for the answer and all your work! I believed it should be more about getting new customers or companies. From my perspective this is basic functionally for every bigger company and there is also some competition on the market. Just don't understand why a company should insist on adding proxy? They just evaluate what's on the market and how it suits their needs. If they consider Joplin among others and find out it cannot work in their environment/infrastructure they just give up and choose something different instead. This is how it works based on my experience. But, of course, this is your business and your decision.

[gibboni]

@laurent22, have you tested global-agent? It works transparently to tunnel modules that use node's default http.request() method as well as the request module. It was made to replace the older global-tunnel library.