Title here
Summary here
Trust PiRogue self-signed certificate
Requirements
- PiRogue installation is done
PUBLIC_EXTERNAL_ADDRESSandEXTERNAL_ADDRESSare different (See Administration concepts)- Public external access is not enabled
If we want to access the PiRogue Dashboard, we must validate a security check the first time we browse the service.
... in 3 steps
Browse to dashboard
You should access dashboard browsing to https://pirogue.local/dashboard if your default installation has SYSTEM_HOSTNAME: pirogue.
Details
Depending on PiRogue variables, EXTERNAL_ADDRESS and SYSTEM_HOSTNAME is where the dashboard is exposed.
It’s independently accessible at https://EXTERNAL_ADDRESS/dashboard or https://SYSTEM_HOSTNAME.local/dashboard.
See Administration concepts for more details.
Show certificate warning details
The first time we browse the dashboard served with a self-signed certificate, the browser warns us about the situation.
Accessing details of the self-signed certificate differs depending on the browser we use:
- Verify the address
- Click on
Advanced
- Verify the address
- Click on
Advanced
- Verify the address
- Click on
Show details
Accept the certificate exception
Accepting a self-signed certificate differs depending on the browser we use:
- Optionally
View certificateto examine the current certificate - Click on
Accept the Risk and Continue
- Click on
Proceed to <SERVER_ADDRESS> (unsafe)
- Click on
Visit this website
- Double confirm exception by clicking on
Visit website
- Enter your user password
- Then confirm the security exception by clicking on
Update settings
Going further
Optionally, learn how you can double-check the self-certificate served by the PiRogue