Page Comparison

We provide several guides here to integrate PowerFolder Server with third party web servers:

Apache Proxy and PowerFolder Server for SSL Encryption

In this article we are showing a configuration example for running using PowerFolder Server with an Apache Proxy for a SSL-encrypted web interface sessions.

Requirements

The requirements below are necessary for the setup:

• Apache 2.2 and higher with mod_proxy,mod_rewrite and mod_ssl enabled.
• A valid, officially signed SSL certificate.  PowerFolder Clients will NOT work with invalid or self-signed certificates.

PowerFolder Server Web Configuration

For this scenario we need to change settings in the server preferences:

• Set the Web Base URL under Preferences > Network > Server URLs:

  Code Block
  https://powerfolder.example.com

  
  

• Set the Web Tunnel URL under Preferences > Network > Server URLs:

  Code Block
  http://powerfolder.example.com/rpc

   Please note that the URL must use HTTP not HTTPS, since the traffic posted against that URL will be encrypted by the PowerFolder internal protocol.

   

  
  

• Set the HTTPS/SSL port under Preferences > Network > Hostname and Ports:

  Code Block
  "-1"

  
  

 After changing those settings, please restart PowerFolder Server.

Apache Configuration

Configure a virtual host within Apache, which responds to requests to http://powerfolder.example.com and https://powerfolder.example.com and forwards the requests to the web port of PowerFolder Server:

<VirtualHost *:80>
       ServerAdmin hostmaster@example.com
       ServerName powerfolder.example.com

       RewriteEngine on
       RewriteCond             %{SERVER_PORT}  !=443
       RewriteCond             %{REQUEST_URI}  !^/rpc
       RewriteRule             ^.*$            https://%{SERVER_NAME}%{REQUEST_URI} [NC,R=301,L]

         ProxyPass               /rpc                    http://10.0.0.1:8080/rpc     nocanon
       ProxyPassReverse        /rpc                    http://10.0.0.1:8080/rpc
 
</VirtualHost>


Listen 10.0.0.1:443
<VirtualHost 10.0.0.1:443>
       ServerAdmin hostmaster@example.com
       ServerName powerfolder.example.com

       SSLEngine  On
       SSLCACertificateFile   /etc/apache2/ssl/powerfolder.example.com.ca-bundle.crt
       SSLCertificateFile     /etc/apache2/ssl/powerfolder.example.com.crt
       SSLCertificateKeyFile  /etc/apache2/ssl/powerfolder.example.com.key
       SSLCipherSuite ALL:-ADH:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP


       ProxyPass               /rpc                    http://10.0.0.1:8080/rpc     nocanon
       ProxyPassReverse        /rpc                    http://10.0.0.1:8080/rpc


       ProxyPass               /rpc                    !

        ProxyPass               /                       http://10.0.0.1:8080/        nocanon
       ProxyPassReverse        /                       http://10.0.0.1:8080/
</VirtualHost>

 We exclude the /rpc URL part from the SSL-encryption, because this URL is used for the PowerFolder Clients to tunnel their traffic by using the HTTP POST method, in case they are behind a firewall and can't establish a direct connection to PowerFolder Server. Since the PowerFolder data traffic is encrypted anyway by a PowerFolder internal protocol, we don't need encryption here. It would just slow down the connection.

 Please note: When it is required by the SSL certificate authority to use an intermediate certificate, it has to be loaded with the SSLCACertificateFile configuration entry. If such an intermediate certificate is NOT required, you can simply drop that line.

Setting up Nginx as SSL proxy

In this article we are showing a configuration example for running using PowerFolder Server with a Nginx Proxy for a SSL-encrypted web interface sessions.

Requirements

The requirements below are necessary for the setup:

• Nginx 1.1 and higher.
• A valid, officially signed SSL certificate.    PowerFolder Clients will NOT work with invalid or self-signed certificates.

PowerFolder Server Web Configuration

For this scenario we need to change settings in the server preferences:

• Set the Web Base URL under Preferences > Network > Server URLs:

  Code Block
  https://powerfolder.example.com

  
  

• Set the Web Tunnel URL under Preferences > Network > Server URLs:

  Code Block
  http://powerfolder.example.com/rpc

   Please note that the URL should not use HTTP not HTTPS, since the traffic posted against that URL will be encrypted by the PowerFolder internal protocol. 

  
  

• Set the HTTPS/SSL port under Preferences > Network > Hostname and Ports:

  Code Block
  ' -1 '

 After changing those settings, please restart PowerFolder Server.

• PF server restart is required.

nginx Configuration

