What is the root cause of this with the attachments? Is it because the *.js file is attempting to ‘donwload’ the attachment via configured fqdn?
I was testing DR setup recently and noticed accessing by IP instead of fqdn produces this error as well. For various reasons, imo, it would be beneficial where attachments worked if accessed by IP because a ton of things could go wrong that the fqdn or primary host is not working and dns doesn’t point to the proper/active vm (like invalid certificate). Everything else seems to be working fine accessing by IP via web browswer (not the app).