Err404

start

err404@undisclosed.example.com (err404 ) — Wed, 22 Apr 2026 10:25:36 +0000

Files server

The purpose of this training is to facilitate the setup, management, and maintenance of a self-hosted personal website and related services.
Required equipment

Hardware requirements

A USB key to copy Proxmox ve install https://enterprise.proxmox.com/iso/ (if the Proxmox way is chosen)
A computer connected to the Internet that will be dedicated to hosting services, otherwise use a hosting service

Optional services

authoritative domain name server

In my case, I chose to have an authoritative domain name server, but this is not mandatory.

SNI reverse proxy

The SNI reverse proxy is only necessary if you want to have several virtual machines (or containers) sharing the same public IPv4 address.

As can be seen in the diagram, IPv6 is easier to configure than when you only have one public IPv4 address.

Installations

I recommend installing a hypervisor (Proxmox) to host the virtual machines or containers for the website and associated services. It is possible to use a hypervisor other than Proxmox, such as virt-manager, VirtualBox, etc.
In any case, it is preferable to configure the network in bridge mode to avoid having to manage NAT redirection.
Proxmox uses bridges by default, which suits our needs.

Proxmox

Copy the Proxmox ISO to the USB key and boot the computer from it.
Follow the installation steps: xfs, root:30GB.
Proxmox configuration.
Add the user userhttps://your_server_proxmox:8006/# v1:0:18:4:::::::14
Give them admin rights: https://your_server_proxmox:8006/#v1:0:18:4:::::::6
Edit /etc/ssh/sshd_config: permitrootlogin no

Yunohost

Yunohost can be installed in two ways in Proxmox: as a virtual machine or as a container. This will depend on your process isolation requirements.

I recommend installing Yunohost as a container, but if you want to install it as a virtual machine, instructions are available here: Yunohost as a virtual machine

Yunohost installation (in container)

Yunohost is installed in an existing container:

Yunohost is based on Debian, so I install a Debian container:

