0 of 0

HTTPS-Only Mode Setup

Intermediate
~25 min

Introduction

CURRENT

THE SCENARIO

Security First: Running production services over unencrypted HTTP exposes sensitive data (API keys, VM credentials, configuration) to network eavesdropping and man-in-the-middle attacks. The Parallels DevOps Service supports TLS/HTTPS encryption and can optionally disable HTTP entirely when TLS is properly configured.

With HTTPS-only mode, you can:

  • Encrypt all API traffic between clients and the DevOps Service - Prevent accidental plaintext communication in production - Validate TLS certificates automatically before disabling HTTP - Maintain backward compatibility with dual-protocol mode (HTTP + HTTPS) - Get safety fallbacks if TLS configuration fails Before you begin: This tutorial assumes you have a working Parallels DevOps Service instance. If you haven’t set it up yet, complete the DevOps CLI Quick Start tutorial first.

KEY OUTCOMES

  • Generate TLS certificates (self-signed or CA-signed)
  • Configure HTTPS/TLS on Parallels DevOps Service
  • Understand dual-protocol vs HTTPS-only mode behavior
  • Implement HTTPS-only mode for production security
  • Troubleshoot common TLS configuration issues
PREREQUISITES
MANDATORY
  • **Parallels DevOps Service** installed and running — [Setup guide](/prl-devops-service/tutorials/tutorial_devops-cli-quickstart/)
  • Access to service configuration (config.yaml or environment variables)
  • OpenSSL installed for certificate generation
flowchart TB A[Client] -->|HTTPS Request| B{TLS Enabled?} B -->|Yes| C[HTTPS Server :8443] C -->|TLS Validation| D{Certificate Valid?} D -->|✓ Valid| E[Encrypted Response] D -->|✗ Invalid| F[TLS Error] B -->|No| G[HTTP Server :8080] G -->|Plaintext| H[Unencrypted Response] I{DISABLE_HTTP_WHEN_TLS?} -->|true + Valid TLS| J[HTTP Disabled] I -->|false| K[Both HTTP & HTTPS] I -->|true + Invalid TLS| L[Fallback to HTTP]
Loading…