Home/ Questions/Q 7013799
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T22:26:17+00:00

Question moved to Serverfault ( https://serverfault.com/questions/346125/ssl-error-rx-record-too-long-ff-django-startssl-windows ) Feel free to delete this on if

  • 0

Question moved to Serverfault ( https://serverfault.com/questions/346125/ssl-error-rx-record-too-long-ff-django-startssl-windows )

Feel free to delete this on if that’s more appropriate (I don’t know what the convention is).

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    (That’s a question for ServerFault more than StackOverflow.)

    If I understand correctly, you’ve set up Django with SSL on port 8082 and without SSL on port 8081.

    It’s often not necessary to secure the communication between the Apache Httpd server and the server behind ProxyPass, from localhost to localhost. You could simply use ProxyPass http://127.0.0.1:8081/.

    Alternatively, if you really want to use SSL/TLS for the communication to the backend (typically, if the server in the back is remote), you’d need to use ProxyPass https://127.0.0.1:8082/ (https) and set the SSLProxy* directives (see mod_proxy summary).

    • 0