Configure a virtual host within Nginx, which responds to requests to http://powerfolder.example.com and https://powerfolder.example.com and forwards the requests to the web port of PowerFolder Server:

server {
      server { listen 80;
              listen 10.0.0.1;
                server_name powerfolder.example.com;
                location / {        
        location / {  
   rewrite       		rewrite ^ https://$server_name$request_uri? permanent;
       
        }
     
          location /rpc {
	                        proxyproxy_pass http://10127.0.0.1:8080/rpc;
        		proxy_set_header X-Forwarded-Host $host;
				proxy_set_header X-Forwarded-For $remote_addr;
  }        }
}

server {
		listen      server {
                listen 10.0.0.1:443;
                443 ssl;
		server_name powerfolder.example.com;
                		client_max_body_size 100G;

		ssl on;
                		ssl_certificate /etc/nginx/ssl/powerfolder.example.com.chained.crt;
                ssl_certificate_key /etc/nginx/ssl		ssl_certificate_key /etc/nginx/ssl/powerfolder.example.com.key;

                		location / {
                        proxy_pass http://10				proxy_pass http://127.0.0.1:8080;
				proxy_set_header X-Forwarded-Host $host;
				proxy_set_header X-Forwarded-For $remote_addr;
		}

		location /websocket {
				proxy_http_version 1.1;
				proxy_pass http://127.0.0.1:8080/websocket;
 }       		proxy_set_header  }

 We exclude the /rpc URL part from the SSL-encryption, because this URL is used for the PowerFolder Clients to tunnel their traffic by using the HTTP POST method, in case they are behind a firewall and can't establish a direct connection to PowerFolder Server. Since the PowerFolder data traffic is encrypted anyway by a PowerFolder internal protocol, we don't need encryption here. It would just slow down the connection.

 Please note: When it is required by the SSL certificate authority to use an intermediate certificate, a chained certificate has to be created. Simply create a new text file, copy & paste the intermediate certificate into it and right after it the actual certificate for your domain. In our example we called the file powerfolder.example.com.chained.crt.

Using nginx with cache (experimental)

It is possible to activate cache in nginx to reduce load of your PowerFolder Server. Static content will get cached by nginx and get delivered directly to the browser. The caching directory can get freely chosen. Since this might contain many data it should have sufficient disk space!

Please ensure to clean your caching directory after every server update to ensure, that no old cached content get delivered to your users.

https://www.nginx.com/blog/nginx-caching-guide/

		proxy_cache_path </etc/nginx/cache> levels=1:2 keys_zone=pf_cache:10m max_size=10g inactive=10m use_temp_path=off;
		server {
                listen 10.0.0.1;
                server_name powerfolder.example.com;
                location / {
                        rewrite        ^ https://$server_name$request_uri? permanent;
                }
                location /rpc {
                        proxy_pass http://10.0.0.1:8080/rpc;
                }
        }

        server {
                listen 10.0.0.1:443;
                server_name powerfolder.example.com;
                ssl on;
                ssl_certificate /etc/nginx/ssl/powerfolder.example.com.chained.crt;
                ssl_certificate_key /etc/nginx/ssl/powerfolder.example.com.key;

                location / {
                        proxy_pass http://10.0.0.1:8080;
						proxy_buffering on;
						proxy_cache pf_cache;
						proxy_cache_valid 200 1d;
						proxy_cache_key $proxy_host$request_uri$cookie_JSESSIONID;
 				}
        }X-Forwarded-Host $host;
				proxy_set_header X-Forwarded-For $remote_addr;
				proxy_set_header Upgrade $http_upgrade;
				proxy_set_header Connection "Upgrade";
		}

		location /websocket_client {
				proxy_http_version 1.1;
				proxy_pass http://127.0.0.1:8080/websocket_client;
       		    proxy_set_header X-Forwarded-Host $host;
				proxy_set_header X-Forwarded-For $remote_addr;
				proxy_set_header Upgrade $http_upgrade;
				proxy_set_header Connection "Upgrade";
		}
}

 We exclude the /rpc URL part from the SSL-encryption, because this URL is used for the PowerFolder Clients to tunnel their traffic by using the HTTP POST method, in case they are behind a firewall and can't establish a direct connection to PowerFolder Server. Since the PowerFolder data traffic is encrypted anyway by a PowerFolder internal protocol, we don't need encryption here. It would just slow down the connection.

 Please note: When it is required by the SSL certificate authority to use an intermediate certificate, a chained certificate has to be created. Simply create a new text file, copy & paste the intermediate certificate into it and right after it the actual certificate for your domain. In our example we called the file powerfolder.example.com.chained.crt.