• 0 Posts
  • 47 Comments
Joined 1 year ago
cake
Cake day: July 22nd, 2023

help-circle

  • They dont need to know any commands.

    Everything in Linux is point and click. There’s an app store where you’ll find everything you’ll need. You will not need to open the terminal at all. All drivers will get installed through the OS.

    Only things which do not work are the keyboard software and stuff to map macros to your keys and/or mouse buttons ans tweak the colours. Like the Razor software.

    Distros like Ubuntu, popos, Linux mint are incredibly beginner friendly. There are, without a doubt, others.

    They didn’t need to know any cmd/powershell commands using windows and they definitely don’t need to know how to use a Linux terminal to browse/mail/install software on Linux.





  • There’s also the option of setting up a cloudflare tunnel and only exposing immich over that tunnel. The HTTPS certificate is handled by cloudflare and you’d need to use the cloudflare DNS name servers as your domains name servers.

    Note that the means cloudflare will proxy to you and essentially become a man-in-the-middle. You – HTTPS --> cloudflare --http–> homelab-immich. The connection between you and cloudflare could be encrypted as well, but cloudflare remains the man-in-the-middle and can see all data that passes by.







  • It’s looping back to itself? Location header is pointing back to itself.

    Is it possible your backend is sending back an http 301 redirect back to caddy, which forwards it to your browser?

    Possibly some old configuration on your backend from the letsencrypt beforehand? Can you check the logs from your backend and see what they’re sending back?

    I’m assuming the request might replace the host with the IP on your reverse Proxy and that your next cloud backend is replying with a redirect to https://nextcloud.domain.com:443

    Edit: I think this is the most incoherent message I wrote to date.

    I think your reverse Proxy is forwarding the request to your next cloud, but replacing the Host header with the IP you specified as reverse Proxy. As a result the request arrives at your next cloud with the IP as “host”.

    Your next cloud installation is then sending back a 301 redirect to tell the client that they should connect to https://nextcloud.domain.com. this arrives through caddy at your browser, goes through the same loop until you’ve reached the max redirects.

    Have a look at your next cloud backend http logs to see what requests are arriving there and what HOST( http header ) it’s trying to connect to on that IP.








  • I don’t think you can a sim card anonymously in europe. You might be able to find some online, though I have no idea:

    - how legal they are

    - if they function at all/normally

    At least in my country ( which isn’t one you listed ) you cannot buy an anonymous SIM card in shops due to some anti terrorism law ( iirc ).

    I thought it was like that for the whole of Europe, but I could be wrong.

    Apparently there are still EU countries where you can buy anonymous SIMs.