• Hi all,
    Apologies if this is not the correct sub to post this, please let me know and I'll remove it.

    We use Unitrends backup. Google cloud storage was set up as one of the 'Backup copy targets'. This was working normally for a few years. Then it stopped working. I was suddenly not able to mount the cloud backup target. I thought maybe it was a google access key/secret issue however when I tried to add a new cloud target it failed, I got the error - Cloud configuration error:...Structure needs cleaning...could not write auth for storage.I thought perhaps the Unitrends disk was corrupted. I called the Unitrends support several times and we tested building a new server and using different storage but got the same error message. Also, the same error if I tried adding AWS as the cloud storage device. They believe something has changed on the pfSense firewall or on the network. To the best of my knowledge I have not changed anything recently.

    In pfSense I have added aliases for the Unitrends servers and have a LAN rule for the Unitrends server, Otherwise I haven't touched it in two years. Has something changed recently with Google cloud storage? Do I need to add a rule/alias for this? Any help or advice would be greatly appreciated.


  • @mcdonaghc said in Unitrends CLoud storage issue:

    In pfSense I have added aliases for the Unitrends servers and have a LAN rule for the Unitrends server, Otherwise I haven't touched it in two years. Has something changed recently with Google cloud storage? Do I need to add a rule/alias for this? Any help or advice would be greatly appreciated.

    The very first thing to check is your firewall log to see if any traffic to or from the Unitrends Cloud servers is being blocked. You will need to know the IP address (or addresses) to look for.

    Second thing to check is whether or not you have the correct firewall rules in place. Have you followed the instructions from this Unitrends Support document?

    https://support.unitrends.com/UnitrendsBackup/s/article/000003983

    And then this one: https://support.unitrends.com/UnitrendsBackup/s/article/000006888.

    Why did you create the Aliases you mentioned? Did you do this recently, as a result of this current problem, or are they from a time pre-dating the current issue? Do the aliases, as defined, have the correct IP address information in them? A common problem with cloud services is they use a number of data centers around the world and connect them to load balancers. This means the IP address can sometimes change unexpectedly. Don't know if this is the case for Unitrends, but it could be. Are your aliases configured as FQDN aliases?

    EDIT: Just saw this important footnote on their support site --

    NOTES: Additional relevant information such as specific exceptions, warnings, etc. These URLs are hosted behind active load balancers in AWS and Unitrends Cloud datacetners. The list of IPs on each URL are dynamic, and change frequently, so we are unable to publish a specific listing. Thus agents and browsers used to access these services will either require unfiltered port 443 access to all external IPs,or, use of a firewall system that supports URL-based filtering instead of port/ip filtering.