From 3a7c506a8f11356aca256df3e9dfa27a18fbb75a Mon Sep 17 00:00:00 2001 From: silversword411 Date: Tue, 18 Jan 2022 00:04:20 -0500 Subject: [PATCH] docs - enabling keys --- docs/docs/troubleshooting.md | 4 ++-- docs/docs/update_server.md | 2 +- docs/mkdocs.yml | 1 + 3 files changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/docs/troubleshooting.md b/docs/docs/troubleshooting.md index 0120abdd..e4d834ba 100644 --- a/docs/docs/troubleshooting.md +++ b/docs/docs/troubleshooting.md @@ -39,7 +39,7 @@ bash -x install.sh 2>&1 | tee install.log ## "Bad credentials" error when trying to login to the Web UI -If you are sure you are using the correct credentials and still getting a "bad credentials" error, open your browser's dev tools (ctrl + shift + j on chrome) and check the Console tab to see the real error. +If you are sure you are using the correct credentials and still getting a "bad credentials" error, open your browser's dev tools (++ctrl+shift+j++ on chrome) and check the Console tab to see the real error. It will most probably be a CORS error which means you need to check your DNS settings and make sure whatever computer you're trying to access the UI from resolves your 3 subdomains to the correct IP of the server running the RMM (public IP if running in the cloud, or private IP if running behind NAT). @@ -138,7 +138,7 @@ This will fix permissions and reinstall python/node packages that might have got Check the debug log from the web UI: **File > Debug Log** -Open your browser's dev tools (ctrl + shift + j on chrome) and check the Console tab for any errors +Open your browser's dev tools (++ctrl+shift+j++ on chrome) and check the Console tab for any errors Check all the systemd services that the rmm uses to function and check to make sure they're all active/running and enabled: diff --git a/docs/docs/update_server.md b/docs/docs/update_server.md index 0df8c2ec..bd766cbb 100644 --- a/docs/docs/update_server.md +++ b/docs/docs/update_server.md @@ -67,7 +67,7 @@ To renew your Let's Encrypt wildcard cert, run the following command, replacing sudo certbot certonly --manual -d *.example.com --agree-tos --no-bootstrap --manual-public-ip-logging-ok --preferred-challenges dns -m admin@example.com --no-eff-email ``` -Same instructions as during install for [verifying the TXT record](install_server.md#deploy-the-txt-record-in-your-dns-manager) has propagated before hitting Enter. +Same instructions as during install for [verifying the TXT record](install_server.md#deploy-the-txt-record-in-your-dns-manager) has propagated before hitting ++enter++. After this you have renewed the cert, simply run the `update.sh` script, passing it the `--force` flag. diff --git a/docs/mkdocs.yml b/docs/mkdocs.yml index 538d7af6..c8ff9081 100644 --- a/docs/mkdocs.yml +++ b/docs/mkdocs.yml @@ -87,6 +87,7 @@ extra: link: "https://github.com/wh1te909/tacticalrmm" markdown_extensions: + - pymdownx.keys - pymdownx.inlinehilite - admonition - pymdownx.details