Since the 2023.3 upgrade my reports have lost the correct FQDN for links and now only link to the internal webserver address

fop

Hi folks,

I'm still finding little niggles after I did the long-delayed upgrade to the latest version (as it was then) back in July. The latest is that my report scheduler no longer lists the external URL for reports to link to, it only shows the netbios names of the webservers. I fixed this years ago by changing the 'Websites' table in the DB to include the 'ExternalURL' field. The Solarwinds documentation on this is a mess and doesn't help people with one primary and 2 AWS, all 3 nodes have the same ExternalURL.

Has anyone found a definitive answer to this? I'm sure we're not the only people with a pair of AWS' behind an Application Gateway in Azure.

Cheers

Adrian

fop

For example, this document - Configure website URL for Alerts and Reports in Orion (solarwinds.com) - says to edit the FQDN field and make sure it's set to what's in the ServerName field; it's been a while but I'm sure I tried setting that to the actual external URL and the world ended. Also that document says to have the AWS you want to use for reports as 'primary' and the others as 'additional'. Our primary poller shouldn't be using its webserver for anything as that's what the pair of AWS' are for, but I can remember the world ending when I changed the order of primary and additional too.

Of course, this is before we discovered why our AWS weren't working post upgrade so things may be different now.