From Legacy to Secure: Migrating Apache/Django to HTTPS with Multiple Domains

on

Today I completed a major piece of infrastructure work: moving an existing Apache 2.4 setup with Django applications from plain HTTP to a full HTTPS configuration.

The job involved:

  • Migrating the main project from www.tweedehands.autos to a new dedicated subdomain sendgrid.tweedehands.autos
  • Configuring Apache VirtualHosts with WSGI for multiple Django apps on the same server/IP
  • Installing and cleaning up SSL certificates (ensuring the chain is valid and root certs are excluded)
  • Setting up proper redirects (HTTP → HTTPS, domain → subdomain)
  • Keeping additional services such as the webmailer app untouched and online during the migration

The outcome:

  • All traffic is now served securely over HTTPS
  • Clear separation between applications and domains
  • Smooth redirect logic for users and search engines
  • A cleaner, future-proof SSL chain without browser warnings

It’s always satisfying to modernize infrastructure while preserving stability for existing applications. Another step forward in keeping platforms secure, reliable, and ready for scaling.

Comments

Post a Comment