"Service is Starting" Splash screen only when accessing by IP.

[DCIM_Support]

Here's an oddball question. Running into an issue after an 8.1 upgrade where accessing the DCO web gui by IP brings up the "grab a cup of coffee" splash screen, but works perfectly fine when accessing by hostname. Tried multiple browsers, don't believe it's a caching issue. No issue with desktop client.

Small install - ~30 racks, 4 cores, 16GB RAM, 100GB storage.

Any thoughts? I can grab logs tomorrow during a remote session if needed.

(CID:118000787)

[DCIM_Support]

Hi Jeff,

Not sure if it might be DNS related - are you using http or https to connect?

It would be great to have the server logs, could you please collect and share them with me, thanks.

Kind regards

(CID:118001031)

[DCIM_Support]

Tried both. I'll do a webex with the customer this afternoon and will grab the server logs and shoot them over to you. Thanks Jef.

I'll also double check that cluster services aren't turned on (single server install), I'll check the DNS/Bind settings, and restart apache.

(CID:118001238)

[DCIM_Support]

did you find a resolution to this?  I'm having a similar issue after an 8.1.0 update.  Web client says service starting, but thick client works fine.  only 2 unique things about their install I can think of is they have EE and Cooling Optimize.

(CID:118003629)

[DCIM_Support]

I found a work/around resolution to my issue, it seems to be related to the HTTP–>HTTPS redirect.  Even though redirect was enabled in webmin-->operations–>setup,  when I try to browse to the server or launch the thick client on port 80, using IP or hostname, I get the service is starting splash screen. If I specify HTTPS in the url, it works fine.  

This worked fine in 8.0.2, so i assume something was changed in 8.1.0 and/or the packages used in this version that affects this.

It's also possible that this is an expected behavior with the redirect enabled, but service is starting splash screen is definitely confusing...

(CID:118004056)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.