Connection Warning: Unable to Reach Required Services

The Robotical app may show a warning that a service could not be reached, or that a request timed out. This can happen when a school or office firewall blocks a connection, or when Wi-Fi, internet or VPN connectivity is interrupted.

How to fix it

  1. Check that you can open another website using the same device and network.
  2. Ask your network administrator to allow the domain families below for the features you use.
  3. Reload the app after the network rules have been updated. On a phone or tablet, close and reopen the app.
  4. If the problem continues, contact hello@robotical.io and include the warning message and the feature you were using.

How to apply the domain rules

Include subdomains when allowing each domain below. For example, allowing robotical.io and its subdomains covers Robotical's API, content, firmware updates, user guides and warranty dashboard. You do not need a separate rule for each Robotical service or individual page, file or URL path.

Some firewalls require both the parent domain and a wildcard rule, such as robotical.io and *.robotical.io. Ask your network administrator to use the equivalent setting for your firewall.

Allow outgoing HTTPS on TCP port 443. The warranty dashboard also uses secure WebSocket connections to Firebase; these must be allowed through the firewall or proxy.

Domains by feature

These are the domains used by the current app and its online features. Allow the rows relevant to your setup; the same domain family may support more than one feature.

Feature Domains to allow, including subdomains
Robotical app and services: app access, speech and translation services, tutorial content, firmware updates and the warranty dashboard robotical.app, robotical.io
Tutorial media, curriculum project files and phone app content downloads amazonaws.com, sanity.io
Sharing and opening cloud projects in Blocks and Blocks Jr; firmware-version checks firebaseio.com, firebasedatabase.app
Scratch costumes, sounds, asset previews, Scratch project loading and the normal Marty narration voice scratch.mit.edu
Machine learning: model downloads and the ML5 library googleapis.com, stretch3.github.io
Warranty registration and dashboard: authentication, account data and registration/login emails robotical.io, googleapis.com, firebaseio.com, amazonaws.com

The googleapis.com rule covers both machine-learning model storage and Firebase authentication services. Current Blocks translation uses Robotical's services, covered by robotical.io.

Optional features and diagnostics

These services are used only for the features described below. They are separate from the main app requirements.

Optional feature Domains to allow, including subdomains
Creating or loading Teachable Machine models teachablemachine.withgoogle.com; model files also use googleapis.com from the main list
Face Sensing fallback, if the bundled MediaPipe files cannot load jsdelivr.net
Tutorial videos that use the Wistia player wistia.com
Sending app feedback and bug reports slack.com, firebaseio.com, firebasedatabase.app
Error reporting, when enabled sentry.io

Colour-sensor diagnostics and profiles, serial-number lookup, native app configuration, diagnostic logging and the News Hub also use the Robotical and Firebase domain families already listed above. They do not require separate rules for each database or Robotical subdomain.

Legacy and compatibility domains

Keep these separate from the current app address. They are needed only when an older or compatibility flow uses them.

Domain to allow, including subdomains When it is used
codemarty.com Older app addresses and a legacy native-wrapper fallback. The current app address is robotical.app.
marty-webapp.web.app Older Robotical hosting. The current registration form still links here for Warranty Terms, and the updater also references this host.

Legacy support ticket and conversation integrations also use amazonaws.com, which is already included above.

Connecting to Marty over local Wi-Fi

The internet domain rules above are separate from the local connection to Marty. If you connect over Wi-Fi, your device must also be able to reach Marty's local IP address using WebSockets. Ask your network administrator to check local device access or client-isolation settings if internet access works but Marty cannot be reached.

See Connecting Marty to Wi-Fi for the connection steps.

Task Runner