@@ -92,10 +92,6 @@ Since version `0.8.0`, changes no longer automatically sync between the Unix sid
93## Connectivity Issues {#connectivity-issues}
93## Connectivity Issues {#connectivity-issues}
95−### I can `|hi` my sponsor star, but I cannot get syncs from it or discover peers
97−This means you have one-way connectivity with your star, with your star being unable to send your messages; many connectivity problems are derived from this. Run `|nuke ~star`, where `~star` is your sponsor star in the Dojo. Then run `|nuke ~star` again. This can solve various communication problems. You can find your sponsor by running `(sein:title our now our)`.
99### I can't communicate with anyone
95### I can't communicate with anyone
101You may have booted a ship with your keyfile twice in the same era. To fix this, you must perform a [personal breach](#personal-breach).
97You may have booted a ship with your keyfile twice in the same era. To fix this, you must perform a [personal breach](#personal-breach).
@@ -132,24 +128,6 @@ The above commands work if you have the wrong keys of other ships. If other ship
133This is the result of deleting your pier and starting your ship again. To fix this, you must perform a [personal breach](#personal-breach).
129This is the result of deleting your pier and starting your ship again. To fix this, you must perform a [personal breach](#personal-breach).
135−### I have two ships, and only one can connect with the other
137−One-way connectivity (OWC) means that ship `~A` can't `|hi` ship `~B`, but ship `~B` can `|hi` ship `~A`. If you have two ships that are suffering from this problem, it can be solved by a series of steps.
139−1. Turn both ships off and on again. This sometimes solves this problem.
141−2. On ship `~B` -- the ship that can connect to the other -- `|nuke ~A`, where `~A` is the ship that cannot `|hi` the other. Wait several minutes. Do you see any messages in your console? If not, try sending a `|hi ~A` from `~B`. If “blocked” or similar messages start appearing, `|nuke ~A` again to unblock, and check if connectivity has been restored.
143−3. If you can’t get any packets to be sent to `~B`, you’re going to have to temporarily modify your ship’s Ames to trick it into sending packets. Make sure to do this on its home desk so as to not impact any syncs. Open `~A/home/sys/vanes/ames.hoon` and find `++ harv`. Just above `(gth caw nif) check`, insert the a line of this code: `=? caw =(caw nif) +(caw)`. Save the file and run `|commit %home`.
145−4. Try running `|hi ~B`. Wait a bit. Are you seeing `%blocked` or `%bad-ack` messages yet? If not, send another `|hi ~B`.
147−5. Once the messages start rolling in, revert the Ames change that you made on `~A` in step 3. Then `|nuke ~A` again from `~B`. Wait a little bit, then check if this resolved the OWC.
149−6. If the OWC is still not resolved, try step 6.
151−7. Be patient. After following these steps, your |hi may still not go through instantly even though OWC has silently been fixed: there could be something like a very large sync queued up.
153## Booting Issues {#booting-issues}
131## Booting Issues {#booting-issues}
155### My ship won't boot and gets a `terminals database is inaccessible` message
133### My ship won't boot and gets a `terminals database is inaccessible` message