search

kercre123 / wire-pod

Free, fully-featured server software for the Anki Vector robot.
MIT License
446 stars 151 forks source link

[HELP] escapepod.local works, but vector does not activate #285

Open Sloth-on-meth opened 8 months ago

Sloth-on-meth commented 8 months ago

Describe the issue:

What are you running wire-pod on?

Are you setting up a prod (regular) bot or a dev/OSKR (unlocked) bot? Prod

What steps have you tried? When i tryi to activate, i get

"Error logging in,. the bot is likely unable to communicate with your wirepod [....]'

i setup my local dns server so escapepod.local points to 192,168,178,79 , which is where my server is running, and it does work when trying in the browser

Sloth-on-meth commented 8 months ago

'dwonload logs' gives me a .txt with giberrish in it sadly

kercre123 commented 8 months ago

Could you send the downloaded log here (even if it is gibberish)?

Sloth-on-meth commented 8 months ago

https://github.com/kercre123/wire-pod/files/14164925/vector-logs-2024-02-05-12-29-52.tar.bz2.txt

Rodziac commented 7 months ago

Hello! I'ts been 3 weeks, so you maybe fixed it or gave up already, but:

  1. It seems you are saving your log file wrong. It's actually a tar.bz2 file, but since you have it saved as tar.bz2.txt it gets opened like a text file. This is actually an archive file. You need to: i. Rename the file to remove .txt at the end ii. Extract the archive
  2. Now that you can open the log archive, you can look inside. i. If you open data/diagnostics/logs/log.txt in your text editor, you can see the actual logs! ii. If you read around the end, you'll see it says: "transport: Error while dialing dial tcp: lookup escapepod.local: no such host"

It seems like your vector is not able to reach the escapepod.local domain. Your Vector maybe is not using your local DNS server. I wonder if your router is set up to use/advertise your local DNS server.

There are log files that show vector ping anki.com. I wonder if you could update your local DNS server to point anki.com to some other IP, restart the vector, check the logs, and see which IP address it pings. If it pings the IP address you set, it means vector is indeed using your local DNS. If not, it means your vector is not using your local DNS so you'll have to look into that.

There -could- be other reasons why it works on your browser but not on vector, but this is the simplest way you can start troubleshooting...

kercre123 commented 7 months ago

wire-pod is a hobby project, not something I can devote all of my time to, so I can't respond to all issues in a timely manner.

Have you tried the troubleshooting steps in the wiki? Maybe try unsetting the rule in your DNS server - wire-pod does mDNS broadcasts which should work if your network allows multicast.

kroteau commented 4 months ago

I've had quite a time debugging an issue just like this. Your router might block mDNS packets(for example mikrotik does this, guest network on a router also block any interaction between connected hosts). Just try a different router! upd (especially for MikroTik routers): go to your wireless interface and set multicast helper to "full", this resolved the issue of escapepod.local address not resolving on my vector. Also works with virtual interfaces as well, only the interface vector and wirepod are connected to needs to be configured this way.

kenny-nt commented 4 months ago

Just wonder why wire-pod don't let us change to a custom host? If escapepod.local can not be resolved in activation, just show a input for entering the wire-pod custom host...