Topic: Port Forwarding and SSL Cert of Webserver in LAN network

[ionosphere]

I have a Rasberry Pi inside a LAN network and it got Apache 2 Webserver (and Debian) on it. We have a host that did a port forwarding to the Rasberry Pi in our LAN network so we could access it online, like http://www.mysite.com:8888. The port 8888 is forwarded to port 80 of the little machine and everything works correctly. I can access my index.html online.

However, I want to connect to my pi via HTTPS. We have already set port forwarding so anything coming into https://www.mysite.com:9999 will be forwarded to the port 443 HTTPS of the Pi. (Accessing https://www.mysite.com:9999 right now would yield "www.mysite.com refused to connect." in just a second.)

This is my first time doing HTTPS stuff, and from reading around, I see I have to get myself a certificate to do HTTPS connection. And correct me if I am wrong, do I need the SSL certificate being ran on the host that did port forwarding to us? Or can I generate my own SSL certificate that will work in this port forwarding scenario? (If yes, what must be used as domain name here for generating the certificate? Any other config required?) If not, what can be done here if I am to make my Pi connectable via HTTPS here?

[admin]

Have a look at http://httpd.apache.org/docs/2.4/ssl/