Protected Sites / Usersnap behind a Firewall
If you are using a staging setup which is protected using BasicAuth (.htaccess), please grant the Usersnap servers (*.usersnap.com) acccess.
You will find the configuration examples for Apache and IIS helpful:
Configuration for Apache 2.2
Order deny,allow Deny from all AuthType Basic AuthName "Password protected" Require valid-user AuthUserFile /path/to/your/.htpasswd Allow from .usersnap.com Satisfy Any
Configuration for Apache 2.4
AuthType Basic AuthName "Password protected" AuthUserFile /path/to/your/.htpasswd Require valid-user Require ip 22.214.171.124 126.96.36.199 188.8.131.52
Configuration for IIS7+
Open the IIS Manager, click on your website and open "IP address and domain restrictions". In this view, enable domain restrictions (Edit Feature Settings | Enable domain restrictions) and add an allow rule for the domain "*.usersnap.com". You can even find more reference on this technique at Microsoft: http://technet.microsoft.com/en-us/library/cc731598(v=ws.10).aspx.
Configuration for Nginx
To enable specific IP ranges on a Nginx server, please add the following ip addresses to your allow list: current renderer of Usersnap
You have to add the configuration to your nginx.conf file, please add a line for the ip addresses like:
allow 184.108.40.206; allow 220.127.116.11; allow 18.104.22.168;
There are a lot of tutorials out there like this tutorial.
If you use any other web server (e.g. Tomcat, ...) just contact us, we are happy to find a solution together with you.
If you can't check for partial hostnames using a reverse lookup, you can get our comprehensive list of renderer IPs.
Please note that these IPs are subject to change, however, the link will always contain an updated list.
If you are not able to change a firewall rule, we have browser extensions which work without any firewall change.
List of rendering IPs
Here you can find a comprehensive list of our rendering engines.
22.214.171.124 126.96.36.199 188.8.131.52