Aller au contenu principal
NUKOE

Mon petit ARPANET: Guide pratique pour héberger un site web rétro

• 10 min •
Un serveur web rétro prêt à accueillir les visiteurs du passé.

In 1995, Brandon, an American student, published his first web page: "Welcome to Brandon's Web Page! Here are some links and a picture of my cat." No sophisticated design, no database, no cookies. Just raw HTML, a bit of CSS, and a contagious passion. Today, this simplicity brings a smile, but it embodies the very essence of the Internet: a space for personal creation, free and decentralized. Before large corporations turned the web into a commercial showcase, thousands of individuals built the network of links and ideas that shaped our digital world.

This article invites you to relive that era by building your own "retro web server." No need for an expensive cloud subscription or complex infrastructure: with an old computer, a bit of patience, and a good dose of nostalgia, you can host a site that could have appeared on the ARPANET of the 1980s or the web of early Internet users. This practical guide will show you how, while exploring why this experience remains relevant today.

Why go back in time?

The web before 2026 was not a giant social network or a product catalog. As a testimony on Reddit recalls, "instead of social networks, people created their own little websites." These personal pages, often hosted on university servers or providers like GeoCities, were the beating heart of the Internet. Each site was unique, reflecting the personality of its author with psychedelic backgrounds, visitor counters, and blinking GIFs.

By recreating this experience, you touch the technical and cultural foundations of the web. You understand why HTML, HTTP, and the first Apache servers were designed as tools for sharing, not surveillance or monetization. It is also a great opportunity to learn the basics of system administration, network security, and web development, without the pressure of modern frameworks.

From ARPANET to your living room: anatomy of a retro server

ARPANET, the precursor to the Internet, relied on machines that were powerful for their time but trivial compared to a modern Raspberry Pi. A retro web server can be just as modest.

Hardware: vintage or emulation?

For an authentic experience, nothing beats a real computer from the 1980s-1990s: a Commodore 64, an Amiga 500, an IBM PC with MS-DOS, or a Macintosh Classic. These machines can function as a web server using software like Contiki (for C64) or MacHTTP (for Mac).

But if you lack space or hardware nostalgia, emulation is an excellent alternative. Emulators like VICE (C64) or Basilisk II (Mac OS 9) allow you to run these systems on your modern machine. You can even connect the emulator to your local network so that other Internet users (or yourself) can access the site.

Software: simple HTTP

The most iconic web server of the time is NCSA HTTPd, created at the National Center for Supercomputing Applications. It gave birth to Apache, which still dominates today. For a retro server, you can use:

  • NCSA HTTPd (version 1.3 or 1.4) – the pioneer.
  • Apache 1.3 – more modern but still vintage.
  • thttpd – a lightweight server, perfect for old machines.
  • Python SimpleHTTPServer – ideal for testing, but less authentic.

Installation often boils down to copying the binary and a minimal configuration file. No complex dependencies, no package manager.

Step-by-step configuration

Let's take the example of a Raspberry Pi (model 1 or 2) running Raspbian, which emulates the spirit of early Linux servers.

Step 1: Install Apache 1.3

sudo apt-get install apache1.3

Yes, it's that simple. But to stick to the era, compile it from source:

wget http://archive.apache.org/dist/httpd/apache_1.3.42.tar.gz
tar xzvf apache_1.3.42.tar.gz
cd apache_1.3.42
./configure --prefix=/usr/local/apache
make
sudo make install

Step 2: Customize the site

Create an `index.html` file in `/usr/local/apache/htdocs/` with basic HTML:


<html><head><title>My retro server</title></head>
<body>
<h1>Welcome to my ARPANET-like server!</h1>
<p>This site runs on a Raspberry Pi with Apache 1.3.</p>
<p>You are visitor number <blink>42</blink>!</p>
</body></html>

Add animated GIFs, a visitor counter (in PHP or CGI), and a patterned background.

Step 3: Make the site accessible

Configure your router to forward port 80 to the local IP of the Raspberry Pi. You can also use a dynamic DNS service like no-ip or DuckDNS to get a stable domain name.

If you want maximum authenticity, limit yourself to the local network: nothing beats the thrill of seeing "http://192.168.1.42" appear on a friend's browser.

Beyond the server: recreating the user experience

A server is nothing without its audience. To dive into the spirit of the early web, encourage your visitors to use a retro browser like Netscape Navigator 4 or Internet Explorer 5 (in a VM). You can even create a directory of links to other retro sites, like the early "webrings."

The experience is then complete: slow navigation (the site can be hosted on an ADSL or ISDN connection), minimalist design, no heavy JavaScript. Your visitors rediscover the magic of the Internet: each page is a discovery, each link an adventure.

Lessons from the past for the web of tomorrow

This return to basics is not just a nostalgic exercise. It reminds us of fundamental principles that the modern web has sometimes forgotten:

  • Decentralization: anyone can be a host, without relying on cloud giants.
  • Simplicity: a static page is often enough to convey an idea.
  • Creative freedom: no algorithm dictates what you should publish.
  • Community: manual links and webrings fostered serendipitous discoveries.

In 2026, a debate on Hacker News asked "What was the Internet like before corporations got their hands on it?" The responses all evoked this blessed period when "you could host your site or your application on a server" without intermediaries. Today, recreating a retro server is about reconnecting with that pioneering spirit.

Extending the adventure: archives and preservation

Your retro server can also serve as a repository for forgotten content. The Ctrl-alt-rees project (ctrl-alt-rees.com) shows how to rebuild disappeared sites from Wayback Machine archives. Why not host a copy of a lost GeoCities site or a BBS from the 1990s? You will thus contribute to the preservation of digital heritage, a crucial issue as reminded by the r/lostmedia community on Reddit.

Conclusion

Building a retro web server is more than a technical project: it is a journey through time, a history lesson, and a declaration of digital independence. In a few hours, you can bring to life a machine that embodies the spirit of the early Internet, a space where creativity and sharing took precedence over profit.

So, ready to write your own "Welcome to my page!"? Get started, and maybe one day, a future enthusiast will unearth your site from the ruins of the web to study its HTML tags.

To go further