Updated XAMPP - Client Found Response Content Type of 'TEXT/HTML'

Get Help
1

Hello all,

I’m running XIBO 1.7.2 on a small web server running XAMPP. I recently updated XAMPP.

Since updating XAMPP, clients are receiving the following error on the player options screen:
Client found response content type of ‘text/html; charset=UTF-8’, but expected ‘text/xml’.
The request failed with an empty response.

Searching brought me to un-commenting the following line in my PHP file;
always_populate_raw_post_data = -1

After restarting the web server I’m still running in to the same error. Even my localhost client is failing.

Any ideas and help would be greatly appreciated.

2

Can you access the CMS itself in the browser?
Does it show any errors on the Report Fault page / Log page?

Did the XAMPP upgrade also upgraded your PHP to PHP7 by any chance?

If it did, then you have two options.

Upgrade Xibo to 1.8 series, that supports php 7
Downgrade the PHP version to make it work with 1.7 Xibo series

That was indeed a solution to this error I believe, although if you have already done it, then something else must be causing it.

As a side note 1.7.2 was released in March 2015, it might be a good idea to upgrade it, at least to the newest version in 1.7 series.

3

Hey Peter,

Thanks for your reply!

I decided to just rebuild my Xibo using the docker install. New tech for me, but its working great now. Just need to update a few workstations at off site locations.

On my XAMPP install I was able to access the CMS. I don’t recall log or report fault pages unfortunately.
The XAMPP upgrade put me at PHP 5.6.3~. I tried updating XIBO to 1.8 - It was getting hung up on updating stat tables but eventually finished. Once completed I was left with the same error. "Client Found Response Content Type of ‘TEXT/HTML’.

Thank you again.

1 Like
4

Interesting, perhaps it was something else rather than the PHP version then, it is not easy to say without information about the environment and logs.

With that being said, I’m glad that you decided to go with docker, it should be more reliable and easy to maintain.