(documentation: https://pve.proxmox.com/wiki/Linux_Container#pct_container_images)
(documentation: https://doc.yunohost.org/en/admin/get_started/install_on/on_top_of_debian)

Here are some commands to run as root in the Proxmox terminal to add the container images:

pveam update

(updates the list of available container images)

pveam available --section system | grep debian

(displays the list of Debian containers only)

pveam download local debian-12-standard_12.7-1_amd64.tar.zst

(downloads the latest available Debian image)

When the download is complete, you can create a container from this image. 20 GB of disk space should be sufficient.
Start the container…
Once in the container as root, retrieve the yunohost installation script and execute it:

cd /root
apt update
wget install.yunohost.org -O install.yunohost.sh
chmod +x install.yunohost.sh
/root/install.yunohost.sh

Once the basic installation is complete, simply go to the web browser to continue. Or type ‘yunohost tools postinstall’ in the command line.

Get a domain name

either with yunohost
or from a registrar

Once the domain name is registered, you just need to generate the certificate on the Yunohost/admin side.

Authoritative domain name server (optional)

if you want to have subdomains and manage them yourself (which will avoid having to go through the registrar for each change).
you must then declare your main domain name as SOA, i.e. set up and declare an authoritative domain name server.
For example, with nsd (which I chose) or knot (which I have not yet tested).

Adding an application

Choose from:

dokuwiki nextcloud calibre galene jirafeau lufi ... etc.

It is possible to have several containers (or virtual machines), each with its own Yunohost, rather than having all the applications in the same Yunohost virtual machine.
This will mainly depend on the use, and if you choose to have several machines (virtual or not), you will need to set up a SNI reverse proxy (because you will probably only have one public IPv4 address and will need to share it between the machines; with IPv6, this kind of problem does not arise).

IPv4 only: Opening ports (and NAT redirects)

Identify the ports to be opened.
Open them on the Internet box side and specify the redirect.
If you have set up an SNI proxy server, you will need to redirect ports 80 and 443 to the SNI proxy server.

Keep in mind that NAT issues do not exist in ipv6 (unless you have CGNAT, but in that case I recommend changing your Internet service provider).
In ipv6, the machine is directly connected to the Internet, with all ports exposed on the public IP (which starts with 2).

Backups (very important)

Yunohost is capable of backing up applications, but it does not back up itself. That's why I use Yunohost in a virtual machine (or container) and have Proxmox perform the backup.
However, a backup should not remain on the same hard drive as its source and should be stored in a different geographical location.

In our case, using a second hard drive would already be a good solution.

Read the logs (important)

Problems encountered during self-hosting

Some ISPs do not route properly to the IP ranges of other ISPs.
The public IP may change without notice, in which case you will need to update the DNS entries and regenerate the certificates.
It may also happen that the box does not deliver a public IPv6 address but only a locally unique IPv6 address. In this case, you will need to force a public IPv6 address.
Some ISPs do not give IPv6 addresses to their customers, or only in certain areas.
In general, you only have one public IPv4 address, so if you want to host multiple services that require the same ports, you will need to set up a SNI reverse proxy.

start

err404@undisclosed.example.com (err404 ) — Sun, 19 Apr 2026 09:38:05 +0000

NextCloud

Nextcloud is free software for file hosting and a collaboration platform. Originally accessible via WebDAV, any web browser, or specialized clients, its open architecture has allowed its functionality to expand since its inception. https://fr.wikipedia.org/wiki/Nextcloud
* I use Nextcloud to synchronize (or rather copy) photos and videos from my smartphone to the server.
* I also use it to share folders publicly, with read and write permissions management (and you can easily generate a QR code to grant access).

OnlyOffice in NextCloud

If you want to obtain the secret key to use OnlyOffice in Nextcloud, simply connect to the Yunohost container via SSH and run the command “documentserver-jwt-status.sh”.
The key obtained must be copied into the OnlyOffice server parameter field (in the Nextcloud administration interface).

Sometimes (too often) Onlyoffice stops working with NextCloud. I don't really understand why, and I haven't found a reliable solution to keep it running smoothly.

Isolation in a container

I recommend you to have a Yunohost container apart for Nextcloud and Onlyoffice, these are two large packages, with a lot of dependencies, and it's easier to maintain with less risk of conflict if these two packages are installed apart from the other Yunohost packages on your server.

basic.less - old revision restored (2025/08/31 08:55)

err404@undisclosed.example.com (err404 ) — Fri, 17 Apr 2026 07:01:15 +0000

/**
* This file provides the most basic styles.
*
* If you integrate DokuWiki into another project, you might either
* want to integrate this file into the other project as well, or use
* the other project's basic CSS for DokuWiki instead of this one.
*
* @author Anika Henke anika@selfthinker.org
*/

::-moz-selection {

  background: var(--selection_background, #275c9c); 
  color: var(--selection_color, white);

}

::selection {

  background: var(--selection_background, #275c9c); 
  color: var(--selection_color, white);

}

html {

  overflow-x: auto;
  overflow-y: scroll;

}
html,
body {

  color: var(--text, #333);
  background: var(--background_site, #fbfaf9) url(images/page-gradient.png) top left repeat-x;
  margin: 0;
  padding: 0;

}
body {

  font: normal 87.5%/1.4 Arial, sans-serif;
  /* default font size: 100% => 16px; 93.75% => 15px; 87.5% => 14px; 81.25% => 13px; 75% => 12px */
  -webkit-text-size-adjust: 100%;

}

/* scrollbars */

/* The emerging W3C standard

 that is currently Firefox-only */

* {

  scrollbar-color: var(--scrollbar_thumb) var(--scrollbar_track);

}

/* Works on Chrome/Edge/Safari */

::-webkit-scrollbar {

  background: var(--scrollbar_track);
  width: 12px;
  height: 12px;

}

::-webkit-scrollbar-thumb {

  background: var(--scrollbar_thumb);

}

/* config manager */

#configmanager fieldset{
color: var(–text, #000);
background-color: var(–background, #fff);
}

#configmanager td.label span.outkey {

font-size: 85%;
  background-color: var(--background, #fff);

}

#configmanager tr .input,
#configmanager tr input,
#configmanager tr textarea,
#configmanager tr select {

  background-color: var(--background, #fff);
  border: 1px solid var(--border,#333);
  color: var(--text,#000);

}

#configmanager tr.default .input,
#configmanager tr.default input,
#configmanager tr.default textarea,
#configmanager tr.default select,
#configmanager .selectiondefault {
background-color: var(–background_site, #fff);
border: 1px solid var(–border,#333);
color: var(–text,#000);
}

#extensionmanager ul.tabs li.active a {

  background-color: var(--background_alt, #eee);
  color: var(--text, #333);
  border-bottom: none;

}

#extensionmanager .panelHeader {
background-color: var(–background_alt, #eee);
}

#extensionlist ul.extensionList li {

  color: var(--text, #000);
  background-color: var(--background, #fff);

}

#extensionlist .legend div.popularity {
background-color: var(–background, #fff);
border: 1px solid var(–text_alt, #999)
}

#extensionlist .legend div.popularity div {

  background-color: var(--pre_text, #333);

}
/* headers */

caption,
figcaption,
summary,
legend {

  padding: 0;
  margin: 0 0 .35em;
  line-height: 1.2;

}
h1,
h2,
h3,
h4,
h5,
h6 {

  font-weight: bold;
  padding: 0;
  line-height: 1.3;
  clear: left; /* ideally 'both', but problems with toc */

}
[dir=rtl] h1,
[dir=rtl] h2,
[dir=rtl] h3,
[dir=rtl] h4,
[dir=rtl] h5,
[dir=rtl] h6 {

  clear: right;

}

h1 {

  font-size: 2em;
  margin: 0 0 0.444em;
border-bottom: 1px solid var(--border, #333);

}
h2 {

  font-size: 1.5em;
  margin: 1.7em 0 0.666em;
  border-bottom: 1px solid var(--border, #333);

}
h3 {

  font-size: 1.125em;
  margin: 1em 0 0.3em;

}
h4 {

  font-size: 1em;
  margin: 1em 0 0.3em;

}
h5 {

  font-size: .875em;
  margin: 1em 0 0.3em;

}
h6 {

  font-size: .75em;
  margin: 1em 0 0.3em;

}
/* bottom margin = 1 / font-size */

/* basic margins and paddings */

p,
ul,
ol,
dl,
pre,
table,
hr,
blockquote,
figure,
details,
fieldset,
address {

  margin: 0 0 0.6em 0;
  padding: 0;

}

div,
video,
audio {

  margin: 0;
  padding: 0;

}

/* lists */

ul,
ol {

  padding: 0 0 0 1.5em;

}
[dir=rtl] ul,
[dir=rtl] ol {

  padding: 0 1.5em 0 0;

}

li,
dd {

  padding: 0;
  margin: 0 0 0 1.5em;

}
[dir=rtl] li,
[dir=rtl] dd {

  margin: 0 1.5em 0 0;

}
dt {

  font-weight: bold;
  margin: 0;
  padding: 0;

}

li ul,
li ol,
li dl,
dl ul,
dl ol,
dl dl {

  margin-bottom: 0;
  padding: 0;

}
li li {

  font-size: 100%;

}

ul { list-style: disc; }
ol { list-style: decimal outside; }
ol ol { list-style-type: lower-alpha; }
ol ol ol { list-style-type: lower-roman; }
ol ol ol ol { list-style-type: lower-greek; }
ol ol ol ol ol { list-style-type: lower-latin; }

/* tables */

table {

  border-collapse: collapse;
  empty-cells: show;
  border-spacing: 0;
  border: 1px solid var(--border, #ccc);

}

caption {

  caption-side: top;
  text-align: left;

}
[dir=rtl] caption {

  text-align: right;

}

th,
td {

  padding: .3em .5em;
  margin: 0;
  vertical-align: top;
  border: 1px solid var(--border, #ccc);

}
th {

  font-weight: bold;
  background-color: var(--background_alt, #eee);
  text-align: left;

}
[dir=rtl] th {

  text-align: right;

}

/* links */

a {

  outline: none;

}
a:link,
a:visited {

  text-decoration: none;
  color: var(--link, #2b73b7);

}
a:link:hover,
a:visited:hover,
a:link:focus,
a:visited:focus,
a:link:active,
a:visited:active {

  text-decoration: underline;

}

/* misc */

img {

  border-width: 0;
  vertical-align: middle;
  color: var(--text_neu, #666);
  background-color: transparent;
  font-style: italic;
  height: auto;

}
video {

  height: auto;

}
img,
object,
embed,
iframe,
video,
audio {

  max-width: 100%;

}
button img {

  max-width: none;

}

hr {

  border-top: solid var(--border, #ccc);
  border-bottom: solid var(--border, #ccc);
  border-width: 1px 0;
  height: 0;
  text-align: center;
  clear: both;

}

acronym,
abbr {

  cursor: help;
  border-bottom: 1px dotted;
  font-style: normal;

}
em acronym,
em abbr {

  font-style: italic;

}

mark {

  background-color: var(--highlight, #ff9);
  color: inherit;

}

code,
samp,
kbd {

  font-family: Consolas, "Andale Mono WT", "Andale Mono", "Bitstream Vera Sans Mono", "Nimbus Mono L", Monaco, "Courier New", monospace;
  /* same font stack should be used for ".dokuwiki table.diff td" in _diff.css */
  font-size: 89%;
  direction: ltr;
  text-align: left;
  background-color: var(--pre_background, #fbfaf9);
  color: var(--pre_text, #333);
  box-shadow: none;
  border-radius: 2px;
  padding: 1.5px 4px 1.5px 4px;

}

pre {

  font-family: Consolas, "Andale Mono WT", "Andale Mono", "Bitstream Vera Sans Mono", "Nimbus Mono L", Monaco, "Courier New", monospace;
  /* same font stack should be used for ".dokuwiki table.diff td" in _diff.css */
  font-size: 1em;
  direction: ltr;
  text-align: left;
  background-color: var(--background_site, #fbfaf9);
  color: var(--text, #333);
  box-shadow: none;
  border-radius: 2px;
  overflow: auto;
  word-wrap: normal;
  border: 1px solid var(--border, #ccc);
  border-radius: 2px;
  box-shadow: none;
  padding: .7em 1em;

}

blockquote {

  padding: 0 .5em;
  border: solid var(--border, #ccc);
  border-width: 0 0 0 .25em;

}
[dir=rtl] blockquote {

  border-width: 0 .25em 0 0;

}
q:before,
q:after {

  content: '';

}

sub,
sup {

  font-size: .8em;
  line-height: 1;

}
sub {

  vertical-align: sub;

}
sup {

  vertical-align: super;

}

small {

  font-size: .8em;

}

/* forms */

/* for all of the form styles, style.ini colours are not used on purpose (except for fieldset border) */

form {

  display: inline;
  margin: 0;
  padding: 0;

}
fieldset {

  padding: .7em 1em 0;
  padding: .7rem 1rem; /* for those browsers understanding :last-child */
  border: 1px solid var(--text_alt, #999);

}
fieldset > :last-child {

  margin-bottom: 0;

}
legend {

  margin: 0;
  padding: 0 .1em;

}
label {

  vertical-align: middle;
  cursor: pointer;

}

input,
textarea,
button,
select,
optgroup,
option,
keygen,
output,
meter,
progress {

  font: inherit;
  font-weight: normal;
  color: var(--text, #000);
  background-color: var(--background, #fff);
  line-height: normal;
  margin: 0;
  vertical-align: middle;
  box-sizing: border-box;

}

select {

  max-width: 100%;

}
optgroup {

  font-style: italic;
  font-weight: bold;

}
option {

  font-style: normal;
  font-weight: normal;

}

input,
textarea,
select,
keygen {

  border: 1px solid var(--border, #333);
  box-shadow: none;
  border-radius: 2px;

}
input:active,
input:focus,
textarea:active,
textarea:focus,
select:active,
select:focus,
keygen:active,
keygen:focus {

  border-color: #999;

}
input[type=radio],
input[type=checkbox],
input[type=image] {

  padding: 0;
  border-style: none;
  box-shadow: none;

}

/* all types of buttons */
input[type=submit],
input[type=button],
input[type=reset],
input.button,
a.button,
button,
.qq-upload-button {

  color: var(--text, #000);
  background-color: var(--background_alt, #eee);
  border: 1px solid var(--border, #333);
  border-radius: 2px;
  padding: .1em .5em;
  cursor: pointer;

}

input[type=submit]:hover,
input[type=submit]:active,
input[type=submit]:focus,
input[type=button]:hover,
input[type=button]:active,
input[type=button]:hover,
input[type=reset]:hover,
input[type=reset]:active,
input[type=reset]:hover,
input.button:hover,
input.button:active,
input.button:focus,
a.button:hover,
a.button:active,
a.button:focus,
button:hover,
button:active,
button:focus,
.qq-upload-button:hover {

  border-color: var(--background_neu, #ddd);
  background-color: var(--background_neu, #ddd);

}

input::-moz-focus-inner,
button::-moz-focus-inner {

  border: 0;
  padding: 0;

}

input[disabled],
button[disabled],
select[disabled],
textarea[disabled],
option[disabled],
input[readonly],
button[readonly],
select[readonly],
textarea[readonly] {

  cursor: auto;
  opacity: .5;
  background-color: var(--background_alt, #eee);
  color: var(--text_alt, #999);

}

design.less - old revision restored (2026/03/19 18:06)

err404@undisclosed.example.com (err404 ) — Fri, 17 Apr 2026 07:00:47 +0000

/
* This file provides the main design styles for the
* bits that surround the content.
*
* @author Anika Henke anika@selfthinker.org
* @author Andreas Gohr andi@splitbrain.org
* @author Clarence Lee clarencedglee@gmail.com
*/

/* header
/

#dokuwikiheader {
padding: 2em 0 1.5em;

.headings,
.tools {
margin-bottom: 1.5em;
width: 49%;
}
.tools {
margin-top: .2em;
}

h1 {
margin: 0;
font-size: 1.5em;
font-weight: normal;
border: none;

img {
float: left;
margin-right: .5em;
zoom: 50%;
}

span {
display: block;
padding-top: 10px;
}

a {
text-decoration: none;
color: var(–text, #333);
background-color: inherit;
}
}

p.claim {
margin-bottom: 0;
font-size: 0.875em;
}

/* make all links in header (including breadcrumb and interwiki) same colour as the rest */
a {
color: var(–link, #2b73b7);
background-color: inherit;
}
}

[dir=rtl] #dokuwikiheader h1 img {
float: right;
margin-left: .5em;
margin-right: 0;
}

/* tools
/

/* highlight selected tool */
.mode_admin a.action.admin,
.mode_login a.action.login,
.mode_register a.action.register,
.mode_profile a.action.profile,
.mode_recent a.action.recent,
.mode_index a.action.index,
.mode_media a.action.media,
.mode_revisions a.action.revs,
.mode_backlink a.action.backlink,
.mode_subscribe a.action.subscribe {
font-weight: bold;
}

#dokuwikiheader .tools {
ul {
padding-left: 0;
margin-bottom: 0;
}

li {
font-size: 0.875em;
margin-left: 1em;
list-style: none;
display: inline;
}

form.search div.ajax_qsearch li {
font-size: 1em;
margin-left: 0;
display: block;
overflow: hidden;
text-overflow: ellipsis;
}
}

[dir=rtl] #dokuwikiheader .tools li {
margin-right: 1em;
margin-left: 0;
}

#dokuwikiheader .mobileTools {
display: none; /* hide mobile tools dropdown to only show in mobile view */
}

/* site tools */

#dokuwikisitetools {
text-align: right;

form.search {
font-size: 0.875em;
}
}

[dir=rtl] #dokuwikisitetools {
text-align: left;
}

form.search {
display: block;
position: relative;
margin-bottom: 0.5em;

input {
width: 18em;
padding: .35em 22px .35em .35em;
}

button {
background: transparent var(–search-png, url(images/search.png)) no-repeat 0 0;
border-width: 0;
width: 19px;
height: 14px;
text-indent: -99999px;
margin-left: -20px;
box-shadow: none;
padding: 0;
}
}

[dir=rtl] form.search {
input {
padding: .35em .1em .35em 22px;
}

button {
background-position: 5px 0;
margin-left: 0;
margin-right: -20px;
position: relative;
}
}

/* breadcrumbs */

.dokuwiki div.breadcrumbs {
border-top: 1px solid var(–border, #ccc);
border-bottom: 1px solid var(–border, #ccc);
font-size: 0.875em;
clear: both;

div {
padding: 0.5em 0em;
}

.bcsep {
font-size: 0.75em;
}
}

/* sidebar
/

.dokuwiki .aside {
font-size: 1em;
overflow: hidden;
word-wrap: break-word;

/* make sidebar more condensed */

h1 {
font-size: 1.714em;
margin-bottom: .292em;
}

h2 {
margin-bottom: .333em;
}

h3 {
margin-bottom: .444em;
}

h4 {
margin-bottom: .5em;
}

h5 {
margin-bottom: .5714em;
}

p,
ul,
ol,
dl,
pre,
table,
fieldset,
hr,
blockquote,
address {
margin-bottom: .2em;
}

ul,
ol {
padding-left: .5em;
}

li ul,
li ol {
margin-bottom: 0;
padding: 0;
}
}

[dir=rtl] .dokuwiki .aside ul,
[dir=rtl] .dokuwiki .aside ol {
padding-right: .5em;
}

/* content
/

.dokuwiki .pageId {
float: right;
margin-right: -1em;
margin-bottom: -1px;
margin-top: -1.5em;
overflow: hidden;
padding: 0.5em 1em 0;

span {
font-size: 0.875em;
background-color: var(–background, #fff);
color: var(–text_alt, #999);
padding: .1em .35em;
box-shadow: none;
display: block;
border: none;
}
}

.dokuwiki div.page {
clear: both;
background: var(–background, #fff);
color: var(–text, #333);
border: none;
box-shadow: none;
padding: 1.556em 2em 2em;
margin-bottom: .5em;
overflow: hidden;
word-wrap: break-word;
}

.showSidebar div.page {
margin-left: -25px;
}

.dokuwiki .docInfo {
font-size: 0.875em;
text-align: right;
}

/* license note under edit window */
.dokuwiki div.license {
font-size: 93.75%;
}

[dir=rtl] .dokuwiki .docInfo {
text-align: left;
}

[dir=rtl] .dokuwiki .pageId {
float: left;
margin-left: -1em;
margin-right: 0;
}

/* footer
/

.dokuwiki .wrapper {
margin-bottom: 1.4em;
}

#dokuwikifooter {
margin-bottom: 1em;
text-align: center;

> .pad {
font-size: 0.875em;
}

div.license {
margin-bottom: 0.5em;
font-size: 100%;
}

div.buttons a {
img {
opacity: 0.5;
}

&:hover img,
&:active img,
&:focus img {
opacity: 1;
}
}

}

[dir=rtl] #dokuwiki__footer .license img {
margin: 0 0 0 .5em;
}

start

err404@undisclosed.example.com (err404 ) — Thu, 16 Apr 2026 11:06:08 +0000

English

Français

If you don't have your own file server by the time you're 30, you've wasted your life...

It is also a matter of digital sovereignty, not being totally dependent on a third party, it brings a lot of freedoms (but it does not remove responsibilities).
Here's a file server solution in self-hosting at home, based on Proxmox and Yunohost: File server training

I draw from time to time: Illustrations

I enjoy building computers in all kinds of boxes: DataBox

Various random stuff...

start

err404@undisclosed.example.com (err404 ) — Fri, 20 Mar 2026 09:57:34 +0000

English

Français

isolated sessions for LibreWolf and Firefox
disabling punycode in LibreWolf or Firefox
fail2ban
Luanti (formerly Minetest)
Unvanquished (Tremulous's fork)
Editable CSS in Dokuwiki
tiny-status a tool for monitoring pages or other content

firefox.png - created

err404@undisclosed.example.com (err404 ) — Thu, 19 Mar 2026 18:57:23 +0000

librewolf.png - created

err404@undisclosed.example.com (err404 ) — Thu, 19 Mar 2026 18:57:23 +0000

vrac.png - created

err404@undisclosed.example.com (err404 ) — Thu, 19 Mar 2026 11:36:48 +0000

databox_18.jpg

err404@undisclosed.example.com (err404 ) — Tue, 17 Mar 2026 19:35:39 +0000

start

err404@undisclosed.example.com (err404 ) — Tue, 17 Mar 2026 18:22:58 +0000

English

Français

I have made several "DataBoxes" and I am still making them.
Some have been destroyed; others are living a new life, in a new location…

DataBox 18

year: 2026
Case: AEG case
Motherboard: Dell
CPU: intel core i7 2600
RAM: 4GB
Weight: heavy
screen: bizarre almost square format
10 USB ports, some of which are present on the side
1 Display-port
1 VGA port
3 port sata
The motherboard graphics chipset is disappointing…

DataBox 17 (E17)

Year: 2021-2026
Case: an AEG drill case for the central unit, and a case of an electroportative tool for the screen
Motherboard: Dell
CPU: intel core i7
RAM: 32Go
weight: very heavy
screen: 1920x1080
ten USB ports, some of which are extended using USB extension cables
two Display-port
two sata ports
Two hooks on the black case allow you to carry the E17 as a backpack and access to the interfaces is easy by opening the databox from the back:

DataBox 16 (Le Cône)

Year: 2021
Case: Construction site cone
Motherboard: ?
CPU: Intel Celeron, 1 core, 2 threads
RAM: 1 GB
Weight:
Two USB ports on the cone, four on the motherboard
One VGA port
One SATA port
Interior view, airflow is taken from the bottom (four wooden wedges are screwed under the base of the cone to allow air and cables to pass through).
The power supply will expel the hot air towards the top of the cone, which is open. The hard drive is 20°C warmer than the ambient air (it is not specifically ventilated).
It looks like it's piled up in a jumble, but in fact it's screwed and strapped.
This databox is currently installed at tmplab and offers the ltsp service (ltsp allows you to start multiple computers over the network and provide them with a coherent and synchronized desktop environment).

DataBox 15 (The Black case)

This DataBox is in a black case, Openings have been cut to allow airflow and cable routing.

Year: 2020
Case: Black briefcase
Motherboard: Dell 790 (2023-present)
CPU: Intel Core i5 (2023-present)
RAM: 16GB DDR3 (2023-present)
10 USB ports
1 Display Port
1 VGA port
4 SATA ports

DataBox 14

This DataBox is housed in an aluminum case.

Year: 2017
Service until 2020
Case:
Motherboard: Lime2
CPU: A20
RAM: ?
Weight: very light
Two USB ports
One HDMI port
One SATA port

DataBox 13

This DataBox is an orange screwdriver case from Ikea.

Year: 2016
Case: Ikea
Motherboard: Laptop, without battery, keyboard, or case
CPU: Mobile Pentium
RAM: 512MB DDR-2
Weight: very light
Two USB ports
One HDMI port
One SATA port
One LCD screen

DataBox 12

This DataBox is a small mini-screwdriver case.
It is intended to become a server (Web, Jabber, SSH, Minetest).
The goal is to consume even less electricity than the current server.
It currently runs Android, but I plan to install Cubian, which is a GNU/Linux distribution based on Debian.

Year: 2016
Case: Mini-screwdriver
Motherboard: Cubieboard II
CPU: Allwiner 10
RAM: 512MB DDR-2
Weight: Very light
Two USB ports
One HDMI port
One serial port
Plenty of pins to connect all sorts of things.

DataBox 11

This DataBox is a real portable computer (except I couldn't find a way to fit the large keyboard inside). It has a 22.5-inch 1920x1080 screen.

Year: 2015
Case: Hilti
Screen: 1920x1080
Motherboard: Intel, rated to consume less than 30W
CPU: Intel Celeron, 1 core, 2 threads
RAM: 1GB DDR-2
Weight: Quite heavy

Two USB ports and the audio ports are extended for easy access without opening the case.
A WiFi card is installed on the PCI slot (the plastic case appears transparent to microwaves).

DataBox 10

Year: 2014
Case: Hilti
Display:
Motherboard: Two motherboards
CPU: Two 1.8GHz processors
RAM: Two 1GB processors
Weight: Very heavy

This DataBox contains two motherboards and is designed for bit swapping (but has not yet been used). It must be used open to dissipate heat.

Each motherboard contains:
- a CPU clocked at 1.8GHz and 1GB of RAM
- a hard drive for the system and possibly another hard drive for data
- a graphics card on the AGP port
- 4 network cards (in addition to the one already present on the motherboard)

DataBox 9 (FergusL)

I dedicate this ninth DataBox to FergusL, who provided the motherboard and the USB Wi-Fi thingy (which, among other things, is used to wedge the motherboard).

Year: 2013
In use until May 2016
Case: HDPE (High-Density Polyethylene)
Screen:
Motherboard: ?
CPU: Intel Pentium III clocked at 1.6GHz (forced overclocked)
RAM: 1GB
The CPU runs at 1.6GHz, and no one I know has managed to get it to run at 1.3GHz, which is the frequency listed on the CPU itself. This makes this DataBox unreliable if it isn't over-ventilated (the first version crashed within 30 minutes).
Due to its instability (it crashed within a few hours, or even days), I have decided to discontinue this DataBox, and various components will be salvaged for reuse on other equipment.

DataBox 8 (Terry Pratchett)

I dedicate this eighth DataBox to Terry Pratchett, whose "Annals of the Discworld" will remain a reference for me.

Year: 2012
Serviced until 2016
Case: Bosh
Display:
Motherboard: Intel, rated for less than 30W power consumption
CPU: Intel Celeron, 1 core, 2 threads
RAM: 1GB DDR-2
Two USB ports and the audio ports are extended for easy access without opening the case.
The IDE hard drive was replaced with a SATA hard drive in 2015.
The motherboard has a VGA output so this DataBox can be used as a low-power server or as a desktop workstation with its own monitor.
A WiFi card is installed in the PCI slot (the plastic case seems transparent to microwaves).

DataBox 7

Year: 2012
In use until 2015
Case: Small case
Display:
Motherboard: Intel, rated to consume less than 30W (I have a second one)
CPU: Intel Celeron, 1 core, 2 threads
RAM: 1GB DDR-2
Two USB ports are extended for easy access without opening the case.
The IDE hard drive was replaced with a SATA hard drive in 2015.
Although the motherboard has a VGA output, it was used as a server, so no display was connected. A Wi-Fi card is installed in the PCI slot, but the antenna is at the end of a 70cm long cable.
The IDE hard drive is used for the system and part of the /home drive, while a second SATA hard drive is used for storage outside of /home.
Since the whole thing tends to get a little hotter, especially in summer, I equipped the case with an exhaust fan regulated by the temperature of the extracted air.

DataBox 6 (the hamster cage)

Year: 2012
In use until 2015
Case: Hamster cage
Screen:
Motherboard:
CPU: AMD 1200+
RAM: 2 x 512MB SDRAM
Weight: uh, it's mostly bulky
The motherboard was replaced in March 2015 due to a lack of power and stability:
PCI: a Wi-Fi card, an Ethernet network card
AGP: a graphics card
Video card integrated into the motherboard
Motherboard:
CPU: AMD 2500+
RAM: 2 x 512MB DDR
Weight: uh, it's mostly bulky
The cage can Open to provide access to the hard drives, the hatch provides access to the switch and connectors.
This sixth DataBox was in service at Gare XP and was called "Switchman" because it served as a router.
Part of the circuit for the GareXP's little electric train is expected to run inside. It is planned to add a few webcams to display passing trains or the fish in the aquarium on one of the screens, with one screen reserved for displaying information during GareXP events.
Yes, the photo is blurry…

DataBox 5 (recycle bin)

Year: 2012
In use until 2012
Case: plastic wastebasket
No screen, VGA output
Motherboard: a small motherboard that fits in the recycle bin
CPU: ?
RAM: 512MB
Weight: not too heavy, it's for a server, not intended to be transported often
I added a fan to force the air to circulate in a favorable direction.
This DataBox was designed to withstand the elements; the only opening is at the bottom. The PC being at the bottom of the recycle bin, and the recycle bin propped up on two bricks or other support.

DataBox 4

Year: 2012
Case: AEG
Screen: 1024x768 LCD
Motherboard:
CPU:
RAM: 2GB (2 x 1GB DDR4)
Two USB ports are attached to the top, along with the power button and LEDs.
Drill cases often have the advantage of having an ergonomic handle for carrying.

DataBox 3

Year: 2012
Service until 2013
Case: Bosh
Screen: 1024x768 powered by 12V
Motherboard: Intel, rated for less than 30W power consumption
CPU: Intel Celeron, 1 core, 2 threads
RAM: 1GB DDR-2

Two straps allow this DataBox to be carried like a backpack.
Two bent brackets allow the keyboard to be carried during transport. To store the mouse, simply open the case and swing it inside (there's plenty of room).
In the photo, you can see that the screen isn't very straight (after transport), a point that was never completed (properly and permanently securing the screen).
The motherboard is powered by a picoPSU that runs on 12V, and the screen is also powered by 12V. I wanted to be able to use this DataBox from a vehicle's 12V outlet, as the entire enclosure consumes a maximum of 75W.

False DataBox 2.5

Year: 2010
Service until 2012
Case: Toshiba
Screen: 1024x768 LCD
Motherboard:
CPU: Pentium M
RAM: 512MB (2 x 256MB DDR)
Since the screen hinges were broken, I removed the screen and turned it over.
A glass panel salvaged from a flatbed scanner protects the screen.
The battery lasts about 10 minutes, which is enough to move from one electrical outlet to another.
In this configuration, most ports are accessible from the top, which is convenient, except for the audio port, which is located at the bottom.
The CD-ROM drive is removed to save weight and allow access to certain switches.

DataBox 2

Year: ?
Service until ?
PC case: metal
Screen: 1024x768 LCD (a glass panel will be placed in front of the screen to protect it)
Motherboard: ?
CPU: ?
RAM: ?
Weight: heavy
The keyboard has a practical metal base for attaching it to the case during transport or storage.
I added a magnet to the mouse so it could be attached to the case when transporting or storing.

DataBox 1

My first experience with a complete, portable PC (I didn't have a laptop) was taking it with me several Tuesday evenings to the weekly Loop meeting when Le Loop was hosted at "La Suite" (Le Loop was called "La suite logique" before taking its current name).

Year: 2009
Service until ?
PC case: metal
Screen: 1024x768 LCD
Motherboard: ?
CPU?
RAM?
Weight: heavy
The keyboard has a handy metal base for attaching it to the case during transport or storage.
I added a magnet to the mouse so it can be attached to the case during transport or storage.
Simply remove the side panel to access the screen.
And simply tilt the screen to access the rest of the case's components.

server-err404-tmplab.jpg - created

err404@undisclosed.example.com (err404 ) — Sat, 14 Mar 2026 00:19:50 +0000

start

err404@undisclosed.example.com (err404 ) — Sun, 08 Mar 2026 17:00:39 +0000

English

Français

In Dokuwiki (or any other cms), I would like to be able to modify style sheets from Dokuwiki itself, online.

Dokuwiki style sheets are located in /var/www/dokuwiki/lib/tpl/dokuwiki/css/ and are organized in several files.

quite simply, you "just" need to create links to the files to turn them into wiki pages:

command-line example under linux:

ln -s /var/www/dokuwiki/lib/tpl/dokuwiki/css/basic.less /var/www/dokuwiki/data/pages/wiki/basic.less.txt ln -s /var/www/dokuwiki/lib/tpl/dokuwiki/css/content.less /var/www/dokuwiki/data/pages/wiki/content.less.txt ln -s /var/www/dokuwiki/lib/tpl/dokuwiki/css/design.less /var/www/dokuwiki/data/pages/wiki/design.less.txt ln -s /var/www/dokuwiki/lib/tpl/dokuwiki/css/mobile.less /var/www/dokuwiki/data/pages/wiki/mobile.less.txt ln -s /var/www/dokuwiki/lib/tpl/dokuwiki/css/pagetools.less /var/www/dokuwiki/data/pages/wiki/pagetools.less.txt ln -s /var/www/dokuwiki/lib/tpl/dokuwiki/css/structure.less /var/www/dokuwiki/data/pages/wiki/structure.less.txt ln -s /var/www/dokuwiki/lib/tpl/dokuwiki/css/usertools.less /var/www/dokuwiki/data/pages/wiki/usertools.less.txt

If you use the Mindthedark template then you will execute:

ln -s /var/www/dokuwiki/lib/tpl/mindthedark/css/basic.less /var/www/dokuwiki/data/pages/wiki/basic.less.txt ln -s /var/www/dokuwiki/lib/tpl/mindthedark/css/content.less /var/www/dokuwiki/data/pages/wiki/content.less.txt ln -s /var/www/dokuwiki/lib/tpl/mindthedark/css/design.less /var/www/dokuwiki/data/pages/wiki/design.less.txt ln -s /var/www/dokuwiki/lib/tpl/mindthedark/css/mobile.less /var/www/dokuwiki/data/pages/wiki/mobile.less.txt ln -s /var/www/dokuwiki/lib/tpl/mindthedark/css/pagetools.less /var/www/dokuwiki/data/pages/wiki/pagetools.less.txt ln -s /var/www/dokuwiki/lib/tpl/mindthedark/css/structure.less /var/www/dokuwiki/data/pages/wiki/structure.less.txt ln -s /var/www/dokuwiki/lib/tpl/mindthedark/css/usertools.less /var/www/dokuwiki/data/pages/wiki/usertools.less.txt

This allows you to modify style sheets directly from the Dokuwiki.

rpsni

err404@undisclosed.example.com (err404 ) — Tue, 13 Jan 2026 22:53:34 +0000

English

Français

You only need a reverse proxy if you don't have ipv6.
and as not everyone has ipv6 yet (there are even people who will disable ipv6 on their machine…) we'll set up a reverse proxy:

simply install a Haproxy server, either in the hypervisor or in a virtual machine.

it's preferable to install the reverse proxy in a virtual machine or container rather than in the hypervisor, to make backups easier.

and in my case I chose to install the reverse proxy in the same machine that does authoritative domain name server

in my case, virtual machines and containers have ipv6, so domain names go directly to these machines, no need for a reverse proxy sni for ipv6.
the problem is that I only have one public ipv4 (my ISP's box) and I'm obliged to share this single public ipv4 for all my virtual machines or containers.
it's to enable this cohabitation that I install a reverse proxy sni.

with ipv6, it's simple: all the machines have direct access to the Internet and can be reached directly from the Internet, they're independent and don't have port-sharing problems, so no address translation problems.

Reverse proxy sni

Install the haproxy package available in Debian apt install haproxy.

Only one file to edit:

/etc/haproy/haproxy.cfg:

global log /dev/log local0 info log /dev/log local1 info chroot /var/lib/haproxy stats socket /run/haproxy/admin.sock mode 660 level admin stats timeout 30s user haproxy group haproxy daemon # Default SSL material locations ca-base /etc/ssl/certs crt-base /etc/ssl/private # See: https://ssl-config.mozilla.org/#server=haproxy&server-version=2.0.3&config=intermediate ssl-default-bind-ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384 ssl-default-bind-ciphersuites TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256 ssl-default-bind-options ssl-min-ver TLSv1.2 no-tls-tickets defaults log global option dontlognull timeout connect 5000 timeout client 50000 timeout server 50000 errorfile 400 /etc/haproxy/errors/400.http errorfile 403 /etc/haproxy/errors/403.http errorfile 408 /etc/haproxy/errors/408.http errorfile 500 /etc/haproxy/errors/500.http errorfile 502 /etc/haproxy/errors/502.http errorfile 503 /etc/haproxy/errors/503.http errorfile 504 /etc/haproxy/errors/504.http ############################ frontend http_in mode http option httplog bind [::]:80 v6only bind *:80 option forwardfor http-request add-header X-Forwarded-For %[src] http-request set-header X-Forwarded-Proto https if { ssl_fc } acl host_err404 hdr(host) -i err404.numericore.com acl host_err404 hdr(host) -i visio.err404.numericore.com acl host_ikce hdr(host) -i ikce.numericore.com use_backend http_err404 if host_err404 use_backend http_ikce if host_ikce backend http_err404 mode http option forwardfor balance roundrobin server server1 ct-err404:80 backend http_ikce mode http option forwardfor balance roundrobin server server1 ct-ikce:80 ####################### frontend tcp_https mode tcp option tcplog bind [::]:443 v6only bind *:443 acl tls req.ssl_hello_type 1 tcp-request inspect-delay 5s tcp-request content accept if tls acl host_err404 req.ssl_sni -i err404.numericore.com acl host_err404 req.ssl_sni -i visio.err404.numericore.com acl host_ikce req.ssl_sni -i ikce.numericore.com use_backend tcp_err404 if host_err404 use_backend tcp_ikce if host_ikce backend tcp_err404 mode tcp option ssl-hello-chk balance roundrobin server err404 ct-err404:443 send-proxy check backend tcp_ikce mode tcp option ssl-hello-chk balance roundrobin server ikce ct-ikce:443 send-proxy check ############### frontend port1935 mode tcp option tcplog bind [::]:1935 v6only bind *:1935 acl err404_1935 req.ssl_sni -i err404.numericore.com use_backend err404_1935 if err404_1935 backend err404_1935 mode tcp balance roundrobin server err404 ct-err404:1935 send-proxy

bind [::]:80 v6only bind *:80 to listen in ipv4 AND ipv6

I added an example for 1935 port

ct-err404 and ct-ikce are my conteneurs's names, resolved by my own resolver, you can write your ip directly if you want.

Machines (virtual, containers, or other)

You will also need to modify the nginx files on the machines concerned (in my case, these are the machines ikce.numericore.com and err404.numericore.com)

In err404.numericore.com:

Simply add `proxy_protocol` in the `server` segment and only for port 443

Do not touch ipv6 since in my case the machines have public ipv6.

Here is an excerpt from the `/etc/nginx/conf.d/err404.numericore.com.conf` file:

server { listen 443 ssl http2 proxy_protocol; listen [::]:443 ssl http2; server_name err404.numericore.com;

When you modify the nginx configuration file, Yunohost will not be happy and will refuse to update them because they have been modified.

You must do the same for the other virtual machines (ikce.numericore.com in my case).

To obtain the real IP addresses of clients in IPv4 (and not just the reverse proxy IP address):
Here is an excerpt from the `/etc/nginx.conf` file:

http { real_ip_header proxy_protocol; real_ip_recursive on; set_real_ip_from 192.168.1.20;

Replace 192.168.1.20 with the IP address of your reverse proxy SNI.

The box

On the box, you need to redirect ports 80 and 443 to the IP address of the machine hosting the reverse proxy SNI.

ipv4_vs_ipv6_en_.svg - created

err404@undisclosed.example.com (err404 ) — Tue, 13 Jan 2026 22:53:13 +0000

dns

err404@undisclosed.example.com (err404 ) — Tue, 13 Jan 2026 08:19:58 +0000

English

Français

an authoritative dns server (SOA dns) will be used to declare that the server is authoritative for certain domain names.
which will make it easy to define lots of sub-domains without having to change the registrar settings.

I chose to use nsd, but I could have used knot
it's preferable to install the domain name server in a virtual machine rather than in the hypervisor to make backups easier.

and in my case I chose to install the authoritative dns server in the same machine that does reverse proxy SNI

nsd

install the nsd package available in Debian
aptitude install nsd

we'll have to edit a few files, then edit an additional file for each dns zone

nsd.conf

/etc/nsd/nsd.conf:

# NSD configuration file for Debian. # # See the nsd.conf(5) man page. # # See /usr/share/doc/nsd/examples/nsd.conf for a commented # reference config file. server: # log only to syslog. log-only-syslog: yes ip-address: 2a02:8428:753:5002:97dc:9048:0:53 ip-address: 192.168.1.7 # use this number of cpu cores server-count: 1 # We recommend leaving this empty, otherwise use "/var/db/nsd/nsd.db" database: "" # the default file used for the nsd-control addzone and delzone commands # zonelistfile: "/var/db/nsd/zone.list" # The unprivileged user that will run NSD, can also be set to "" if # user privilige protection is not needed username: nsd # Default file where all the log messages go #logfile: "/var/log/nsd.log" # Use this pid file instead of the platform specific default pidfile: "/var/run/nsd.pid" # don't answer VERSION.BIND and VERSION.SERVER CHAOS class queries hide-version: yes hide-identity: yes # Enable if privilege "jail" is needed for unprivileged user. Note # that other file paths may break when using chroot # chroot: "/etc/nsd/" # The default zone transfer file # xfrdfile: "/var/db/nsd/xfrd.state" # The default working directory before accessing zone files # zonesdir: "/etc/nsd" # The following line includes additional configuration files from the # /etc/nsd/nsd.conf.d directory. include: "/etc/nsd/nsd.conf.d/*.conf"

we add a zone file, in my case I have a zone for err404.numericore.com and sub-domains like visio.err404.numericore.com and another zone for ikce.numericore.com

zones.conf

/etc/nsd/nsd.conf.d/zones.conf:

zone: name: ikce.numericore.com zonefile: /etc/nsd/nsd.conf.d/ikce.numericore.com.zone zone: name: err404.numericore.com zonefile: /etc/nsd/nsd.conf.d/err404.numericore.com.zone

err404.numericore.com.zone

Beware, there's a trap that has stuck me for quite a long time:
in the line @ IN SOA ns.err404.numericore.com. err404.numericore.com. (the field err404.numericore.com. is actually an email address

on the other hand, be careful not to forget the period after domain names

I use public ip:

in ipv4 I'll use the box's public ip and redirect port 53 to the machine hosting my dns service

in ipv6 I'll directly indicate the public ipv6 of the machine hosting my dns service

the line containing Serial is simply a serial number that must be strictly increasing each time the file is updated, so we'll often use a current date and increment
/etc/nsd/nsd.conf.d/err404.numericore.com.zone:

$ORIGIN err404.numericore.com. $TTL 7200 @ IN SOA ns.err404.numericore.com. err404.numericore.com. ( 2021042514 ; Serial 7200 ; Refresh 1800 ; Retry 1209600 ; Expire 86400 ) ; Minimum ; NAMESERVERS @ IN NS ns.err404.numericore.com. ns IN A 77.129.238.159 ns IN AAAA 2a02:8428:753:5002:97dc:9048:0:53 ; A RECORDS @ A 77.129.238.159 @ AAAA 2a02:8428:753:5002:fcb3:ff:fe8a:3b80 visio A 77.129.238.159 visio AAAA 2a02:8428:753:5002:fcb3:ff:fe8a:3b80

$ORIGIN err404.numericore.com. will be used as variable for the rest of the file
@ will be replaced by the variable $ORIGIN
so we will define ip for err404.numericore.com and visio.err404.numericore.com.

the box

and finally, on the box, redirect ports 53 to the ip of the machine hosting the authoritative dns server –authoritative–.

start

err404@undisclosed.example.com (err404 ) — Fri, 09 Jan 2026 09:56:57 +0000

source d'inspiration: https://github.com/bderenzo/tinystatus

I modified Bderenzo's tinystatus, by adding an indication of the number of days remaining before the certificate expires, and I also added a variable for periodic page reloading.

fichier tinystatus.sh:

#!/usr/bin/env bash # source https://github.com/bderenzo/tinystatus # MIT licence: https://github.com/bderenzo/tinystatus/tree/master?tab=MIT-1-ov-file#readme # Configuration variables TITLE="Tinystatus" HEADER="Global Status" CHECKS_FILE="${1:-checks.csv}" INCIDENTS_FILE="${2:-incidents.txt}" OUTAGE_RC=false TIMEOUT=10 USER_AGENT="User-Agent: Mozilla/5.0 (X11; Linux x86_64; Debian) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36" TMP_DIR="$(mktemp -d)" TMP_DIR_DEBUG="/tmp/tinystatus-debug" refresh_delay="60" command_exists(){ if ! command -v "${1}" >/dev/null 2>&1; then echo >&2 "Error: ${1} missing. Please install it" exit 1 fi } get_element(){ echo "${2}" | awk -v col="${1}" -F',' '{gsub(/^[ \t]+|[ \t]+$/, "", $col); print $col}' } check(){ check="${1}" host="${2}" name="${3}" expected_rc="${4}" id="${5}" today=$(date +%s) ipversion="$(echo "${check}" | grep -o '[46]$')" case "${check}" in http*) rc="$(curl -${ipversion}sSkLo /dev/null -H "${USER_AGENT}" -m "${TIMEOUT}" -w "%{http_code}" "${host}" 2> "${TMP_DIR}/${id}.ko.info")" cert="$(curl ${host} -vI 2>&1 | grep "expire date"| tr -s " "| cut -d" " -f4-8)" date_exp="$(curl ${host} -vI 2>&1 | grep "expire date")" date_cert=$(date -d "${cert}" +"%s") delay_cert0=$((date_cert - today)) delay_cert=$((delay_cert0 / 86400)) echo "$delay_cert" > "${TMP_DIR}/${id}.ok.cert" if [ -s "${TMP_DIR}/${id}.ko.info" ]; then sed -e 's,curl: ([0-9]*) ,,' -i "${TMP_DIR}/${id}.ko.info" else echo "Status code: ${rc}, expected: ${expected_rc}" > "${TMP_DIR}/${id}.ko.info" fi;; ping*) ping -${ipversion}W "${TIMEOUT}" -c 1 "${host}" >/dev/null 2>&1 rc=$? [ "${rc}" -ne "${expected_rc}" ] && echo 'Host unreachable' > "${TMP_DIR}/${id}.ko.info";; port*) error="$(nc -${ipversion}w "${TIMEOUT}" -zv ${host} 2>&1)" rc=$? [ "${rc}" -ne "${expected_rc}" ] && echo "${error}" | sed -e 's,nc: ,,' > "${TMP_DIR}/${id}.ko.info";; # cert*) # rc="$(curl ${host} -vI 2>&1 | grep "expire date" > "${TMP_DIR}/${id}.cert")";; esac #set -x # verity status and write files if [[ "${rc}" == "${expected_rc}" ]]; then echo "${name}" > "${TMP_DIR}/${id}.ok" # rc="$(curl ${host} -vI 2>&1 | grep "expire date" >> "${TMP_DIR}/${id}.ok")" else echo "${name}" > "${TMP_DIR}/${id}.ko" # rc="$(curl ${host} -vI 2>&1 | grep "expire date" >> "${TMP_DIR}/${id}.ko")" fi #set +x } # Verify requirements command_exists 'curl' command_exists 'nc' command_exists 'ping' command_exists 'grep' #mkdir -p "${TMP_DIR}" || exit 1 # Execute checks id=0 while IFS="$(printf '\n')" read -r line; do check="$(get_element 1 "${line}")" code="$(get_element 2 "${line}")" name="$(get_element 3 "${line}")" host="$(get_element 4 "${line}")" check "${check}" "${host}" "${name}" "${code}" "${id}" & : $((id++)) done < "${CHECKS_FILE}" wait OUTAGES_COUNT="$(ls "${TMP_DIR}/"*.ko | wc -l)" #OUTAGES_COUNT="0" # Generate HTML cat << EOF <!DOCTYPE html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" http-equiv="refresh" content="${refresh_delay}" content="width=device-width, initial-scale=1, shrink-to-fit=no"><title>${TITLE}</title><style> body { font-family: segoe ui,Roboto,Oxygen-Sans,Ubuntu,Cantarell,helvetica neue,Verdana,sans-serif; } h1 { margin-top: 3em; } ul { padding: 0px; } li { list-style: none; margin-bottom: 2px; padding: 5px; border-bottom: 1px solid #ddd; } .container { max-width: 80em; width: 100%; margin: 15px auto; } .panel { text-align: center; padding: 10px; border: 0px; border-radius: 5px; } .failed-bg { color: white; background-color: #E25D6A; } .success-bg { color: white; background-color: #52B86A; } .failed { color: #E25D6A; } .success { color: #52B86A; } .small { font-size: 80%; } .status { float: right; } </style></head> <body> <div class='container'> <h1>${HEADER}</h1> EOF if [ "${OUTAGES_COUNT}" -ne 0 ]; then echo "<ul><li class='panel failed-bg'>${OUTAGES_COUNT} Outage(s)</li></ul>" else echo "<ul><li class='panel success-bg'>All Systems Operational</li></ul>" fi cat << EOF <h1>Services</h1> (updated every ${refresh_delay}s) <ul> EOF for file in "${TMP_DIR}/"*.ko; do [ -e "${file}" ] || continue echo "<li>$(cat "${file}") <span class='small failed'>($(cat "${file}.info"))</span><span class='status failed'></span></li>" done for file in "${TMP_DIR}/"*.ok; do [ -e "${file}" ] || continue echo "<li><a href="$(cat "${file}")">$(cat "${file}")</a> <span class='status success'>certificat expire in $(cat "${file}.cert") days</span></li>" done cat << EOF </ul> <p class=small> Last check: $(date +%FT_%T)</p> EOF if [ -f "${INCIDENTS_FILE}" ]; then echo '<h1>Incidents</h1>' if [ -s "${INCIDENTS_FILE}" ]; then sed 's|^$.*$$|<p>\1</p>|' "${INCIDENTS_FILE}" else echo '<p>No incident reported yet ;)</p>' fi fi cat <<EOF </div> </body></html> EOF # Cleanup and exit rm -r "${TMP_DIR}" 2>/dev/null if "${OUTAGE_RC}"; then exit "${OUTAGES_COUNT}" fi

file example check.csv:

http4, 200, https://err404.numericore.com (IPv4), https://err404.numericore.com http6, 200, https://err404.numericore.com (IPv6), https://err404.numericore.com http4, 200, https://wow.err404.numericore.com (IPv4), https://wow.err404.numericore.com http6, 200, https://wow.err404.numericore.com (IPv6), https://wow.err404.numericore.com

tinystatus.png - created

err404@undisclosed.example.com (err404 ) — Fri, 09 Jan 2026 09:56:47 +0000

browser_without_punycode

err404@undisclosed.example.com (err404 ) — Tue, 02 Dec 2025 12:12:45 +0000

English

Français

To disable the url's punycode in firefox or librewolf:

go to about:config

apply next values:

network.IDN_show_punycode –> false

browser.urlbar.decodeURLsOnCopy –> true (this is when you copy/paste full url)

we do not change the value of network.idn.punycode_cyrillic_confusables –> true to avoid confusion with some Russian chars

start

err404@undisclosed.example.com (err404 ) — Mon, 20 Oct 2025 15:31:11 +0000

English

Français

I need to complete this list, which hasn't been updated for ten years

2011

Creation of the logo for Babel, a routing protocol

2010

infographic

During a trip, I took some photos in the "Castle Room," and a friend sitting under the gargoyle inspired me to do some image editing:
I used The Gimp software to add a little life to the sculpture.

panorama

During a journey in Brittany at Pointe du Raz, I had fun creating panoramas with Hugin

2009

Merging two separate logos to create a logo for the GNU/Linux category for Wikipedia.

2007

During a decoration project in Kaohsiung. The idea was to design a bar, of which here are the models. In the end, the bar was simplified and built straight ahead.

Bar

2005

Computer graphics

For this illustration, I used several images, generally from NASA, but I'm not sure; I can no longer find the files used to create this image. From memory, there are at least:
* an orbital station (Mir?)
* the cockpit of a space shuttle

computer graphics

I used a photo of the Martian surface and drew a miniature landscape as if there were some kind of citadel, with houses and roads.

2001

Espace Artemis

Logos

Some illustrations and sketches of company logos for the Espace Artemis role-playing game universe

Drones

2000s

Espace Artemis

Motorep

Some illustrations for the Espace Artemis role-playing game universe

A motorep. For this image, I used several sources, the details of which I no longer have links.
There is at least one image of a snowmobile, one image of a NASA experimental aircraft, and one image of a cloudscape.

Orbital Stations

For the Artemis Space game universe, I designed an orbital station similar to the Earth Station in the game, and drew some details.

Tank in the Desert

For the Artemis Space game booklet, I illustrated the passage of the tank full of water, abandoned in the desert.

1998

1997

1996

1995

1994

1992

1990s

start

err404@undisclosed.example.com (err404 ) — Mon, 20 Oct 2025 15:30:09 +0000

English

Français

Boris GANNE illustrations:

start

err404@undisclosed.example.com (err404 ) — Tue, 09 Sep 2025 09:28:54 +0000

English

Français

Fail2ban is a software that reads logs and bans IP addresses (IPv4 and IPv6) that abuse the system or perform actions that correspond to certain reasons for banning them.

https://fr.wikipedia.org/wiki/Fail2ban

I find it unfortunate that certain errors (http 400, for example) are not banned by default.

Here are my files:

jails

excerpt from /etc/fail2ban/jail.local (which is a copy of /etc/fail2ban/jail.conf)

[nginx-3xx] enabled = true port = http,https logpath = /var/log/nginx/access.log backend = polling bantime = 30d [nginx-4xx] enabled = true port = http,https logpath = /var/log/nginx/access.log backend = polling bantime = 30d [nginx-400] enabled = true port = http,https logpath = /var/log/nginx/access.log backend = polling bantime = 30d maxretry = 0

Filters

fichier complet pour /etc/fail2ban/filter.d/nginx-3xx.conf

[Definition] failregex = ^<HOST>.*"(GET|POST|HEAD).*" (301|302) .*$ ignoreregex =

complete file for /etc/fail2ban/filter.d/nginx-4xx.conf

[Definition] failregex = ^<HOST>.*"(GET|POST|HEAD).*" (404|444|403|405) .*$ ignoreregex =

complete file for /etc/fail2ban/filter.d/nginx-400.conf

[Definition] failregex = ^<HOST>.*".*" (400) .*$ ignoreregex =

Boris_Ganne_-_200x_-_concert_au_bord_de_l_eau_-_ébauche_crayon.png - created

err404@undisclosed.example.com (err404 ) — Wed, 03 Sep 2025 12:52:17 +0000

Boris_Ganne_-_200x_-_château_-_lavis_à_l_encre_de_chine.png - created

err404@undisclosed.example.com (err404 ) — Wed, 03 Sep 2025 12:52:17 +0000

start

err404@undisclosed.example.com (err404 ) — Tue, 02 Sep 2025 09:53:45 +0000

English

Français

In my web browser, I wanted to have isolated browsing windows (which do not share their session cookies, for example).

My usual settings are to delete all data and retain nothing from the history when closing the browser.
But the web browser's private browsing windows share their session cookies and I don't want that…
There are containers, but you have to decide which one to use each time, which is not practical.
So I quickly cobbled together a script that copies a new profile to /tmp/browser-$name/ (which is a copy of an existing profile) with a random path.
When you close this window, the temporary profile is deleted.
This allows you to have isolated windows and not clutter up disk space unnecessarily when closing the isolated window.
I also wanted to take advantage of saved passwords and bookmarks, which is why I use a reference profile.

Here are two solutions: one for LibreWolf and one for Firefox

solution for LibreWolf

#!/bin/bash # this file is distributed under version 3 or superior from GNU Public Licence # see https://www.gnu.org/licenses/gpl-3.0.en.html # you need to personalise the source variable # there is the source profile for me: source="$HOME/.librewolf/*.pw" # merci à ·☽•Nameless☆•777 · pour son idée d'utiliser mktemp randompath=$(mktemp -d XXXXXXXXX --suffix=.browser -p /tmp) cp -r ${source}/* ${randompath}/ librewolf --profile ${randompath}; rm -r ${randompath}

solution for Firefox

#!/bin/bash # this file is distributed under version 3 or superior from GNU Public Licence # see https://www.gnu.org/licenses/gpl-3.0.en.html # you need to personalise the source variable # there is the source profile for me: source="$HOME/.mozilla/firefox/*.pw" # merci à ·☽•Nameless☆•777 · pour son idée d'utiliser mktemp randompath=$(mktemp -d XXXXXXXXX --suffix=.browser -p /tmp) cp -r ${source}/* ${randompath}/ firefox --profile ${randompath}; rm -r ${randompath}

start

err404@undisclosed.example.com (err404 ) — Mon, 01 Sep 2025 09:30:51 +0000

DokuWiki is an open source wiki application licensed under GPLv2 and written in the PHP programming language. It works on plain text files and thus does not need a database.

I usually install the following plugins:

Bureaucracy Plugin de Andreas Gohr: Create forms and generate pages or emails from them.

caption plugin de Till Biskup: Adding figure and table captions.

cmsmode plugin de Andreas Gohr: Hide Wiki Features from non-logged in users.

color syntax plugin de Harald Hanche-Olsen: Write colored text in DokuWiki.

Gallery Plugin de Andreas Gohr: Creates a gallery of images from a namespace or RSS/ATOM feed.

Move plugin de Michael Hamann, Gary Owen, …: Move and rename pages and media files whilst maintaining the links.

Wrap Plugin de Anika Henke: Universal plugin which combines functionalities of many other plugins. Wrap wiki text inside containers (divs or spans) and give them a class (choose from a variety of preset classes), a width and/or a language with its associated text direction.

XBR Plugin de Christopher Smith: A replacement for the standard dokuwiki renderer which keeps your line-breaks.

err404

err404@undisclosed.example.com (err404 ) — Sat, 16 Aug 2025 08:42:38 +0000

The server err404.numericore.com is hosted in France, by me and under my responsability.
You can contact me via matrix at @err404:matrix.numericore.com (also hosted in my server)

start - created

err404@undisclosed.example.com (err404 ) — Sat, 16 Aug 2025 07:43:39 +0000

Yunohost installation (in virtual machine)

Add the Yunohost install ISO in Proxmox (https://build.yunohost.org/yunohost-bullseye-11.0.9-amd64-stable.iso) to be placed inhttps:your_server_proxmox:8006/# v1:0:=storage%2Fp0%2Flocal:4::=contentIso:::::2
* Create a 30GB VM (specify to boot from the Yunohost ISO)
* Give it at least 2 vpcu and a minimum of 1GB of RAM

Select the graphical installation and follow the steps (leave the default values for most of the time)
Warning: the Yunohost installer is not very happy if it cannot find simd support, but you still need to check Yes to install it.

Once the installation is complete, simply connect to the machine's IP address using a web browser.

start - created

err404@undisclosed.example.com (err404 ) — Fri, 15 Aug 2025 19:40:24 +0000

Lufi is a file-sharing tool, similar to Dropbox.

start - created

err404@undisclosed.example.com (err404 ) — Fri, 15 Aug 2025 19:36:01 +0000

jirafeau is a file-sharing tool, similar to Dropbox.

start - created

err404@undisclosed.example.com (err404 ) — Fri, 15 Aug 2025 19:30:15 +0000

Galène is a video conferencing server that is easy to deploy and requires few server resources. https://galene.org/

For Yunohost, you will need to assign it a domain name or subdomain, for example visio.err404.numericore.com
If you do not have a public IPv6 address to assign to this machine, it will be very difficult to provide a real video conferencing service. (It won't work for everyone, and it's best not to assign a public IPv4 address until you have a working TURN service.)

Galène Demo

In my Galène, I wanted to be the administrator (op), but I also wanted visitors to have some rights to present their screen or other things, so I added the line ‘’“presenter”: [{}],‘’ before the description, and I restarted the Galène service.
Here is what my public.json file looks like:

{ "users":{ "err404":{ "permissions":"op", "password":{"type":"pbkdf2","hash":"sha-256","key":"xxxxxxxxxxxxxxxxxx","salt":"yyyyyyyyyyyyyyyy","iterations":4096} } }, "presenter": [{}], "description":"name or password are optionals", "public":true, "allow-recording":true, "auto-subgroups":true }

files_server_on_a_old_laptop.jpg - créée

err404@undisclosed.example.com (err404 ) — Wed, 13 Aug 2025 19:04:05 +0000

disque_dur.jpg - créée

err404@undisclosed.example.com (err404 ) — Wed, 13 Aug 2025 14:56:57 +0000