Accessing CMS from https://example.com/xibo automatically takes out the xibo part

Get Help
1

I installed xibo 1.8.7 with docker on a vm at address 192.168.1.114, connecting to 192.168.1.114:80 works no problem.

I have a reverse proxy configured on another vm to give out https[dot]example[at]com/xibo but if I access it, it’ll take out the “xibo” and add “login” instead. I end up with https[dot]example[at]com/login and it brings me to :

The requested URL /login was not found on this server.

Apache/2.4.18 (Ubuntu) Server at example[at]com Port 80

If I add the xibo part manually (https[dot]example[at]com/xibo/login) it goes to the CMS until I click somewhere and it goes back to not working becasue it took out the “xibo” part again.

I have a working xibo config that was installed by someone else, it’s version 1.7.6 and it works on https://example.net/xibo, so I know it is possible to do without docker.

Here’s the nginx config (copy pasta from the working config changed to this one) :

  server {
         listen 80;
         server_name example[dotcom;
         return 301 https://$host$request_uri;
     }

    server {
        server_name example[dotcom;

        access_log      /var/log/nginx/example.access.log;
        error_log       /var/log/nginx/example.error.log;

    listen 443 ssl; # managed by Certbot
    managed by Certbot stuff

    location ~ \.php$ {
         include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/run/php/php7.0-fpm.sock;
    }

        location ~ /\. {
        deny all;
        }

        location / {
                proxy_pass              http://192.168.1.15:8080/;
                proxy_set_header        Host                    $host;
                proxy_set_header        X-Real-IP               $remote_addr;
                proxy_set_header        X-Forwarded-For         $proxy_add_x_forwarded_for;
                }

        location /xibo/ {
                proxy_pass              http://192.168.1.114:80/;
                proxy_set_header        Host                    $host;
                proxy_set_header        X-Real-IP               $remote_addr;
                proxy_set_header        X-Forwarded-For         $proxy_add_x_forwarded_for;
                proxy_set_header        X-Forwarded-Proto       $scheme;
                proxy_read_timeout      90;
                }

        location /data {
    try_files $uri $uri/ /index.php?$args;
                }
}

How can I make this work with docker ?

2

In your config.env file, uncomment the CMS_ALIAS line and set it appropriately.

Then down/up the containers.

3

I checked the config.env on the xibo server and the CMS_ALIAS is already uncommented.
Here’s a copy/pasta:

## CMS Configuration

## Please make a copy of this file as config.env, and then
## edit it to suit your environment

## The CMS brings its own MySQL server to store your
## data. 
## On a new installation, we need to create a user account for the CMS to
## connect to that database with. What password should
## that account use? Enter a random password here.
## We recommend using a 16 character random upper/lower case
## and digits.
## You could for example use the random.org password generator
## here: https://www.random.org/passwords/?num=1&len=16&format=plain&rnd=new
##
## IMPORTANT: DO NOT USE SPECIAL CHARACTERS, SPACES etc. Please use only
## alpha-numeric (ie A-Z a-z 0-9) passwords of around 16 characters. The
## random generator linked above will give you something suitable.
##
## If you're upgrading an existing installation, be sure to use the correct
## password for the cms user account in the MySQL database (ie what you had in
## this variable previously).

MYSQL_PASSWORD=nope

## SMTP Server Configuration
## The CMS needs to be able to send email to you
## Please enter credentials for a suitable SMTP server
## Defaults will work for GMail - replacing your GMail username
## and password as appropriate. You will also need to enable access
## for less secure applications on your GMail account for this to
## work. See https://support.google.com/accounts/answer/6010255

## SMTP Server Hostname
CMS_SMTP_SERVER=smtp.gmail.com:587
## SMTP Username
CMS_SMTP_USERNAME=youraccount@gmail.com
## SMTP Password
CMS_SMTP_PASSWORD=yourpassword
## Use a TLS Connection YES/NO
CMS_SMTP_USE_TLS=YES
## Use a STARTTLS Connection YES/NO
CMS_SMTP_USE_STARTTLS=YES
## Rewrite domain (the domain your email will appear to come from)
CMS_SMTP_REWRITE_DOMAIN=gmail.com
## Hostname that we should identify ourself to the remote server as
CMS_SMTP_HOSTNAME=gmail.com
## Can the From line be overridden in the outbound email
## NB GMail will rewrite the From address anyway so it's not important
## for GMail - YES/NO
CMS_SMTP_FROM_LINE_OVERRIDE=YES

## It is sometimes necessary to configure the webserver running inside
## the container to know the DNS name by which you will normally
## access the CMS. For most installations this is unnecessary and can
## be left as default, however, if you know this, it won't hurt to
## set it
CMS_SERVER_NAME=cms.example.org

## Sometimes you want Xibo to run in a sub directory of the webserver
## rather than at the root. If so, specify it here. Comment it out to
## use the web root.
CMS_ALIAS=/xibo


## Xibo comes with a 2GB limit for individual file uploads
## If you require larger files, uncomment the following and adjust as
## required
# CMS_PHP_POST_MAX_SIZE=4G
# CMS_PHP_UPLOAD_MAX_FILESIZE=4G
# CMS_PHP_MAX_EXECUTION_TIME=600

I redid it just to be sure and it gave me these errors :

Recreating xibodocker187_cms-db_1 … done
Recreating xibodocker187_cms-xmr_1 … done
Recreating xibodocker187_cms-web_1 … error

ERROR: for xibodocker187_cms-web_1 Cannot start service cms-web: driver failed programming external connectivity on endpoint xibodocker187_cms-web_1 (c086379dc8a6a4ede6d1ec5476ab119d94943f37310a1b8db55a8e30956136c2): Error starting userland proxy: listen tcp 0.0.0.0:80: listen: address already in use

ERROR: for cms-web Cannot start service cms-web: driver failed programming external connectivity on endpoint xibodocker187_cms-web_1 (c086379dc8a6a4ede6d1ec5476ab119d94943f37310a1b8db55a8e30956136c2): Error starting userland proxy: listen tcp 0.0.0.0:80: listen: address already in use
ERROR: Encountered errors while bringing up the project.

4

The error is telling you that you’re trying to launch Xibo on port 80 and there’s already something there. So either you have two instances running somehow, or you used a different docker-compose file last time

5

I have no idea, I’m pretty sure I only installed it once, I’m just gonna redo the server and see if that was the problem!

6

I remade the server and it does almost the same thing.

Starting xibo_cms-xmr_1 ... done
Starting xibo_cms-db_1  ... done
Starting xibo_cms-web_1 ... done

No error this time, CMS_ALIAS=/xibo

When I go to https://example.com/xibo is still automatically takes out the “xibo” part, but when I login (https://example.com/xibo/login) and it brings me to https://example.com/dashboard/status, if I add the xibo in there it works without a problem until I try to go back to the dashboard then it takes out the xibo again.

8

That is wrong in your reverse proxy config.

You’re proxying /xibo from your reverse proxy to / of the Xibo install. So Xibo sees the incomming request to / and therefore has no knowledge you’re using /xibo in the path. You need to proxy it to /xibo as well!

location /xibo/ {
            proxy_pass              http://192.168.1.114:80/xibo/;
            proxy_set_header        Host                    $host;
            proxy_set_header        X-Real-IP               $remote_addr;
            proxy_set_header        X-Forwarded-For         $proxy_add_x_forwarded_for;
            proxy_set_header        X-Forwarded-Proto       $scheme;
            proxy_read_timeout      90;
}
1 Like