Local DNS issues with FarmbotOS

Hi there! I recently (day before yesterday) finished my build and am too having DNS resolution failures and token refresh failures.

I’ve tried on WiFi and Ethernet (after reading this forum and similar problems) - what logs would you want from me to further help diagnose? It’s currrntly pretty unusable and constantly dropping off - can’t even get it to stay online long enough to set the tool positions.

FWIW it’s about 5 meters from an outdoor access point, with clean airtime.

I run my own local DNS and don’t actually see it hitting any queries when it says it fails. I also don’t see it dropping the WiFi link, it seems clear. There are another 30-50 little ESP8266s that are on the same VLAN and have no trouble, so I’m pretty confident in the network.

Happy to help, please let me know! Cheers,

I’ve split this topic since i think this might actually be a bug in the low level networking layer. First though, i need a bit of information.

  • What version of FarmBot OS are you using?
  • Are you using FarmBot’s servers, or a local instance?
  • What error logs do you see in the ticker/logs panel?

Right now you should be able to manually set the dns server in configurator’s advanced settings, though depending on a few other things, this may not solve your issue.

Thanks!

Farmbot version is 6.4.11, I’m using farmbot cloud (debating local!), and all I see when this happens is “Cannot resolve my.farm.bot” over and over.

Hey @connor that´s not for real?!? I am reporting these connectivity issues since month which basically make the farmbot unusable and now as a second person has the same errors you begin looking into this topic? You guys really need to work on your support strategy! Even one bot which is not working is too much!

As you know from all the other threads I am running on 6.4.11 on the online version. My error logs I posted in many threads but happy to repost:
Error Trying to resolve https://my.farm.bot 9 more times. 0.6, 0.8, 0.5 Oct 5, 7:07am

Btw why are you not using the new diagnose function?

Guys I am really once more disappointed from your (not) support, you need to change that immediately!

Here’s a most recent log, I’m going to try downgrading to 6.4.9 per other thread to see if that helps… (it can’t even finish a single watering at this point)

|Error|Trying to resolve https://my.farm.bot 8 more times.|530, 100, -500|Oct 6, 1:23pm|
| --- | --- | --- | --- |
|1

Success|Farmbot is up and running!|-1, -1, -1|Oct 6, 1:23pm|
|1

Error|Trying to resolve https://my.farm.bot 9 more times.|530, 100, -500|Oct 6, 1:22pm|
|1

Info|Forcing a token refresh.|530, 100, -500|Oct 6, 1:22pm|
|1

Success|Movement to (530.0, 100.0, -500.0) complete.|-1, -1, -1|Oct 6, 1:22pm|
|1

Busy|Moving to (530.0, 100.0, -500.0)|-1, -1, -1|Oct 6, 1:22pm|
|1

Info|[MLH] Moving absolute: {'y': 100, 'x': 530, 'z': -500}|530, 100, -500|Oct 6, 1:22pm|
|1

Success|Movement to (530.0, 100.0, -500.0) complete.|530, 100, -500|Oct 6, 1:22pm|
|1

Success|Farmbot is up and running!|-1, -1, -1|Oct 6, 1:22pm|
|1

Info|Forcing a token refresh.|110, 100, -294.6|Oct 6, 1:21pm|
|1

Busy|Moving to (110.0, 100.0, 0.0)|2585, 0.2, -328|Oct 6, 1:20pm|
|2

Success|[Get Water Nozzle] - Sequence complete.|2585, 0.2, -328|Oct 6, 1:20pm|
|1

Success|Movement to (2585.0, 0.2, -328.0) complete.|2585, 0.2, -328|Oct 6, 1:20pm|
|1

Success|Wireless network reconnected.|2585, 0.2, -405.28|Oct 6, 1:20pm|
|1

Busy|Moving to (2585.0, 0.2, -328.0)|2585, 0.2, -428|Oct 6, 1:20pm|
|2

Info|[Get Water Nozzle] - Sequence Executing: MoveRelative|2585, 0.2, -428|Oct 6, 1:20pm|
|1

Success|Movement to (2585.0, 0.2, -428.0) complete.|2585, 0.2, -428|Oct 6, 1:20pm|
|1

Busy|Moving to (2585.0, 0.2, -428.0)|2735, 0.2, -428|Oct 6, 1:20pm|
|2

Info|[Get Water Nozzle] - Sequence Executing: MoveRelative|2735, 0.2, -428|Oct 6, 1:20pm|
|1

Success|Movement to (2735.0, 0.2, -428.0) complete.|2735, 0.2, -428|Oct 6, 1:20pm|
|1

