Forums
(@sojan16)
1 year, 8 months ago
It turns out that the old site IP was proxying to the new one, so the add-in was not aware of the originating IP. The issue was DNS as usual
