Uploads fail with "timed out"

[t0dd]

Scenario:

1. Using desktop app on linux (Fedora 29) that I built myself

2. Syncing to self-hosted server (also linux on Fedora 29) that uses Nginx as the webserver go-between managing the traffic (instead of connecting directly to the Turl server).

3. Traffic is SSL encrypted via Let's Encrypt

4. ...and I also attempted with direct connection to the IP:8181 via non-ssl'ed http

Problem:

Timeouts on large files.

Error: {"err":{"message":"http://MY_TURTL_SERVER_IP:8181/notes/016959b27932e337979561eef464173cXXXXXXXXXXXXXXXXXXXXXX202a00f4/attachment: timed out","type":"generic"},"file":"src/api.rs","line":150,"wrapped":true} (7471)

I don't know what the size of the file is that times out... but 55M for example does. 8M did not.

Question: I'm (desktop) on a slow (relative) broadband connection. But it is reliable. The server is running in the cloud on blazing fast internet. Is there a timeout setting somewhere that I can tell the Turtl Server to honor?

Related question: I have to view debug logs on the client side to see what's going on over the API. Is there a way to do that serverside?

Related question #2: What does "Frozen" mean in the context of a sync'ed item?

RFE: If I elect to attempt to "Unfreeze" something, there needs to be some kind of UI feedback that I actually did something.

Thanks!

-t0dd

[t0dd]

Note also... trying to send a large file via the Android app (0.7.2.5)... crashes the app when I touch "Save"

[t0dd]

I just moved this discussion the community.turtlapp.com site...

https://community.turtlapp.com/t/larger-uploads-fail-with-timed-out/127

On Thursday, March 7, 2019 at 3:27:56 PM UTC-5, t0dd wrote: