We have a local connection option which allows you to test sites behind your firewall, or to access web pages that are saved locally on your machine. In just a few seconds, you can establish a connection which allows you to do live testing or screenshots against any of the internal sites you have access to.
To run a Local Connection, launch the dialog in the app:
You can find more information about the local connections here:
- Blog article introducing our Chrome extension for local connection
- Using Node.js module on the command line
- Using Java jar on the command line
Alternatively, you can allow access to your internal dev or test site for CrossBrowserTesting.com’s browsers by placing a firewall rule allowing http traffic from 184.108.40.206 to access a particular internal web site. Typically you will select a port on the outside interface of your firewall, put a ‘deny all’ rule on it with an exception that you will allow traffic from 220.127.116.11, then forward this traffic to the particular web server.
Internal Web Site Option
An encrypted tunnel is created between your machine and CrossBrowserTesting.com. Our remote browsers are directed to send their traffic to your local proxy. All URLs are resolved locally via your proxy, so URLs with your internal DNS names will work just fine. The proxy will receive ALL traffic, such that if you test http://google.com, even this request will route through your tunnel and will be handled via your proxy server.
Requirements / limitations:
- Java Applet: Outbound ssh requests to port 22 on CrossBrowserTesting.com must be allowed via your firewall.
- All other tunnel types: Outbound ssh requests to port 443, SSL on CrossBrowserTesting.com must be allowed via your firewall.
Note: Try to use your full IP address.
For localhost or 127.0.0.1 connection use the word local instead like this
To test a web server inside your firewall, simply enter the same URL you would use from your local browser.