So, this is 2020. Very soon browsers are going to entirely block http and self signed certificates. So learning how to do this is important if you want to run new toys.
You can argue if that is a good thing or not, but it will not change it happening.
The schirrms page gives a good basic introduction but SME has more tools built in and available now. It is less trouble to set up if you take time to read and understand.
Search the interwebs for 'apache reverse proxy' and you will get thousands of guides on the basics. Then it is just a case of implementation on SME.
A reverse proxy (not a cache proxy) separates the 'outside' world from the 'inside' world.
A reverse proxy takes say a https connection and sends it to a http server transparently. Our Rocket.Chat at chat.reetspetit.info does exactly this. Rocket actually runs on
http://127.0.0.1:3000 (because of nodejs) but you get a connection using https.
So you could have a website running http only on a server somewhere on you lan. Your SME is the gateway. You can set up a reverse proxy on SME to send the requests to the internal server.
In your cases the 'internal' server - geneweb or grafana sit on the SAME machine as the apache https server. So instead of a reverse proxy to an IP somewhere on your lan you reverse proxy to say 127.0.0.1:12345
Externally everyone can access your site using https - the proxy passes it to the http server, and then sends any response back as https.
Ma compagne travaillant dans une grande société française ne peux même pas acceder à SME sans que ce soit une page http, les https : interdites !
My partner working in a large French company cannot even access SME without it being an http page, https: prohibited!
I would imagine that is so they can monitor all the web traffic traffic of their staff. It is not a good reason for you to use http on your server.......
Comment rendre le système lisible par tous ?
How to make the system readable by all?
Use a reverse proxy.
Have either of you actually tried to search the wiki for reverse proxy??? Eg
https://wiki.contribs.org/Seafiledb domains setprop db domains setprop seafile.itx.pialasse.com Nameservers local ProxyPassTarget http://127.0.0.1:8000/ TemplatePath ProxyPassVirtualHosts
signal-event domain-modify seafile.itx.pialasse.com Nameservers local ProxyPassTarget http://127.0.0.1:8000/ TemplatePath ProxyPassVirtualHosts
signal-event domain-modify seafile.itx.pialasse.com
This will use the existing basic proxy template and reverse from
https://seafile.itx.pialasse.com ->
http://127.0.0.1:8000/There is some other information on the wiki but I will let you find it yourselves.