CMS Not resolving after following SSL guide

[mike_taov]

To be completed by the original poster:

CMS Version: 4.0.11

Specify the full CMS version you are using, including the revision number.

Issue:

After following the guide here: https://community.xibo.org.uk/t/xibo-cms-with-docker-on-ubuntu-22-04/9392
I’m unable to resolve the server using the FQDN on http or https, but I can get in via local IP so I’m a little confused.

Here is my Apache Default Site conf (I Removed the rewrites from Certbot after noting that it wasn’t working):

Blockquote
<VirtualHost *:80>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request’s Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.
ServerName myddnsname.webhop.me

    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html

    # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
    # error, crit, alert, emerg.
    # It is also possible to configure the loglevel for particular
    # modules, e.g.
    #LogLevel info ssl:warn

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    # For most configuration files from conf-available/, which are
    # enabled or disabled at a global level, it is possible to
    # include a line for only one particular virtual host. For example the
    # following line enables the CGI configuration for this host only
    # after it has been globally disabled with "a2disconf".
    #Include conf-available/serve-cgi-bin.conf

    ProxyPreserveHost On
    RequestHeader set X-Forwarded-Proto expr=%{REQUEST_SCHEME}

    ProxyPass / http://127.0.0.1:8080/
    ProxyPassReverse / http://127.0.0.1:8080/

Here's the dockers 

And my custom-ports.yml
version: “2.1”

services:
cms-db:
image: mysql:8.0
volumes:
- “./shared/db:/var/lib/mysql:Z”
restart: always
environment:
- MYSQL_DATABASE=cms
- MYSQL_USER=cms
- MYSQL_RANDOM_ROOT_PASSWORD=yes
mem_limit: 1g
env_file: config.env
cms-xmr:
image: Package xibo-xmr · GitHub
ports:
- “9505:9505”
restart: always
mem_limit: 256m
env_file: config.env
cms-web:
image: Package xibo-cms · GitHub
volumes:
- “./shared/cms/custom:/var/www/cms/custom:Z”
- “./shared/backup:/var/www/backup:Z”
- “./shared/cms/web/theme/custom:/var/www/cms/web/theme/custom:Z”
- “./shared/cms/library:/var/www/cms/library:Z”
- “./shared/cms/web/userscripts:/var/www/cms/web/userscripts:Z”
- “./shared/cms/ca-certs:/var/www/cms/ca-certs:Z”
restart: always
environment:
- MYSQL_HOST=cms-db
- XMR_HOST=cms-xmr
- CMS_USE_MEMCACHED=true
- MEMCACHED_HOST=cms-memcached
env_file: config.env
ports:
- “127.0.0.1:8080:80”
mem_limit: 1g
cms-memcached:
image: memcached:alpine
command: memcached -m 15
restart: always
mem_limit: 100M
cms-quickchart:
image: ianw/quickchart
restart: always

[mike_taov]

If I forward 443 to the server, then it works, however we need 443 for another machine, are there any workarounds?

[Jon_Knowles]

I would use nginx setup as a reverse proxy and use the multiple upstream to handle multiple internal servers that need to run on a single external IP.

That way Nginx does all the ssl/tls offloading, makes your certificate renewals much easier and allows your applications to use their resources more efficiently.

Are you running xibo + whatever else on an office network or home network with a single external IP?

I use nginx for this as well as load balancing for years and it works very well.

NGINX Reverse Proxy | NGINX Documentation

[mike_taov]

Yes, Just hosting it from our HQ for some digital signage on our tills and eventually our TVS, I do plan on having a dedicated IP for it and an actual server as well.