IIS Webserver + Xibo 1.8.1

Hi there,

i’ve installed Xibo in a Docker on Windows 10.

Now I need a webserver to host some ASP.net Websites. If I install IIS, Xibo can’t be reached longer over http://localhost/ because the default IIS Website is then located on localhost.

Is it possible to run both xibo and IIS or is there a possibility to use the webserver which is used and created by Xibo?


Please help me.
The problem still exists

Place one of the servers on a different port

Thank you for your answer.

I moved the default IIS site to http port 591, but xibo can’t be reached under localhost when IIS is installed.

Can I configure xibo as a application in IIS? But I don’t know where the docker is located. Xibo is located in C:\users

Likely somewhere in it’s configuration IIS is still listening on port 80. Once port 80 is free, Xibo can run on it again.

Alternatively, you can use the custom ports docker-compose file to move Xibo on to a different port, and leave port 80 for IIS.

All I have to do is to change the “80” to 591 for example, save the file without .template and run the docker with “docker-compose -f cms_remote-mysql.yml up -d”? Is that right,because it doesen’t work.

No. You need to follow the instructions in the manual for running the CMS on a custom port. That very definintely doesn’t involve the remote-mysql.yml file :slight_smile:


Under “Using different ports”.

Once you have the ports file created, and edited to your requirements, you would then run

docker-compose down
docker-compose -f cms_custom-ports.yml up -d

Thank you.

I already did that. It was a typing error I mean the cms_custom-ports.yml but it doesen’t work.

After “docker-compose -f cms_custom-ports.yml up -d” xibo is not longer available.

I wrote “65501:591” instead of “65501:80” into the cms_custom-ports.yml file

Correct. That won’t work :slight_smile:

If you want it on port 591, then it needs to be