If your website or web app is protected, behind a firewall, or require users to be authenticated, you will need additional settings when setting up Usersnap.
If you have any further questions, please contact our customer success team.
If your site requires basic authentication (.htaccess), you need to grant access to the Usersnap servers (*.usersnap.com).
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
AuthType Basic AuthName "Password protected" AuthUserFile /path/to/your/.htpasswd Require valid-user Require ip 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206
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
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 220.127.116.11; allow 18.104.22.168; allow 22.214.171.124; allow 126.96.36.199; allow 188.8.131.52; allow 184.108.40.206;
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.
220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206
If you are not able to change a firewall rule, you can use our browser extensions which will work without any firewall change.
Updated 3 months ago