Closed Iuritics closed 6 years ago
thanks for the report - I'm guessing the client needs to enable keepalive, hopefully I can take a look later this week
Thanks a lot, Jeff, very nice of you. I am not a programmer but I am to telling it to my own. I wish it goes well.
Thank you again
Carlos
On Thu, Dec 14, 2017 at 9:57 PM, Jeff Wu notifications@github.com wrote:
thanks for the report - I'm guessing the client needs to enable keepalive
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WuTheFWasThat/vimflowy/issues/279#issuecomment-351833415, or mute the thread https://github.com/notifications/unsubscribe-auth/Ag86rM6Iv5oc5CSU_1gOh_kzIh-QoExZks5tAYuhgaJpZM4RCjBD .
-- Ucelay Abogados www.ucelay.es http://twitter.com/carlosucelay carlosucelay@ucelay.es Fuencarral 131, 1º dcha. 914450307
Possibly just a dup of #279, closing for now
Hi, Thanks for this app. I have installed it with a docker server. Then, when frontend web is inactive for a long while it turns into this message although when I refresh the page, it keeps the same information it already contained before the error and it asks just to refresh:
An unexpected error was caught!
Please help out Vimflowy and report the bug. Report the issue here with:
Error:
Socket connection closed!
g</t.prototype.init/</</this.ws.onclose@http://46.183.117.19/build/app.js:46:118493
Refresh the page to continue