Yeah not for priority support, just to help out. For instance in the beginning of protonmail you could donate, or pay up to an early adopter tier. While I was not expecting anything, later down the road they began increasing space available to those people. Anyway, just a thought.
1 Like
@laurent Along with financial contributions, is there a way to support by contributing dev work? It looks like the project is open source.
Is there a standardized format for contributing / knowing what needs to be worked on? I'd love to get involved and help out, if I can.
1 Like
Thank you! This is exactly what I was looking for 
A new release is on the way with a fix for the "too many login error", sorry about the trouble.
Regarding support: you can post here or you can email the Joplin Cloud support address (which appears in various place). Regardless of scale, I want to hear about this kind of issue as it can affect other users too.
Regarding that particular issue, it was due to a brute force prevention routine, which is going to be fixed in the coming release.
1 Like
I'm also having issues while syncing with Joplin Cloud:
Completed: 15/09/2021 10:04 (265s)
Last error: Error: Unknown error: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.18.0 (Ubuntu)</center> </body> </html>
1 Like
I am getting the same error. Since past hour or so.
Seems to be a server issue - too many login attempts for me - so nothing can sync for some reason.
Normality restored.
Edit: too soon. The problem persists. I'm considering going back to OneDrive and cancel my Joplin Cloud subscription.
A new release is on the way with a fix for this issue. More info there: Cannot Login to Joplin Cloud - #26 by laurent
1 Like
Just as a reminder, OneDrive sync was down for several days last year due to one of their broken updates. So just because it's Microsoft or Google doesn't mean you'll have more reliability, nor that you'll have better support. Just like them, I want to create a service that's as reliable as possible in any case.
It's all a matter of scale - I couldn't handle on my own the millions of users that Google has, but I can handle the few hundreds on Joplin Cloud. If it turns out the service is a success, I can also hire a person to quickly respond to incidents.
Ok the new update is live now, and the "too many login error" should be solved.
1 Like
OneDrive sucks. They have a serious Bug with their delta api since one year... ODP Regression: OneDrive Graph API /delta deltaLink response is malformed · Issue #1408 · OneDrive/onedrive-api-docs · GitHub
Awesome! Thank you for the quick work on this 
There was also an issue with the Postgres database which for some reason had over 30 active queries that had been there for several hours or days in some cases, and it looks like because of this the db server CPU was always at 100%.
I assume that's what was causing the recent "The pool is probably full" error that was reported on the forum.
Anyway after killing all these requests the cpu is back at 5% and it's staying there for now. I don't fully understand what's happening but I've enabled the slow query log and will keep an eye on the server to find out why it does that.
Ah, that makes sense. I was noticing syncs taking awhile, although working, after the new update went live.
Now they're back to normal speeds 
1 Like
That is entirely your prerogative, and I'm actually not addressing you in person. But wow... this service is fresh out of beta, has one tiny hitch which doesn't even affect anything except instant syncing and people are all up in arms.
I mean sure, if Joplin Cloud ate all your notes, made your baby cry or was down for 6 days out of 7 I can see the point in threatening to leave, but honestly I think people should calm down a little and give the system a chance.
Just my 2 cents and again, nothing personal towards the one I quoted... and no hard feelings either way.. Definitely go with the system you trust more 
3 Likes
Don't take me wrong. It was not a threat. But this is not the first time. And we need to be realistic.
Hopefully the problem is now gone for good.
Thank you Laurent for your reactivity 
Looks like the root cause of all the issues these past few days is that a user has reached some limit, maybe in terms of number of items, or number of changes, I'm not sure yet. Whenever he goes online, the whole system slow down. So for now I've put a timeout to automatically kill these queries to prevent them from accumulating, and that seems to work.
However it means sync is not working for one user, who I haven't identified yet. So if you're seeing errors "canceling statement due to statement timeout", please contact me.
In the meantime, I'm going to deploy another release with a better slow query debugging tool that will allow me to find what specific query is causing issue, and to optimise it.
3 Likes