Protected Sites
If your website or web app is protected (e.g with Cloudflare or similar), behind a firewall, or require users to be authenticated, you will need additional settings when setting up Usersnap.
To get these accurate screenshots, we are storing the HTML when your users are taking a screenshot in a feedback item. But to accurately render them, our rendering-servers need access to your web pages to have access to the CSS and JavaScript files embedded in the HTML.
If your website or web application is protected by a firewall or a script, you and your technical team need to make sure that these resources (CSS, JavaScript) are available for our rendering servers.
If you have any further questions, please contact our customer success team.
Basic Authentication
If your site requires basic authentication (.htaccess), you need to grant access to the Usersnap servers (*.usersnap.com).
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 144.76.224.70 78.46.60.85 136.243.88.28 52.51.159.222 52.50.237.226 52.208.135.82 18.196.29.249 18.196.146.235 18.196.76.93
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: https://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 52.51.159.222;
allow 52.50.237.226;
allow 52.208.135.82;
allow 18.196.29.249;
allow 18.196.146.235;
allow 18.196.76.93;
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.
Protected/Firewall
If you can't check for partial hostnames using a reverse lookup, you can get our comprehensive list of renderer IPs.
List of Rendering IPs
52.51.159.222
52.50.237.226
52.208.135.82
18.196.29.249
18.196.146.235
18.196.76.93
If you are not able to change a firewall rule, you can use our browser extensions which will work without any firewall change.
Using a different screenshot rendering technology
Our Usersnap feedback platform got a huge upgrade and you are able to collect screenshots via an alternative rendering technology.
Updated over 3 years ago