Link check report
Result: Broken links detected. Output:
https://docs.paratoolspro.com/Azure/getting-started-Azure-CCWS/
error when dialing [::1]:8443: dial tcp [::1]:8443: connect: connection refused https://localhost:8443
Triage notes
1 of 1 errors is a suspected false positive; no real broken links found.
- URL:
https://localhost:8443 (linked from https://docs.paratoolspro.com/Azure/getting-started-Azure-CCWS/)
- Classification: suspected-false-positive
- Reason:
docs/Azure/getting-started-Azure-CCWS.md:91 instructs the reader to open az network bastion tunnel and then browse to https://localhost:8443 on their own machine to reach the VM's DCV/RDP endpoint through the tunnel. The markdown uses an autolink (<https://localhost:8443>), so it renders as a real <a href> in the HTML output and muffet dutifully tries to crawl it. localhost inside the GitHub Actions runner is never a real service, so the connection is always refused — this is expected and not a defect in the docs or the site.
- Suggested manual next step: Add a host-specific
--exclude pattern to .github/workflows/link-check-prod.yml's muffet invocation to skip localhost URLs going forward, e.g.:
--timeout=30 \
--ignore-fragments \
+ --exclude='^https?://localhost(:[0-9]+)?(/|$)' \
--header="User-Agent: ParaToolsProLinkChecker/1.0 (+https://github.com/ParaToolsInc/ParaToolsPro)" \Why this wasn't opened as a PR: The automation attempted to push this exact change on branch claude/link-fixes-32950167593, but the push was rejected by GitHub: "refusing to allow a GitHub App to create or update workflow .github/workflows/link-check-prod.yml without workflows permission." The GitHub App token used by this job does not have the workflows scope needed to modify files under .github/workflows/, which is a GitHub-side security restriction on App-authored workflow edits (not something this automation should bypass). A human with an appropriately-scoped token/PAT needs to apply the one-line diff above, or grant the App the workflows permission if App-authored workflow-file PRs should be supported for future runs.
Link check report
Result: Broken links detected. Output:
Triage notes
1 of 1 errors is a suspected false positive; no real broken links found.
https://localhost:8443(linked fromhttps://docs.paratoolspro.com/Azure/getting-started-Azure-CCWS/)docs/Azure/getting-started-Azure-CCWS.md:91instructs the reader to openaz network bastion tunneland then browse tohttps://localhost:8443on their own machine to reach the VM's DCV/RDP endpoint through the tunnel. The markdown uses an autolink (<https://localhost:8443>), so it renders as a real<a href>in the HTML output and muffet dutifully tries to crawl it.localhostinside the GitHub Actions runner is never a real service, so the connection is always refused — this is expected and not a defect in the docs or the site.--excludepattern to.github/workflows/link-check-prod.yml's muffet invocation to skiplocalhostURLs going forward, e.g.:--timeout=30 \ --ignore-fragments \ + --exclude='^https?://localhost(:[0-9]+)?(/|$)' \ --header="User-Agent: ParaToolsProLinkChecker/1.0 (+https://github.com/ParaToolsInc/ParaToolsPro)" \Why this wasn't opened as a PR: The automation attempted to push this exact change on branch
claude/link-fixes-32950167593, but the push was rejected by GitHub: "refusing to allow a GitHub App to create or update workflow.github/workflows/link-check-prod.ymlwithoutworkflowspermission." The GitHub App token used by this job does not have theworkflowsscope needed to modify files under.github/workflows/, which is a GitHub-side security restriction on App-authored workflow edits (not something this automation should bypass). A human with an appropriately-scoped token/PAT needs to apply the one-line diff above, or grant the App theworkflowspermission if App-authored workflow-file PRs should be supported for future runs.