Has anyone succesfully deployed selfhosted anytype with Cloudflare tunnels? #241
Replies: 4 comments 3 replies
-
|
I couldn’t get this working with a Cloudflare tunnel, but using my server’s Tailscale IP did the trick. Not the perfect setup, but it works for now. |
Beta Was this translation helpful? Give feedback.
-
|
I am also working with Tailscale for now, but with CF tunnels, I would recommend creating tunnels for all essential ports, but cloudflared only allows forwarding a TCP port for now, not sure of UDP and QUIC ports. |
Beta Was this translation helpful? Give feedback.
-
RemarkI use this method successfully login to the anytype server through Cloudflare tunnel with my roaming mobile device. I don't know if there's any security issue. HoweverFailed to login to the same vault with another device (linux laptop), encountered this error messageThen I make a new vault, and try to invite my phone to my laptop using QR and Link.
Then I try to invite my laptop to my phone instead
I don't know if the my workaround caused these issue, or if I have anything setup wrong in my docker setting, or is there the issue of the application. Methodin cloudflare tunnel setting:
modified the id: XXX
networkId: XXX
nodes:
- addresses:
- any-sync-node-1:1001
- quic://any-sync-node-1:1011
- 192.168.0.300:1001
- quic://192.168.0.300:1011
- 127.0.0.1:1001
- quic://127.0.0.1:1011
# ++++++++++++++++++++++++++++++++++++
- any-sync-node-1.my.domain
# ++++++++++++++++++++++++++++++++++++
peerId: XXX
types:
- tree
- addresses:
- any-sync-node-2:1002
- quic://any-sync-node-2:1012
- 192.168.0.300:1002
- quic://192.168.0.300:1012
- 127.0.0.1:1002
- quic://127.0.0.1:1012
# ++++++++++++++++++++++++++++++++++++
- any-sync-node-2.my.domain
# ++++++++++++++++++++++++++++++++++++
peerId: XXX
types:
- tree
- addresses:
- any-sync-node-3:1003
- quic://any-sync-node-3:1013
- 192.168.0.300:1003
- quic://192.168.0.300:1013
- 127.0.0.1:1003
- quic://127.0.0.1:1013
- any-sync-node-3.my.domain
peerId: XXX
types:
- tree
- addresses:
- any-sync-coordinator:1004
- quic://any-sync-coordinator:1014
- 192.168.0.300:1004
- quic://192.168.0.300:1014
- 127.0.0.1:1004
- quic://127.0.0.1:1014
# ++++++++++++++++++++++++++++++++++++
- any-sync-coordinator.my.domain
# ++++++++++++++++++++++++++++++++++++
peerId: XXX
types:
- coordinator
- addresses:
- any-sync-filenode:1005
- quic://any-sync-filenode:1015
- 192.168.0.300:1005
- quic://192.168.0.300:1015
- 127.0.0.1:1005
- quic://127.0.0.1:1015
# ++++++++++++++++++++++++++++++++++++
- any-sync-filenode.my.domain
# ++++++++++++++++++++++++++++++++++++
peerId: XXX
types:
- file
- addresses:
- any-sync-consensusnode:1006
- quic://any-sync-consensusnode:1016
- 192.168.0.300:1006
- quic://192.168.0.300:1016
- 127.0.0.1:1006
- quic://127.0.0.1:1016
# ++++++++++++++++++++++++++++++++++++
- any-sync-consensusnode.my.domain
# ++++++++++++++++++++++++++++++++++++
peerId: XXX
types:
- consensus |
Beta Was this translation helpful? Give feedback.
-
|
Almost... but it's terrible. I got p2p working, but it can't directly connect to the server. First generate everyting with make start Edit all the configs with your 443 url from cloudflare. Also edit your client.yml And then it can work a little... |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Has anyone succesfully deployed selfhosted anytype with Cloudflare tunnels? If yes how have you done? Cannot find an udp option in cloudflare tunnels and it seems like any-sync use UDP and QUIC.
Seems like there might be a way to use udp with cloudflare tunnel but its kind of confusing and isn't as straightforward as other protocols.
I do not want to open ports on my firewall. I use anysync-dockercompose.
Beta Was this translation helpful? Give feedback.
All reactions