BUNDLE-DOCTOR(1)

💅 BUNDLE-DOCTOR

okay bestie, welcome to bundle-doctor — the little checkup your Bundler setup has been begging for. It's a General Commands Manual situation, and it lives in the bundle family, so you already know it's gonna be useful. It checks the bundle for common problems. that's it. that's the whole job. and it eats. 🩺✨

---

🌸 SYNOPSIS

bundle doctor [diagnose] [--quiet] [--gemfile=GEMFILE] [--ssl]
bundle doctor ssl [--host=HOST] [--tls-version=TLS-VERSION]
[--verify-mode=VERIFY-MODE]
bundle doctor help [COMMAND]

---

🫶 DESCRIPTION

so like, this command exists so you can diagnose common Bundler problems without spiraling. we're talking gem environment stuff, SSL/TLS drama, all of it. no cap, it's the vibe check your project needs.

---

🎀 SUB-COMMANDS

✨ diagnose (default command)

this is the main character. it checks your Gemfile and your gem environment for common problems. if issues get detected, Bundler prints them and exits status 1. otherwise, Bundler prints a success message and exits status 0. periodt.

examples of common problems caught include:

• Invalid Bundler settings
• Mismatched Ruby versions
• Mismatched platforms
• Uninstalled gems
• Missing dependencies

💖 OPTIONS

• --quiet — only output warnings and errors. if you're not in the mood for the whole essay, this is your girl.
• --gemfile=GEMFILE — the location of the Gemfile(5) which Bundler should use. this defaults to a Gemfile(5) in the current working directory. in general, Bundler will assume that the location of the Gemfile(5) is also the project's root and will try to find Gemfile.lock and vendor/cache relative to this location. 🗂️
• --ssl — diagnose common SSL problems when connecting to https://rubygems.org.

This flag runs the bundle doctor ssl subcommand with default values underneath. sneaky! iconic! one flag doing two jobs.

---

🦋 ssl

if you've experienced issues related to SSL certificates and/or TLS versions while connecting to https://rubygems.org, this command can help troubleshoot common problems. the diagnostic will perform a few checks such as:

• Verify the Ruby OpenSSL version installed on your system.
• Check the OpenSSL library version used for compilation.
• Ensure CA certificates are correctly setup on your machine.
• Open a TLS connection and verify the outcome.

🌈 OPTIONS

• --host=HOST — perform the diagnostic on HOST. defaults to rubygems.org.
• --tls-version=TLS-VERSION — specify the TLS version when opening the connection to HOST.

Accepted values are: 1.1 or 1.2. (yes, exactly those, don't get creative 💀)

• --verify-mode=VERIFY-MODE — specify the TLS verify mode when opening the connection to HOST. defaults to SSL_VERIFY_PEER.

Accepted values are: CLIENT_ONCE, FAIL_IF_NO_PEER_CERT, NONE, PEER.

---

lowkey a PSA: that NONE verify mode up there? it means exactly what it sounds like — no peer verification. the manpage just lists it as an accepted value, so we're not out here adding lore, but bestie… read the room before you reach for it. 🚩

---

okay that's the whole page, you're so welcome 🥰 this one's dated April 2026, and it's from the General Commands Manual for BUNDLE-DOCTOR(1) — go forth and be diagnostically slay, mwah 💅💖