Your access to the Usetrace.com web app
Allow http(s) and websocket protocols without restrictions to outgoing ports 80 and 443 on the domains usetrace.com and conference.usetrace.com.
Help! My editor gets stuck!
Some corporate firewalls may buffer websocket requests and this may cause connection issues in Usetrace editor. Check that websocket connections are unrestricted and unbuffered.
This is a helpful site to check that your firewall settings are not blocking websocket connections: http://websocketstest.com/
Usetrace access to your site
Usetrace needs to get access to your site that you want to test. You define your site in Usetrace as your Base URL.
If the URL is available in the public internet, you are good to go. Your site may not be available in the public internet, e.g. your staging environment. It is possible to allow Usetrace to access your internal sites as well.
Options on testing internal sites:
Whitelist Usetrace ip from your firewall (184.108.40.206, 220.127.116.11, 18.104.22.168 and 2a05:d018:139:b700::/56)
Make your web server publicly accessible for testing. See Tunneled connection.
If you use basic authentication, you can define the credentials in the Base URL, e.g. http://user:firstname.lastname@example.org
You can open an SSH tunnel from your network to Usetrace infrastructure. Contact us at email@example.com for details
Setup a VPN. Contact us for details.