Update troubleshooting.mdx

[burumumishsa]

Added Plugin uninstall failure alternative

Summary by CodeRabbit

• Documentation
  • Added troubleshooting guide for plugin uninstallation issues via SSH, including step-by-step instructions and solutions for resolving permission-related errors that may occur after plugin removal.

[netlify]

✅ Deploy Preview for pelica ready!

Name	Link
🔨 Latest commit	e6c462a
🔍 Latest deploy log	https://app.netlify.com/projects/pelica/deploys/6a2df6863e72340008b0a3d6
😎 Deploy Preview	https://deploy-preview-204--pelica.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Warning

Review limit reached

@burumumishsa, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 47 minutes and 29 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f4fe910b-8f0e-4c36-b397-cf9d679c1634

📥 Commits

Reviewing files that changed from the base of the PR and between 43ebf0f and e6c462a.

📒 Files selected for processing (1)

• docs/troubleshooting.mdx

📝 Walkthrough

Walkthrough

A new "Plugin uninstalling issues" subsection is added to docs/troubleshooting.mdx. It provides SSH-based steps using php artisan p:plugin:uninstall, a note about uninstall duration, and a sudo chown -R www-data:www-data /var/www/pelican command to fix potential 500 errors after removal.

Changes

Plugin Uninstall Troubleshooting Docs

Layer / File(s)	Summary
Plugin uninstall troubleshooting section docs/troubleshooting.mdx	Adds a new subsection with the artisan uninstall command, a timing note, and a permissions reset command to resolve post-uninstall 500 errors.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A bunny hopped in, artisan in paw,
"Uninstall your plugins without a flaw!"
🐇 SSH in, type the command with care,
A chown for good measure, permissions repaired.
No 500 errors shall trouble thee there! 🥕

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update troubleshooting.mdx' is vague and generic, using non-descriptive language that fails to convey the specific nature of the changes being made.	Consider using a more specific title that highlights the main change, such as 'Add plugin uninstalling troubleshooting section' to clearly communicate the purpose of the documentation update.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/troubleshooting.mdx`:
- Around line 156-159: The troubleshooting section hardcodes the www-data user
in the permission-fixing command, which only applies to Debian-based
deployments. Instead of providing this single-use command, either reference the
nginx and apache ownership variants that are already documented elsewhere in the
troubleshooting guide, or provide generic guidance telling readers to replace
www-data with the actual user their web server runs under (e.g., nginx, apache,
or their specific deployment user). This ensures the fix works across all
deployment types without leaving non-Debian setups with incorrect permissions.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 02bcd39a-a2c2-47b5-8e26-dabf1f8fdab7

📥 Commits

Reviewing files that changed from the base of the PR and between b0e3632 and 43ebf0f.

📒 Files selected for processing (1)

• docs/troubleshooting.mdx

📜 Review details

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2026-02-02T01:29:01.167Z

Learnt from: parkervcp
Repo: pelican-dev/docs PR: 186
File: docs/guides/disk-quotas/ext4-xfs.mdx:176-192
Timestamp: 2026-02-02T01:29:01.167Z
Learning: In the Pelican docs repo (pelican-dev/docs), trailing slashes on device paths (e.g., /dev/sdb/) in the disk quotas guidance should not be flagged. Accept both forms and ensure this exception is only applied to device path examples in documentation; maintain standard validation for other content.

Applied to files:

• docs/troubleshooting.mdx