My installation was working fine on an IIS installation. I was not getting ticker modules on the displays, so I entered my network’s proxy information in the CMS GUI settings. The next time I tried to use the CMS, it said connection refused.
I have tried reverting the proxy settings to nothing through phpmyadmin, and have restarted the IIS instance, as well as the server. And I have toggled the firewall on and off.
Edit: Now it is saying “took too long to respond” instead of “connection refused.”
If you’re directly modifying the database, then those changes won’t be applied.
You also need to clear the “cache” directory in the CMS library. Delete any files in that cache directory, and then it should load the settings from the database.
edit3: Ok I’m dumb. I checked “Force HTTPS” in the gui. That was what caused the connection refused. Clearing cache does not commit changes thru phpmyadmin though.
Had to add a binding in IIS for https. Then was able to connect.
Open IIS
Default web site > edit bindings
Add…
HTTPS, use localhost cert
Then connect to xibo normally in browser.
Uncheck the Force HTTPS option in Settings > Network
The logs are extremely verbose, even though I have them set to error right now. Is there somewhere besides the cms gui I should get the logs from? I filtered for “Error” level logs since there were 150 pages of logs even after truncating and just hitting “Preview layout” after.
The CMS gui is the best place to look at the logs. I’m not sure where else you’d want to look at them?
150 pages from one click sounds very unlikely. Perhaps there’s something more serious underlying this. As it’s a custom install we’ll do what we can to help out, but it makes it significantly harder for us to assist.