dotnet-devcert-trust

Diagnose and fix .NET HTTPS dev certificate trust issues on Linux.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/tientt010/Dotnet-JiraLite-Microservices --skill dotnet-devcert-trust-tientt010
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-devcert-trust
Source: https://github.com/tientt010/Dotnet-JiraLite-Microservices/tree/main/.github/skills/dotnet-devcert-trust
Command: npx skills add https://github.com/tientt010/Dotnet-JiraLite-Microservices --skill dotnet-devcert-trust-tientt010

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Linux developers frequently encounter untrusted .NET dev certificates because the system CA bundle does not reflect the user-level certificate store. This Skill provides a complete diagnostic and recovery workflow to export the dev certificate, install it into the system trust store, and rebuild the CA bundle across Ubuntu, Fedora, Arch, and WSL2 environments, ensuring TLS trust for localhost services and inter-service communication.

Core Features & Use Cases

  • End-to-end trust recovery: Generate/regenerate the dev cert, export as PEM, install into the system trust store, and rebuild the CA bundle.
  • Distro-specific guidance: Covers Ubuntu/Debian, Fedora/RHEL, Arch, and WSL2 with commands and caveats.
  • Operational readiness: Enables .NET apps, curl, OpenSSL, and browsers to trust the dev certificate for Redis TLS and gRPC during development.

Quick Start

Follow the recovery procedure to export, install, and rebuild the system CA bundle for the Linux dev certificate.

Frequently Asked Questions about dotnet-devcert-trust

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix untrusted .NET HTTPS dev certificate errors on Linux?

To fix untrusted .NET HTTPS dev certificate errors on Linux, you need to export the certificate and install it into the system CA trust store. This ensures local development tools like curl and OpenSSL trust the localhost dev certificate.

Why does my Linux system not trust the .NET developer certificate for local development?

Your Linux system does not trust the .NET developer certificate because the system CA bundle does not automatically reflect the user-level certificate store. Rebuilding the CA bundle after exporting and installing the PEM certificate resolves this trust issue.

How do I make .NET dev certificates trusted in WSL2 for Redis TLS and gRPC?

To make .NET dev certificates trusted in WSL2 for Redis TLS and gRPC, apply a recovery workflow to export the dev cert, install it into the system trust store, and rebuild the CA bundle. This enables secure inter-service communication during development.

Does this .NET dev cert trust recovery procedure support Fedora and Arch Linux?

Yes, the .NET dev cert trust recovery procedure supports Fedora, Arch, Ubuntu, Debian, and WSL2 environments. It provides distro-specific commands to install the exported certificate into the system trust store and rebuild the CA bundle.

What is the best way to rebuild the system CA bundle for .NET local development on Ubuntu?

The best way to rebuild the system CA bundle on Ubuntu for .NET development is to run the full diagnostic and recovery workflow. This exports your dev certificate as PEM, installs it to the system trust store, and rebuilds the bundle for proper TLS validation.

.NET dev certificate trust not working on Linux after dotnet dev-certs https trust, what now?

If .NET dev certificate trust is not working on Linux, the user-level trust store likely failed to sync with the system CA bundle. You must manually export the dev cert as PEM, install it into the system trust store, and rebuild the CA bundle.