mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 05:26:03 +03:00
[GH-ISSUE #334] NET::ERR_CERT_AUTHORITY_INVALID on Raspbian Buster #215
Labels
No labels
TLS stack issue
Windows
bug
duplicate
duplicate
enhancement
help wanted
help wanted
pull-request
question
question
root store
waiting for info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mkcert#215
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sguilliard on GitHub (Jan 24, 2021).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/334
Been following the directions to install on Raspberry Pi 4b here: https://kifarunix.com/how-to-create-self-signed-ssl-certificate-with-mkcert-on-ubuntu-18-04/ (using the latest releases - tried both mkcert-v1.4.3-linux-arm64 wouldn't execute, but the 32-bit version executed ok: mkcert-v1.4.3-linux-arm
mkcert appears to be installed ok, but the CA isn't being accepted by the Chromium browser on the local machine (should this also work for other machine accessing from the LAN?). Trying to find more details directions to see if there's soemthing I've missed, but now at a loss...
Browser returns the following in Chrome (Firefox the same):
@FiloSottile commented on GitHub (Jan 24, 2021):
mkcert needs to be installed on the machine from which you access the site. If you install it on a Raspberry Pi, you then need to follow there instructions to copy its CA to your computer and install it.
https://github.com/FiloSottile/mkcert#installing-the-ca-on-other-systems
@sguilliard commented on GitHub (Jan 24, 2021):
The error is from the local machine (the same machine that mkcert is installed on)
@sguilliard commented on GitHub (Jan 24, 2021):
I think I've solved the problem. Install should not be done from the root on a raspberry pi (do not use SUDO), and neither should the cert generation. Is this a thing just on the RPi? Anyway, all working now...
@FiloSottile commented on GitHub (Jan 24, 2021):
Glad you got it working. mkcert will generate a different CA for every user you run it as, so root will have a different CA.