stargazer1sd

Thanks for the clarification. Changing conf_global.php did the trick. The forum seems to be operating normally now. Hopefully, this will continue as the actual users start exercising it. 

@Randy Calvert @Nathan Explosion Thank you so much for the info!

5 minutes ago, Randy Calvert said:

Also fyi… this makes the assumption your hosting provider supports https for your site. IPB can’t install/configure SSL on your server. It only can change the links that the software generates from http to https.  

Once you change this value, you may need to clear your site cache from the ACP in the support section. 

Thank you! This host will support SSL cert(s). We turned off http to https redirect earlier, and it helped some. But, I think a lot of our users have an https shortcut. 

Right now, it seems like the right solution is to edit the conf_global file, and reactivate the HTTPS redirection. That should keep Chrome happy and uncomplaining. 

And thank you for pointing out the cache clear requirement. 

1 hour ago, Nathan Explosion said:

Edit your conf_global.php file and change the http to https for your URL there.

Thanks! I'll try that. 

I think I found the root cause. Chrome wants some of the pages' JavaScript code delivered via https. It refuses to load that code, so a bunch of stuff on the page won't work. 

Is there any way to get the board to reference this code via HTTPS?

21 hours ago, Jim M said:

Did you disable third party applications and plugins as well?

We aren't currently using any of either. 

Now, we are self-hosted, and I didn't realize there was a different section of the forum for us. Should this be moved to that section?

I disabled the ads, and the problem is still with us. Tried changing to default theme and still no joy. 

We have been having problems getting the Chrome browser to function with our forum. Firefix and Safari seem to work fine. Proximate cause is that the page's Javascript isn't getting called for click events. The forum is hosted on its own server and is running the current version. We are NOT using a content delivery network. This seems to have mysteriously appeared with a Chrome update. 

We were hoping that updating to the current version would rectify the problem but it hasn't. 

Any hints/guidance appreciated.