Busy|Moving to (2735.0, 0.2, -428.0)|2735, 0.2, -398|Oct 6, 1:20pm|
|2

Info|[Get Water Nozzle] - Sequence Executing: MoveRelative|2735, 0.2, -398|Oct 6, 1:20pm|
|1

Success|Movement to (2735.0, 0.0, -398.0) complete.|2735, 0, -398|Oct 6, 1:20pm|
|1

Error|Token failed to reauthorize: jwood@me.com - https://my.farm.bot :enetunreach|1925.8, 0, -384.72|Oct 6, 1:20pm|
|1

Error|Authorization failed: {:error, :enetunreach}|1925.8, 0, -384.72|Oct 6, 1:20pm|

Struggling to downgrade, it keeps auto upgrading, despite me having turned that off already…

My farmbot randomly reports DNS issues, but similar to the initial post of this topic the WLAN connection is good and should not be the problem.

Besides the router, which does provide a DNS caching server, I also have monitored domain servers which run 24/7 and provide DNS (both as source for the router, but also public authoritative for a few dozen domains). These are known to be reliable.

So I tried to factory reset and manually set the DNS servers for the FarmBot. It does come up and running, but fails in subtle ways; for instance it is no longer possible to install farmwares other then the built-in ones (stays stuck on the “Installing farmware from https://raw.githubusercontent.com/.../manifest.json” log step, no preflight checks or success message.

I tried this several times, always the same behavior. Even when I manually set the router as DNS server (e.g. identical to the one received via DHCP). As soon as I switched back to DHCP and left the advanced options empty, installing the farmware works again. So there’s definitively something fishy going on with the DNS part of FB (OS version is 7.0.1).

This may be related to the fails I have been seeing.

However, our FB seems to never regain the network connection (almost every time).
I am suspecting this may be a multi-fold set of issues.

  1. Whatever the DNS/7.0.1 thing is
  2. Heat/FBOS corruption
  3. Network Config/FW rule issues. (We have port 3002 (WebSockets) enabled, but have never seen traffic on it. Not sure if that is expected…

Our current strategy is to nurse the Bot along until FBOS V8 is released.

Here is a snippet form the most recent logs - The FB did not remain off-line on this occasion.

—Begin Log Snippet—

2

Success Synced 0, -0.2, 0 Jun 13, 5:59pm
2

Busy Syncing 0, -0.2, 0 Jun 13, 5:58pm
1

Info Forcing a token refresh. 0, -0.2, 0 Jun 13, 5:58pm
2

Success Synced 0, -0.2, 0 Jun 13, 5:58pm
2

Busy Syncing 0, -0.2, 0 Jun 13, 5:58pm
1

Success DNS resolution successful 0, -0.2, 0 Jun 13, 5:58pm
1

Error Authorization failed: {:error, :connect_timeout}. Trying again 2 more times. 0, -0.2, 0 Jun 13, 5:58pm
1

Error Authorization failed: {:error, :nxdomain}. Trying again 3 more times. 0, -0.2, 0 Jun 13, 5:57pm
3

Success Interface eth0 is up. 0, -0.2, 0 Jun 13, 5:57pm
3

Busy Waiting for interface eth0 up. 0, -0.2, 0 Jun 13, 5:57pm
3

Warn Farmbot was disconnected from the internet: :nxdomain 0, -0.2, 0 Jun 13, 5:57pm
1

Error Trying to resolve https://my.farm.bot 9 more times. 0, -0.2, 0 Jun 13, 5:57pm
1

Error Authorization failed: {:error, :closed}. Trying again 4 more times. 0, -0.2, 0 Jun 13, 5:57pm
1

Success Farmbot is up and running! 0, -0.2, 0 Jun 13, 5:57pm
3

Warn Farmbot was disconnected from the internet: :nxdomain 0, -0.2, 0 Jun 13, 5:57pm
1

Info Forcing a token refresh. 0, -0.2, 0 Jun 13, 5:57pm
2

Success Synced 0, -0.2, 0 Jun 13, 5:55pm
2

Busy Syncing 0, -0.2, 0 Jun 13, 5:55pm
2

Success Synced 0, -0.2, 0 Jun 13, 5:25pm
2

Busy Syncing 0, -0.2, 0 Jun 13, 5:25pm
2

Busy Syncing 0, -0.2, 0 Jun 13, 4:55pm
2

Success Synced 0, -0.2, 0 Jun 13, 4:25pm

—End Log Snippet—