diff --git a/docs/data/routes/docs/temp/node-certificates/en.md b/docs/data/routes/docs/fundamentals/troubleshooting/node-certificates/en.md
similarity index 100%
rename from docs/data/routes/docs/temp/node-certificates/en.md
rename to docs/data/routes/docs/fundamentals/troubleshooting/node-certificates/en.md
diff --git a/docs/data/routes/docs/nextjs/getting-started-nextjs/walkthrough-dotnetnew/en.md b/docs/data/routes/docs/nextjs/getting-started-nextjs/walkthrough-dotnetnew/en.md
index 22e7a99f58..2cfd61c7ed 100644
--- a/docs/data/routes/docs/nextjs/getting-started-nextjs/walkthrough-dotnetnew/en.md
+++ b/docs/data/routes/docs/nextjs/getting-started-nextjs/walkthrough-dotnetnew/en.md
@@ -126,7 +126,7 @@ To create the `MyProject` solution:
 
      > On local environments, Sitecore instances are installed using privately signed certificates. `.\init.ps1` generates certificates using the `mkcert` utility. Node.js rejects these certificates because their root CAs are not known. 
      >
-     > If this is your first time using `mkcert` with Node.js, you will need to [manually set the  `NODE_EXTRA_CA_CERTS` environment variable](/docs/temp/node-certificates) to prevent HTTPS errors.
+     > If this is your first time using `mkcert` with Node.js, you will need to [manually set the  `NODE_EXTRA_CA_CERTS` environment variable](/docs/fundamentals/troubleshooting/node-certificates) to prevent HTTPS errors.
      >
      > The `.\init.ps1` script will instruct you on how to set the `NODE_EXTRA_CA_CERTS` environment variable in your user or system environment variables: 
      >
diff --git a/docs/data/routes/docs/nextjs/troubleshooting/en.md b/docs/data/routes/docs/nextjs/troubleshooting/en.md
index 8f9c68ca90..98263d6013 100644
--- a/docs/data/routes/docs/nextjs/troubleshooting/en.md
+++ b/docs/data/routes/docs/nextjs/troubleshooting/en.md
@@ -57,7 +57,7 @@ If you are working with a local Sitecore instance using a privately signed certi
 
 > UnauthorizedError: invalid signature
 
-Ensure you've [configured Sitecore CA certificates for Node.js](/docs/temp/node-certificates).
+Ensure you've [configured Sitecore CA certificates for Node.js](/docs/fundamentals/troubleshooting/node-certificates).
 
 ## Errors deploying a JSS app locally
 
diff --git a/docs/data/routes/docs/techniques/authentication/sitecore-auth/en.md b/docs/data/routes/docs/techniques/authentication/sitecore-auth/en.md
index 6044caefb1..648acf0ab3 100644
--- a/docs/data/routes/docs/techniques/authentication/sitecore-auth/en.md
+++ b/docs/data/routes/docs/techniques/authentication/sitecore-auth/en.md
@@ -60,7 +60,7 @@ It is possible to build a simple login/logout using the [SSC Authentication serv
 * The proxy system utilized by Headless mode is able to proxy requests to the SSC Auth services, and proxy the `.ASPXAUTH` cookie.
 * Because the requests are proxied, CORS headers should not be an issue.
 * For login functionality to work however, the `apiHost` in `config.js` of the sample headless server needs to be updated to SSL, e.g. `https://JssReactWeb`.
-* If proxying to a development Sitecore instance using a privately signed certificate, ensure you've [configured Sitecore CA certificates for Node.js](/docs/temp/node-certificates).
+* If proxying to a development Sitecore instance using a privately signed certificate, ensure you've [configured Sitecore CA certificates for Node.js](/docs/fundamentals/troubleshooting/node-certificates).
 * Alternatively, you can disable SSL validation entirely by setting `secure` to `false` in the proxy options, e.g. in `config.js`
 
 ```
diff --git a/docs/data/routes/docs/techniques/ssr/headless-mode-ssr/en.md b/docs/data/routes/docs/techniques/ssr/headless-mode-ssr/en.md
index 6f67ea1674..1688fba70e 100644
--- a/docs/data/routes/docs/techniques/ssr/headless-mode-ssr/en.md
+++ b/docs/data/routes/docs/techniques/ssr/headless-mode-ssr/en.md
@@ -28,7 +28,7 @@ All Sitecore marketing features are supported by this headless mode, including p
 
     > NOTE: It is possible to configure these settings using environment variables as well, if that is preferable. This is great for containers and some PaaS hosts.
 
-2. If proxying to a development Sitecore instance using a privately signed certificate, ensure you've [configured Sitecore CA certificates for Node.js](/docs/temp/node-certificates). Alternatively, you can disable SSL validation entirely by setting `secure` to `false` in the proxy options, e.g. in `/config.js`
+2. If proxying to a development Sitecore instance using a privately signed certificate, ensure you've [configured Sitecore CA certificates for Node.js](/docs/fundamentals/troubleshooting/node-certificates). Alternatively, you can disable SSL validation entirely by setting `secure` to `false` in the proxy options, e.g. in `/config.js`
 
 ```
   proxyOptions: {
diff --git a/docs/src/app/components/Navigation/docs.js b/docs/src/app/components/Navigation/docs.js
index cce52c2f79..2b490f7213 100644
--- a/docs/src/app/components/Navigation/docs.js
+++ b/docs/src/app/components/Navigation/docs.js
@@ -200,6 +200,16 @@ export default {
             },
           ],
         },
+        {
+          url: 'troubleshooting',
+          displayName: 'Troubleshooting',
+          children: [
+            {
+              url: 'node-certificates',
+              displayName: 'Sitecore CA certificates for Node.js',
+            },
+          ],
+        },
       ],
     },
     {
diff --git a/docs/src/app/components/Navigation/nextjs.js b/docs/src/app/components/Navigation/nextjs.js
index 17920c8610..0165018d02 100644
--- a/docs/src/app/components/Navigation/nextjs.js
+++ b/docs/src/app/components/Navigation/nextjs.js
@@ -196,6 +196,10 @@ export default {
         },
       ],
     },
+    {
+      url: 'troubleshooting',
+      displayName: 'Troubleshooting',
+    },
   ],
   links: [],
 };