It should connect in seconds. There are a few things you should check.
Start with checking the port. On https://www.yougetsignal.com/tools/open-ports/?port=28967 you can fill in the domain or IP you are using in the run command. Then check the port.
If it’s closed, it could still be several things.
- Make sure the WAN IP you see in your router settings matches the IP shown on the above page.
- Make sure your port forward is set up correctly. That means no filter on incoming IPs, forwarding to the IP of your node on the local lan. Set to TCP and port 28967.
- If you’re running a firewall, make sure you allow incoming traffic on port 28967.
- Make sure you’re not blocking any outgoing traffic from your node’s IP to any port. Make an explicit rule to allow that if needed.
You can keep using the page linked above to verify. It will only show the port as open if your node is running.
If the port does show up as open, it’s likely because your identity isn’t signed (correctly).
Check this:
docker exec -it storagenode ls -l /app/identity
You should have 6 files in there. ca.cert should be 10xx bytes and identity.cert should be 15xx bytes. If you are missing files or these two files are smaller, your identity isn’t signed correctly. Please follow the instructions on how to sign again. If your token was already used, try to find the folder with the 6 files of the right size. Your token is one use only, so don’t lose your signed identity files.