If you haven’t previously followed it on the server your using, then you can just follow the guide as it is written, you don’t need to do the last steps which deal with upgrading certbot.
If you followed them in the past, then you will need to do those steps once.
thanks for your answer but i was so impatient that i do the second part and it worked
i know i don’t control all what i did about xibo mostly the server part and docker and so and so
perhaps i will do nothing with this magnificient tool but i would want to know something else.
i saw you have installed a server ( xibo.alexharrington.co.uk) but we can’t see it anymore is it down or you hide it ?
what is your advice about the use of xibo in production ? is it a good thing that anybody cant see the login page ?
what about xibo as a white label ?
I only set that up as an example to write the guide. That server doesn’t exist.
With respect, if you’re putting a server out on the internet then you should know how to make reasonable provision to secure it against attack etc. The containers we provide are as locked down as we are reasonably able, and the guide tells you to configure a firewall, but there’s probably other precautions you should be taking.
That is what systems administrators do, and it’s not reasonable for us to specify what other steps you should take as they vary from case to case.
If you don’t have someone with suitable expertise to run servers on the public internet, then think carefully about going down that route.
If you’re using a white label, then you simply apply that to the CMS after the installation following the steps in the guide on the same subject.