Agisoft Viewer Share to Client Not Working

[claytonb8298]

Hello,  I have a project that I am sharing via Agisoft Cloud viewer portal to a client and when the click on the link the model will load in the background, but in the foreground is a blue/green/white spinning circle (Agisoft colors) and they aren't able to operate within the model, i.e. use mouse to pan, orbit and zoom.  The circle just spins and spins and spins.

I am not having this problem and from what I can tell, other clients on the same team but different companies aren't having problems.

Has anyone had any experience fixing this?

See attachment for example of spinning.

[Agisoft Cloud Team]

Hello,

First, I’ve moved this topic from the Agisoft Viewer category to the Agisoft Cloud category, as it is more relevant to the issue described.

The spinner is normally displayed while the scene is loading. In particular, this can occur when a DEM layer is enabled/disabled or its position in the workspace changes, since the terrain needs to be rebuilt based on the currently visible layers and their respective positions.

However, the behavior you describe is not expected, and it may indicate a bug on our side.

To investigate this further, could you please share the project with our support team? You can do this by enabling access via link and sending the sharable link to support@agisoft.com.

Once we identify the cause of the issue, we will provide an update both via email and here on the forum so that others can benefit from the findings as well.

[Agisoft Cloud Team]

Hello,

We identified that the issue is caused by the network configuration. Specifically, access to the global terrain and base map services hosted on AWS is being blocked.

For your reference, and for anyone who may encounter a similar situation, please ensure that the following endpoints and services are allowed in your network configuration.

Regarding the system/web application itself, we use the following IP addresses:

• 75.2.27.220
• 99.83.165.180

However, allowing only these IP addresses is not sufficient for full functionality. The application relies on AWS S3 Object Storage for data storage and delivery, utilizing S3 Transfer Acceleration.

Obtaining a fixed list of IP addresses for this service is challenging because it operates on AWS's global network and edge locations. As a result, the S3 bucket hostname may resolve to different IP addresses depending on the client's geographic location and network routing. AWS does not provide a dedicated or static set of IP addresses for a specific S3 bucket or Transfer Acceleration endpoint.

The most comprehensive list of AWS IP ranges can be downloaded using:

Code: [Select]

curl -O https://ip-ranges.amazonaws.com/ip-ranges.json
You can then filter the global AWS address ranges with:

Code: [Select]

jq '.prefixes[] | select(.region=="GLOBAL") | select(.service=="AMAZON")' < ip-ranges.json
Please note that even after filtering, the resulting list will be quite large and may change periodically as AWS updates its infrastructure.

The preferred approach is to configure your firewall to allow traffic based on FQDNs/hostnames rather than individual IP addresses, provided your firewall supports this functionality.

Additionally, access to the AWS S3 address pool used in the eu-west-1 region may be required. These addresses can be filtered with:

Code: [Select]

jq '.prefixes[] | select(.region=="eu-west-1") | select(.service=="S3")' < ip-ranges.json
Configuring access by hostname/FQDN remains the recommended solution, as it avoids ongoing maintenance associated with changing AWS IP ranges.

Please let us know if you need any additional information or assistance with the configuration.