Orion web https redirect

edit the primary servername to be what it should be for end users to be able to reach the server. We have to do that every time we do an upgrade. If you use HTTPS you will want to be sure that the port info is accurate as well.

jkcy

So the primary record fields (ServerName, Port and SSLEnabled) will look like the 'additional' record, correct?

sean.martinez

UPDATE dbo.Websites SET ServerName=’Server01.domain.com’, Port=’443’ SSLEnabled=1 WHERE Type=’primary’

A restart of the Solarwinds Services are needed in order for the alerts to take effect.

jkcy

Thanks for the help!

m_roberts

Does this work in a situation where the report URL should address to an Additional Web Server? I want my reports to go to an FQDN, which is that of one of the AWS, as this is the server that is used for primary access to the Orion web interface. The primary server has had its web presentation disabled, so it can concentrate on more important matters, such as data collection, alerting etc.

sean.martinez

Yes, this will work for the Main or Additional or Proxy Server. This field is what will be the generated link for Alerts and reports and the Orion Web Console link under the Start Menu on all Server, so as long as it reports to one Orion Web Console, it's all good.

ecklerwr1

Why has this never been fixed? I thought this has been going for years now?

ecklerwr1

I've also read that this breaks the installer from running correctly and also that it will reset after patches or updates??? I had hoped this was fixed but this link make me think not. Re: HTTP vs HTTPS frustration

jkcy

Not only that. The SW Support Team had to re-run the Configuration Wizard on my box to fix another issue. After that I found a new entry is added. I had to modify it again before I can access the web console.