Webgui With Ssl On Apache

[christophk]

Dear all

 

I am using btsync constantly and it's a great software.

Thanks a lot for the cool program.

 

I need a bit of help in order to make the access to the WebGUI of a linux btsync client encrypted with SSL.

 

Is there any howto, how this might be possible? I only found something for nginx, but I don't know nginx at all.

 

Currently I am trying the following:

 

on my domain example.com I want to use the subdomain bit.example.com to access the btsync webgui.

I tried to keep it simple So without SSL I did this in my /etc/apache2/sites-available:

 

<VirtualHost *:80>

        ServerName      bit.example.com

        Redirect permanent / http://bit.example.com:8888

</VirtualHost>

 

This works for http. Now I want to try it with https, so I did this:

 

<VirtualHost *:80>

        ServerName      bit.example.com

        Redirect permanent / https://bit.yna.cc:8888

</VirtualHost>

 

And added the certificates my SSL sites-available config file:

 

<VirtualHost *:8888>

 

        ServerName      bit.example.com

 

        SSLEngine On

 

        SSLCertificateFile /etc/apache2/certs/bit.example.com/ssl.crt

        SSLCertificateKeyFile /etc/apache2/certs/bit.example.com/ssl.key

 

</VirtualHost>

 

I also tried the same, listening on port 443. But I only get error messages that there is an internal server problem.

Can someone point me into the right direction what I have to do here?

 

Every support would be very much appreciated,

 

KR, Chris

[frater]

I solved the "ssl problem" in 10 minutes on my system. It was already running nginx though.

I never used apache as reverse proxy. In fact nowadays it's common practice to run nginx in front of apache to protect it from hackers.

A reverse proxy has less code than a full-fledged webserver. The user that's running the nginx process doesn't have access to the files of your website. A potential hacker that's using buffer underpin techniques will only get access as an nginx user.

Apache itself will not have a TCP-connection with the world. It will only receive clean http directives from the reverse proxy. I have experience with pound, nginx and varnish. I never used apache for this task.

Why do you insist on using apache?

It's like driving a bus to work. You'll probably get there, but not that practical.

In this forum there's a how-to for nginx.

Cheers