Skip to content

leproxy not support self-signed ssl certs ? #10

@changchichung

Description

@changchichung

I have a domain name, let's say it's called abc.com. There is a machine with the hostname rc.abc.com. I have already set up https://rc.abc.com:44333 to open a Django program that I wrote. The SSL certificate file used here is generated by myself using OpenSSL.

Now I have applied for another domain name, called aaa.cc. I want users to be able to access https://rc.abc.com:44333 through https://app.aaa.cc. My mapping file looks like this:

app.aaa.cc: https://rc.abc.com:44333

Unfortunately, this does not work, and the browser only shows a blank page. However, if I modify my program to use HTTP service and use the same port 44333, my mapping file looks like this:

app.aaa.cc: http://rc.abc.com:44333

Now I can see my app screen correctly.

Is there something wrong with my settings? I still want my app to use HTTPS to provide services!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions