Rescue Live Guide System Requirements
Rescue Live Guide uses a cloud-based browser solution. Therefore, system requirements concern the use of supported browsers and the accessibility or required network resources both on agent and customer side.
Rescue Live Guide Browser Requirements
Rescue Live Guide supports the following browsers.
- Desktop
-
- Supported Browsers for Agents
- The latest version of Chrome, Firefox, or Safari.
- Supported Browsers for Customers
- The latest version of Chrome, Firefox, Safari, Edge, or Internet Explorer 11.
- Android
- The latest version of Chrome.
- iOS
- The latest version of Chrome or Safari.
Rescue Live Guide Network Requirements
From both the support agent's and the customer's network, the following HTTPS web resources need to be accessible.
- .logmeinrescue.com
- .support.me
- .gotoassist.com
- Amazon Web Services (AWS) cloud platform
Solution for Resolving AWS Blocking
If the traffic from AWS to your website is blocked, we offer two ways for you to identify requests from Live Guide and make an exception for those requests to reach your website: Add AWS IP addresses to an allow list, or Set Web Application Firewall exception. For detailed information, see the corresponding sub-section below.
Allow AWS IP addresses
Allow the AWS IP addresses Rescue Live Guide uses. You can find the list of the IP addresses to be added to the allow list for the 6 data center locations of Rescue Live Guide below:
- US East (N. Virginia)
-
- 52.206.65.137
- 34.195.14.141
- 52.201.48.230
- 3.231.80.200
- 52.73.125.65
- 54.156.162.0
- 3.89.198.17
- 34.207.1.210
- 3.82.67.131
- 3.88.120.243
- 52.5.153.205
- 50.17.169.140
- US West (Oregon)
-
- 44.233.101.96
- 54.184.245.157
- 52.12.111.124
- 52.12.26.208
- 54.202.20.126
- 54.189.27.29
- 54.203.245.19
- 54.190.190.144
- 44.227.79.161
- 44.232.63.204
- 50.19.237.77
- 18.207.43.51
- 54.159.24.105
- 3.212.155.249
- 3.220.204.180
- 3.213.135.161
- 184.72.239.64
- 107.21.107.106
- 54.88.22.187
- 52.37.149.231
- 54.191.200.57
- 52.37.160.35
- Europe (Frankfurt)
-
- 35.156.165.171
- 3.126.95.195
- 3.127.56.214
- 3.126.226.181
- 18.184.170.120
- 3.123.223.106
- 35.157.140.201
- 3.121.221.152
- 3.126.48.183
- 3.126.54.4
- 52.29.212.248
- 52.58.144.225
- Asia Pacific (Singapore)
-
- 52.220.101.222
- 54.251.175.114
- 18.138.199.69
- 52.77.154.189
- 3.0.126.84
- 52.220.43.164
- 52.74.146.151
- 13.228.122.251
- 13.228.144.184
- 52.76.106.242
- 52.220.104.96
- 52.220.112.188
- Asia Pacific (Tokyo)
-
- 52.197.155.132
- 52.196.65.159
- 54.178.247.237
- 18.178.171.10
- 18.181.128.24
- 54.199.175.190
- 54.95.41.237
- 18.177.189.216
- 3.112.145.192
- 18.177.128.210
- 52.196.198.8
- Asia Pacific (Mumbai)
-
- 3.7.182.116
- 3.7.21.132
- 3.6.67.171
- 3.7.232.95
- 13.232.8.66
- 3.7.22.225
- 3.7.227.195
- 3.7.189.59
- 3.7.236.26
- 15.206.85.136
- 15.206.162.68
- 35.154.239.181
Set Web Application Firewall exception
The specific configuration steps are different on the various web application firewall tools but on a high level it should involve similar steps to the below example:
- To allow web requests based on strings that appear in the request itself, create a condition that you can then filter for.
- When choosing the part of the request to filter on, make sure to select Header and add the selected secret you specified for Live Guide.
- Create a rule with the string match condition you set up in the previous steps to allow the requests that match this condition.