myMCUcertificate setup

Connect this computer

The serial monitor talks to your board straight from the browser, and browsers only allow that on a secure page. This server uses its own certificate, so each computer has to trust it once. It takes about a minute — then the serial monitor works and the padlock stops complaining.

⛨
myMCU-ca.crt certificate authority

This is a public certificate (the private key never leaves the server). Installing it says “I trust certificates issued by this classroom server”.

⬇ Download certificate Right-click → “Save link as…” if the download does not start.

1 · Use the https address

Editing and compiling work over http://…:4173, but the serial monitor needs https://…:4443 with a trusted certificate. Import the certificate first, then use the https address.

2 · Install it on your system

Chrome and Edge on Windows use the Windows certificate store, so installing it there is enough for both.

Option A — one command (recommended)

Open Command Prompt as Administrator (Start → type cmd → right-click → Run as administrator), then paste:

certutil -addstore -f Root "%USERPROFILE%\Downloads\myMCU-ca.crt"

If you saved the file somewhere else, adjust the path. You should see Root "Trusted Root Certification Authorities" and certUtil: -addstore command completed successfully.

Option B — double-click

  1. Double-click myMCU-ca.crt → Install Certificate…
  2. Choose Local Machine (needs admin) → Next
  3. Select Place all certificates in the following store → Browse… → Trusted Root Certification Authorities → OK
  4. Next → Finish → accept the security warning

Check it later: certmgr.msc → Trusted Root Certification Authorities → Certificates.

Safari, Chrome and Edge on macOS use the System keychain.

Option A — Keychain Access

  1. Double-click myMCU-ca.crt — Keychain Access opens and asks for a keychain. Choose System.
  2. Find myMCU in the list → double-click it.
  3. Open Trust → set When using this certificate to Always Trust.
  4. Close the window and type your password (or Touch ID) to save.

Option B — terminal

sudo security add-trusted-cert -d -r trustRoot \
  -k /Library/Keychains/System.keychain ~/Downloads/myMCU-ca.crt

Firefox keeps its own store — see the Firefox tab as well.

There are two stores on Linux: the system store (curl, some browsers) and each browser's own. Install in both if you are unsure.

System store (Debian / Ubuntu)

sudo cp ~/Downloads/myMCU-ca.crt /usr/local/share/ca-certificates/myMCU-ca.crt
sudo update-ca-certificates

Fedora / RHEL / Arch: sudo cp myMCU-ca.crt /etc/pki/ca-trust/source/anchors/ && sudo update-ca-trust

Chrome / Chromium (NSS store)

certutil -d sql:$HOME/.pki/nssdb -A -t "C,," -n "myMCU CA" -i ~/Downloads/myMCU-ca.crt

If certutil is missing: sudo apt install libnss3-tools (or sudo dnf install nss-tools).

Or import in the browser UI

Chrome → chrome://settings/certificates → Authorities → Import → select the file → tick Trust this certificate for identifying websites.

Firefox ignores the Windows/macOS/Linux store and keeps its own — always do this step for Firefox.

  1. Open Settings → Privacy & Security → scroll to Certificates → View Certificates…
  2. Tab Authorities → Import… → choose myMCU-ca.crt
  3. Tick Trust this CA to identify websites → OK
  4. Restart Firefox completely.

The serial monitor itself only exists in Chrome and Edge — Firefox can edit, compile and use the AI, but Web Serial is not available there.

3 · Check it worked

  1. Quit the browser completely (all windows — on Windows also check the tray) and start it again. Chrome caches certificate decisions per process.
  2. Open https://…:4443 — the padlock must be a normal padlock, with no “Not secure” and no click-through warning.
  3. Sign in, open a project and press Serial Monitor → Connect. If the port list appears, the certificate is doing its job.

Clicking “Advanced → Proceed” does not work for the serial monitor. Chrome only enables Web Serial when the certificate is genuinely trusted.

Troubleshooting

“Your connection is not private” / NET::ERR_CERT_AUTHORITY_INVALID
The CA is not installed, or the browser was not restarted. Redo step 2, then fully quit and reopen the browser.
“NET::ERR_CERT_COMMON_NAME_INVALID” or the address is not listed
The certificate was made for a different address. Compare the valid for list above with the address in the bar. If they differ, ask your teacher to regenerate the certificate with this server's current IP, then download it again.
Chrome still warns after installing on Windows
You probably installed it into Current User instead of Local Machine, or into Personal instead of Trusted Root Certification Authorities. Re-run Option A from an Administrator prompt.
The padlock is fine, but the Serial Monitor says “not supported”
Web Serial only exists in Chrome and Edge (desktop). Firefox and Safari cannot do it.
Everything works, then breaks after a reboot
The certificate is still installed — the server's address may have changed (DHCP). Use the address the server prints on startup, or ask for a reservation.