FarmBot requires access to various servers to operate properly.
The first server is the web server (HTTPS). The servers are operated in the United States by Heroku, a Salesforce subsidiary. Heroku subcontracts their infrastructure services to Amazon Web Services (AWS). The servers reside in Amazon’s
us-east-1 region, which is located in Virginia. The server uses the domains
my.farmbot.io. Both domains point to the same server. Services are provided on TCP port 443 (HTTPS and WSS). Heroku does not provide lists of IP ranges, but they should mirror Amazon’s us-east-1 IP ranges. We do not have control over IP allocation, but the most up-to-date list can be found here. Our DNS server is
The second server is the real-time message broker, which runs the RabbitMQ software package. It is also hosted on Amazon Web Services United States region by CloudAMQP, a hosting provider specializing in RabbitMQ message brokers. Like our web servers, the message broker is hosted within Amazon’s
us-east-1 data center. The server’s public domain name is
clever-octopus.rmq.cloudamqp.com. Web browsers require long-running access to this server on TCP port 443. FarmBot devices require long-running access to this domain on TCP port 8883.
New FarmBot OS port requirement (March 2021): FarmBot requires access to TCP port 8883. This port is used for MQTT. You must enable this port prior to upgrading to FBOS versions above 13.0.1. Please update port restrictions as quickly as possible, as upgrades are mandatory for continued device operation on the publicly hosted server at my.farm.bot.
Long-running connections are required
Connections to this server will be kept open for long periods of time via the WebSocket protocol. This is critical to the smooth operation of the device. From the perspective of your security software, it will appear as a long-running HTTPS connection. It is important that your security software does not prematurely close this socket. Disallowing the use of WebSockets or attempting to close sockets after a timeout is a common obstacle to smooth device operation in an enterprise setting.
The FarmBot device also requires outbound access to two redundant NTP servers for setting the system clock:
1.pool.ntp.org. The servers are based in the United States. The services are provided on UDP port 123. Obstructed NTP access is an extremely common source of FarmBot failures in an enterprise setting.
Web content is delivered by the following third parties. All content is transferred over HTTPS (TCP port 443):
farmbot-production.storage.googleapis.com- FarmBot photograph storage.
openfarm.cc- Crop knowledge database
maxcdn.bootstrapcdn.com- Visual stylesheet assets for UI.
fonts.gstatic.com- UI font files.
api.github.com- FarmBot OS software release information.
raw.githubusercontent.com- Hosting of plugin metadata used by the Web App.
The servers in the list above do not require long-running access. They simply open a connection and close it upon completion, which should not take more than a few seconds.
Data in transit is encrypted via SSL and HTTPS (WSS:// in the case of WebSockets). MQTT traffic uses TLS managed by CloudAMQP. The web application implements an HTTP content security policy (CSP) to avoid exfiltration of data by malicious scripts on the end user’s machine. Software updates are run at least once a month. Our source control hosting vendor (Github) provides us with real-time security alerts when vulnerabilities are found in libraries used by the application. Staff is on-call 24 hours a day to apply security patches. The authenticity of the server’s HTTPS certificate is managed by Let’s Encrypt, our certificate authority. Passwords are hashed using Devise, the most common user authentication library for Ruby on Rails applications.
FarmBot does not require a fixed IP address. DHCP is the preferred method of assigning an IP to a device. Due to internal network configuration variation, some organizations may need to assign a static IP to a device, although this is less common.
As of April 2021, FarmBot does not support the use of proxy servers, although we do plan to support the use of proxies in a future version of FarmBot OS. Please see this discussion on Github for more information.
Some users, particularly schools and larger organizations, have reported their devices as being block listed by their security software because the security software categorizes it as a “rogue access point”. Please ensure that your security software does not identify FarmBot’s WiFi configurator as a rogue access point.
FarmBot does not support enterprise WiFi at this time.
If provided an SSH key during configuration (in the “Advanced” panel), it is possible to SSH into a device. There are some caveats, however:
- The SSH session exposes an IEX shell, not bash.
- The Linux distribution that FarmBot uses does not offer any useful utilities for an end user. (IE there is no
- SSH access is used for debugging only. It is not intended to be used for software development or hosting.
Controlling a FarmBot requires only modest hardware and is not particularly demanding for most modern desktop computers. As a general rule, a desktop system capable of word processing and video streaming should be adequately capable of running the FarmBot Web App.
FarmBot is known to work on systems that have:
- The latest 64-bit version of Mac OS, Windows, and Ubuntu
- The latest version of Mozilla Firefox or Google Chrome
- 4GB of memory
- A reasonably performant processor, such as an Intel Core i3.
The FarmBot Web App may run on other systems, though FarmBot, Inc. may not support such systems if performance problems arise.
Please let us know if you have any other security concerns by emailing firstname.lastname@example.org, or opening an issue on GitHub.