You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 27, 2022. It is now read-only.
I am having issues connecting to any dat:// data sets using the latest and any previous Beaker versions. I am running two homebase version 2 instances, one on a VPS and another on my cable internet studio network and they are happily exchanging and syncing data. However, no beaker version, neither from the 0.8 or the current 1.0beta releases, as well as the latest release of the dat desktop client, finds the data sets, no difference if I'm in the same network as the local homebase or not. Is there any way to "force add" a peer IP address to a dat swarm, or other ways to debug what's going on on either end?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am having issues connecting to any dat:// data sets using the latest and any previous Beaker versions. I am running two homebase version 2 instances, one on a VPS and another on my cable internet studio network and they are happily exchanging and syncing data. However, no beaker version, neither from the 0.8 or the current 1.0beta releases, as well as the latest release of the dat desktop client, finds the data sets, no difference if I'm in the same network as the local homebase or not. Is there any way to "force add" a peer IP address to a dat swarm, or other ways to debug what's going on on either end?
Beta Was this translation helpful? Give feedback.
All reactions