note on firewall

developer-guide/25-Calibrations/01-Calibrations.md

@@ -12,9 +12,9 @@ Ideally, all calibrations, including od_calibration and pump_calibration, should
 1. Interface should have the following:
    - `pio run <x>_calibration` starts the calibration and saves it keyed by a unique name (see 2. for storage)
    - `pio run <x>_calibration list` lists all saved calibrations, keyed by their unique name.
-   - `pio run <x>_calibration display ?name?` displays information about the current calibration to be used, or the calibration ?name? if provided
-   - `pio run <x>_calibration change_current <name>` changes the current calibration to `<name>` calibration.
-   - `pio run <x>_calibration publish <name>` publishes the calibration to the leader.
+   - `pio run <x>_calibration display "<name>"` displays information about the current calibration to be used, or the calibration ?name? if provided
+   - `pio run <x>_calibration change_current "<name>"` changes the current calibration to `<name>` calibration.
+   - `pio run <x>_calibration publish "<name>"` publishes the calibration to the leader.
 
 2. On disk, all run calibrations should be stored in local persistent storage under `<x>_calibrations` keyed by a unique name, and the current calibration
 should be stored in `<x>_current_calibration`, with appropriate key (can use `<calibration_type>`) that is not the unique name, but something consistent. Note: The name cannot be `current`.

user-guide/03-Extending your Pioreactor/05-calibrate-od600.md

@@ -64,5 +64,5 @@ To see a full list of all previous calibrations, use `pio run od_calibration lis
 
 ## Changing a calibration
 
-If you wish to change your calibration to a previous version, use `pio run od_calibrations change_current <name>` where `<name>` is some previous calibration you've run (i.e from `pio run od_calibration list`).
+If you wish to change your calibration to a previous version, use `pio run od_calibrations change_current "<name>"` where `<name>` is some previous calibration you've run (i.e from `pio run od_calibration list`).
 

user-guide/50-Troubleshooting/UI troubleshooting.md

@@ -17,9 +17,13 @@ slug: /troubleshooting-ui
  - Try SSHing in and restarting the webserver: `sudo systemctl restart lighttpd.service && sudo systemctl status lighttpd.service`.
 
 
+### No information is shown on the Inventory page / no green dot / no response when I click some buttons.
+
+See [question below](#i-see-failed-to-connect-to-mqtt--in-a-pop-up---what-can-i-do).
+
 ### I see "Failed to connect to MQTT. ..." in a pop-up - what can I do?
 
-This error occurs because your UI can't connect to an internal system, MQTT, that is used for displaying data and actions. Likely you also weren't able to access the UI with `http://pioreactor.local`, but had to use an IP address as the url.
+This error likely occurs because your browser can't connect to an internal system, MQTT, that is used for displaying data and actions. Possibly you also weren't able to access the UI with `http://pioreactor.local`, but had to use an IP address as the url.
 
 To fix this:
 
@@ -36,6 +40,12 @@ Your IP may be different than the one above.
 3. Hit `Save`.
 4. Power-cycle the Pioreactor by rebooting it from the Inventory page.
 
+:::note
+
+Another reason might be that your institution's firewall is blocking port 9001. Ask your IT department about this. The web UI requires port 80 and port 9001 open to use.
+
+:::
+
 #### If you are using a remote access service, like ngrok or tailscale
 
 Likely you didn't fill out the `mqtt` `broker_address` parameter in the configuration correctly. See the [remote access instructions](https://docs.pioreactor.com/user-guide/remote-access) again.