How to use HTTPS with Jam.py

Hello there! For other readers, since been a while from the OP question, there is a way to run gunicorn over SSL: https://groups.google.com/g/jam-py/c/M0GzXl1J3Gc/m/RPQ_u2FJAQAJ

However, the problem with gunicorn and Jam (or any wsgi app), is seeing the log files. And log files are really needed. Also, after the reboot, the app will not work unless there is a startup file created for gunicorn. Which is fiddly.

Hence, since Jam is a wsgi app, Apache can happily run on ssl with it. There is no need to start the application on port 8080 with gunicorn or to run “python server.py”, or as OP mentioned “pass the 443 command line argument to server.py”.

As per OP link, just set the SSL options and off you go.

Before even trying SSL, make sure Apache actually works: https://groups.google.com/g/jam-py/c/Zv5JfkLRFy4/m/JnoLSg3uGQAJ

Good luck

If you want to use Jam.py with HTTPS behind an Apache server, it’s typically best to utilize Apache as a reverse proxy for the Jam.py application. Instead of running the Jam.py application directly on port 443 (which will cause a conflict if Apache is already using that port), you should:

1. Run Jam.py on a different, unused port (e.g., 8080).
2. Configure Apache to reverse proxy HTTPS requests on port 443 to the Jam.py application running on port 8080 (or whatever port you chose).

Here’s a step-by-step guide:

1. Run Jam.py on an Unused Port: Start the Jam.py server on an unused port, say 8080.
2. Configure Apache as a Reverse Proxy: Update or create an Apache configuration file for your site/domain. Add the following configuration, adapting for your needs:

<VirtualHost *:443>
    ServerName yourdomain.com
    ServerAlias www.yourdomain.com

    # SSL Configuration from Certbot
    SSLEngine on
    SSLCertificateFile /etc/letsencrypt/live/yourdomain.com/fullchain.pem
    SSLCertificateKeyFile /etc/letsencrypt/live/yourdomain.com/privkey.pem
    Include /etc/letsencrypt/options-ssl-apache.conf

    # Reverse proxy configuration
    ProxyPreserveHost On
    ProxyPass / http://localhost:8080/
    ProxyPassReverse / http://localhost:8080/

</VirtualHost>

This configuration tells Apache to accept HTTPS requests on port 443 and forward (proxy) them to your Jam.py application running on port 8080.

3. Enable Necessary Apache Modules: Ensure you’ve enabled the necessary modules for proxy and SSL functionalities:

sudo a2enmod proxy
sudo a2enmod proxy_http
sudo a2enmod ssl

Now, when you access your domain via HTTPS (https://yourdomain.com), Apache will handle the SSL/TLS encryption and then proxy the requests to the Jam.py application.

Hi there,

You can not have two services listening on the same port. If your Apache service is already listening on port 443 with a valid SSL, you will not be able to start your Jam app on the same port.

You should start your app as normal and not on port 443.

An alternative option, would be to use Nginx as described here:

https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-16-04

The article uses Django as an example, but the setup will be the same.

Let me know how it goes!

Best,

Bobby