Open gitaaron opened 2 years ago
I created two instances of Box on two ubuntu VMs using ansible playbooks (ipfs + ipfs-cluster + box). After doing the steps above, everything works and I can see the changes I make in the file reflected in the browser. However, after a while it seems that fula-client gets disconnected. The cloud icon changes to a loading animation and it can't reconnect to the box again. Even when I refresh the browser it can't connect. I restarted Box service (the one fuludocs was trying to connect to) and the browser gets connected again. @gitaaron is it possible that the issue is about fula-client getting disconnected and unable to connect again? Are you sure that fula-client was connected when you saw that changes aren't getting reflected in the browser?
Hi Mehdi,
I tried refreshing the browser and reconnecting and that did not work. It was reloading the previous CID.
If you want you can reassign this to me and I can come up with a more reliable way of reproducing it.
Thanks, Aaron
On Sat., May 28, 2022, 5:54 p.m. mehdibalouchi, @.***> wrote:
I created two instances of Box on two ubuntu VMs using ansible playbooks (ipfs + ipfs-cluster + box). After doing the steps above, everything works and I can see the changes I make in the file reflected in the browser. However, after a while it seems that fula-client gets disconnected. The cloud icon changes to a loading animation and it can't reconnect to the box again. Even when I refresh the browser it can't connect. I restarted Box service (the one fuludocs was trying to connect to) and the browser gets connected again. @gitaaron https://github.com/gitaaron is it possible that the issue is about fula-client getting disconnected and unable to connect again? Are you sure that fula-client was connected when you saw that changes aren't getting reflected in the browser?
— Reply to this email directly, view it on GitHub https://github.com/functionland/fula/issues/189#issuecomment-1140334330, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAFDZZFZUEM5ZSQPROZ6Q3VMKIZ3ANCNFSM5WPVXZIQ . You are receiving this because you were mentioned.Message ID: @.***>
This may be hard to reproduce but creating this issue now -
Steps to reproduce