• 2 Posts
  • 27 Comments
Joined 1 year ago
Cake day: June 16th, 2023
  • proton_lynx@lemmy.worldtolinuxmemes@lemmy.world•What's going on y'all?
    14·
    4 months ago

    I think people are missing the point here. The biggest problem was not that the update was bricking the machines, that could’ve happened to Linux/macOS/BSD etc. The problem is that the solution to the problem is to MANUALLY access the machine, get into safe mode and type some commands. This is insane. And you should be able to EASILY disable automatic updates for apps like that on Windows Server.

  • proton_lynx@lemmy.worldtoSteam Deck@sopuli.xyz•Will anything dethrone the Steam Deck? Probably not -GamingonLinux
    96·
    4 months ago

    It’s really funny to see how out of touch those companies are with the portable consoles. They clearly don’t understand what makes the Steam Deck a good console. They focus on the hardware specs and that’s it, minimal work on the software side (ROG Ally is at least trying). Valve nailed it with the Steam Deck in various aspects: hardware is good, CAD files are available so it’s highly customizable, but the cherry on top is the software integration, it is amazing and it’s always improving. IMHO software is the real reason for Deck’s success (OS, Proton, compatibility badges, etc).

  • proton_lynx@lemmy.worldtoSelfhosted@lemmy.world•[SOLVED] Nextcloud Snap behind Caddy is responding with `301 Moved Permanently`English
    3·
    9 months ago

    Yep, definitely something wrong with the webserver 😅 Can you try this configuration?

    https://nextcloud.domain.com {
        reverse_proxy 192.168.1.182:443 {
                header_up Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
                header_up X-Forwarded-Proto {scheme}
                header_up X-Forwarded-For {remote}
                header_up X-Real-IP {remote}
        }
}

    You said that “originally, the Nextcloud server handled HTTPS with Let’s Encrypt at domain.com” and now you are redirecting to 192.168.1.182 on port 443. Is this Nextcloud server still serving HTTPS with Let’s Encrypt for domain.com?

    I’m asking because if you are using Caddy in front of that HTTPS webserver as a reverse-proxy, you will need to override the Host header with the configured upstream address. Here’s the documentation. I think it would be something like this (?):

    https://nextcloud.domain.com {
        reverse_proxy domain.com:443 {
                header_up Host {upstream_hostport}
                header_up Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
                header_up X-Forwarded-Proto {scheme}
                header_up X-Forwarded-For {remote}
                header_up X-Real-IP {remote}
        }
}