Uberspace 7 – a small experience report

I really like the web hoster Uberspace, and the team started the public beta of Uberspace 7 (U7) a few days ago:

They invested a lot of work into the new system, and it comes with a lot of improvements compared to Uberspace 6 – even now, in the beta version. All domains on U7 get automatic SSL certificates from Let’s Encrypt, and HTTP requests are redirected to HTTPS. U7 supports HTTP/2, comes with PHP-FPM (no more start delay) and MariaDB 10.1 as default database solution. The command line toolchain is fresher than before, and there is a new handbook on manual.uberspace.de. More on that in the post »Die U7 Public Beta« by Jonas Pasche.

I directly registered a few Uberspaces on U7, and among other sites, this site you are currently visiting runs on the new version. My first impression: the performance improvements are huge, especially in the backend. Virtual email users are not supported yet, so I keep a U6 for that, but in the long run, I plan to move everything from U6 to U7. A Piwik installation has to stay on U6 too because U7 sets the X-Frame-Options to SAMEORIGIN, which prevents me from inserting the opt-out-iFrame on other domains. But it is already on the to-do list, that this value can be modified.

One feature I used a lot on U6 will not be supported on U7: hostname directories, to serve, for example, the site test.example.com from the directory /var/www/virtual/$USER/test.example.com. It should be possible to create this feature by yourself, but I failed with my modest knowledge. With that, I have more Uberspaces now than before, but that is no problem because of the adjustable price and the better solution because that feature:

»motivates to host different applications in the same account and combines the security risks of all those applications«.

So far I am really excited about the new version and miss nothing except the virtual email users, which will be coming later, and am happy about the great performance 🙂

Leave a Comment

Your email address will not be published. Required fields are marked *