08 · When something fails: stumbles along the way

A root meets a stone. It goes around and carries on.

The most common stumbles, from the simplest to the most hidden. The commands are to be typed on the mucua (on its keyboard, or remotely over SSH, with the mucua user).

"The site doesn't open"

1. Is the phone on the same network as the mucua? The gathering's Wi-Fi, not the one next door.
2. Is mobile data on? Turn it off for a moment and try again.
3. Try the number. The IP shows on the mucua's screen (chapter 02) — http://10.42.0.1, for example. If the number opens and the name doesn't, the mucua is fine: the problem is only the name (next item).

"The number opens, but baobaxia.local doesn't"

.local is announced by the mucua on the network, and whoever asks needs to know how to listen:

• iPhone, Mac and Windows usually understand it.
• Many Androids don't understand .local in the browser. Use the padlock address (local.baobaxia.net) or the number.
• On Linux, the libnss-mdns package is sometimes missing.
• Some routers (guest networks, school or company Wi-Fi) block that announcement between devices.
• If there are two mucuas on the network, the second one becomes baobaxia-2.local.

"local.baobaxia.net doesn't open"

• On the network the mucua creates, it always works — if it doesn't open, the phone is using another path (mobile data, Android's "private DNS": turn it off in Settings → Network → Private DNS).
• On someone else's network (the school's router), it only works if the router points the name to the mucua (chapter 05). Use baobaxia.local or the number.
• If the browser complains about the certificate, check the mucua's clock: with the wrong date, the certificate looks expired.

"I changed baobaxia-rede.txt and nothing changed"

The file is read at boot. To apply it right away, from inside the mucua:

sudo nano /boot/efi/baobaxia-rede.txt     # on the Raspberry: /boot/firmware/
sudo baobaxia-rede
sudo baobaxia-rede status

"The chat doesn't accept the password"

1. The address is username@domain — with the same domain shown on the arrival page, not another mucua's.
2. The password is the site's. Try logging into the site with it.
3. Whoever looks after the mucua checks which domain the chat uses:

   sudo baobaxia-xmpp status
   sudo baobaxia-certificado dominio

If the certificate has several names (local.baobaxia.net and arquivos.local.baobaxia.net), the main one must be the shortest. To change it (the chat is restarted along with it):

   sudo baobaxia-certificado dominio local.baobaxia.net

"The first boot didn't finish"

The first boot tells what it did in a file:

sudo tail -n 40 /var/log/baobaxia-primeiro-boot.log

• "needs internet" / pip error: the image was made without the Python pieces built in (the --vendor-wheels of whoever makes the image). Plug the mucua into a cable with internet and restart: the first boot tries again by itself.
• "MUCUA_UUID is not a UUID": fix the line in baobaxia-rede.txt (chapter 04), or delete it for a new mucua.

Until it ends well, the first boot tries again on every boot.

"A strange character showed up on screen"

The boot screen doesn't show accents properly — that's why the menu and the messages are written without them. If a message from another program has an accent, a ? or a little square may appear instead. It's not a fault: on the site, everything shows correctly.

To look closely

sudo baobaxia-rede status          # the network: mode, connections, IPs
sudo baobaxia-chegar status        # the arrival page: apps, HTTPS, chat
sudo baobaxia-xmpp status          # the chat
sudo baobaxia-certificado status   # the certificate and how many days are left
journalctl -u baobaxia-api -n 50   # what the site has been saying

If none of this solves it, the Rede Mocambos community helps: bring the error message and what you have already tried.