Failed to retrieve Certificate from wasabisys

[apbirch67]

hello, before i raise the ticket with Veeam, out of the blue this week two of my veeam servers on my network can't connect to wasabisys.com. I'm pretty sure it is a cert issue on their side but I wanted to see if anyone else is seeing issues.

I do have two other object storage providers set up and working fine. Also, I have a handful of customers that are working fine. I can connect to my wasabi buckets using FileZilla Pro without any issues from the same network.

Thanks

[Gostev]

Can't connect persistently, or just sporadic issues?

[apbirch67]

Now it is persistently, had been working fine for over a year.

I did receive a note back from the vendor that they changed some IP's last weekend. So I'm following up with that thought and will post back if I can get it sorted with them.

[apbirch67]

More digging, I have isolated the traffic from wasabi in our firewall and we are seeing a good amount of tcpip traffic coming back from them without a port number. This triggers an autoblock on our firewall so it never gets to our rules. Still working with their support on this new information.

[avs262]

Did you ever find a solution to this? I'm seeing the same issue with s3.us-east-1.wasabisys.com starting at about the same date. s3.us-west-1.wasabisys.com is fine.

[veremin]

Have you reached Veeam or Wasabi support to investigate this issue deeper? Thanks!

[avs262]

Yes, and they referenced this thread.

[Gostev]

Referenced this thread saying what? Just curious as there's really not a whole lot of useful information here in this topic

[avs262]

Veeam Support - Case # 04678587

[Gostev]

Ah, actually based on this last status update above you need to work with Wasabi support instead:

More digging, I have isolated the traffic from wasabi in our firewall and we are seeing a good amount of tcpip traffic coming back from them without a port number. This triggers an autoblock on our firewall so it never gets to our rules. Still working with their support on this new information.

Seems like Wasabi is flooding network equipment with invalid TCP/IP traffic, so nothing to deal with Veeam.