• 4 Posts
  • 115 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2024

help-circle







  • Sort of a self-answer, now that i read more about this issue. The problem is not on the frontend (browser --> server), but with shared connections in the backend. E.g. you have a reverse proxy in place. Whats relevant is that the connection between the reverse proxy and the backend server should be HTTP/2.

    Note that disabling HTTP/1 between the browser and the front-end is not required. These connections are rarely shared between different users and, as a result, they’re significantly less dangerous. Just ensure they’re converted to HTTP/2 upstream.







  • cron@feddit.orgtoSelfhosted@lemmy.worldSelf host sff project
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    2 months ago

    Are you looking to build your own server?

    If you’re thinking about building one, the Jonsbo N4 is a compact case (~20L) that fits up to six 3.5" drives and two 2.5" drives/SSDs. It’s a nice choice if you want something small but expandable. Just note that you’ll need to pick out your own components, and there are some limits when it comes to power supplies and CPU coolers.







  • cron@feddit.orgtoSelfhosted@lemmy.worldIPv6 for self hosters
    link
    fedilink
    English
    arrow-up
    8
    ·
    4 months ago

    Its really not that hard. Sadly, my ISP doesn’t offer IPv6 yet, but for my vServer, enabling IPv6 was just a checkbox during creation. Then, you need to make sure that the service (e.g. webserver) also listens on the IPv6 address and maybe tweak the configuration of the webserver to actually serve websites via IPv6. Also, check your firewall settings. Lastly, you need to set the DNS AAAA records and you’re done.