• 0 Posts
  • 26 Comments
Joined 3 years ago
cake
Cake day: August 7th, 2023

help-circle
  • Look buddy I understand that URL has the same issue you mention in your post but it is the official Anubis URL.

    Thus if you really want to be professional you load up the URL past the anime girl, organize a meeting and share your screen.

    Tell them what it is and what it is for.

    Explain what is opensource and the fact that this is free only if they accept that anime girl. Otherwise it’ll be 50 bucks and they can put their own ai designed logo instead.

    If they are still acting like childs treat them like childs. Recenter the meeting on what it is for. Do a proof of concept. I don’t know, do something instead of stating that the official website is not how you would like it to be ?




  • Sympa, bienvenue dans le monde de l’admin système 😉

    Par contre très important : l’exposition depuis l’extérieur.

    Je ne sais pas quel tuto tu as suivi mais pour tout ça tu n’as besoin d’exposer que deux ports : 80 et 443. Rien d’autre sauf peut-être le port que tu as assigné a WireGuard si tu n’es pas chez un FAI qui propose ça en natif sur là box (Free).

    Idéalement tu n’expose PAS le port 22 ni chez toi ni chez ton ami : les bots taperont fort dessus et si tu as une identification avec un mot de passe tu peux être sûr que ça va sauter, encore plus rapidement si ton mot de passe n’est pas compliqué. Utilise des clefs ssh au minimum.

    Je te conseille d’activer un pare-feu sur ta machine, ufw est très simple d’utilisation, et y ajouter un fail2ban ou crowdsec sur les logs des services pour automatiquement bannir les IP qui tentent trop souvent.

    Oui c’est un peu plus que ce que tu as prévu mais c’est là beauté de là chose : t’as commencé a héberger tes propres services, tu ne vas jamais t’arrêter (tu peux remplacer presque tout ce que tu utilises en ligne chez les GAFAM au quotidien).

    N’hésites pas a poster si tu as des questions, y en a pas mal qui pourront sûrement t’aider a y répondre !

    Bonne aventure a toi 😊


  • diminou@lemmy.ziptoSelfhosted@lemmy.world•*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    2
    ·
    5 months ago

    Can you elaborate on what you are using exactly with home assistant ? And is English your primary language in that context ?

    Trying to do something similar, English not primary and its a bit… Harder than it seems. Can’t figure out if it is because I’m not using English or something else. (3060 12GB BTW)













  • You could probably go for nextcloud.yourdomain.ddns.org, but I can’t guarantee that since I have no experience with ddns.org.

    There is a lot of cheap registrars, I’ll let you check and select the one you want if you need a second domain.

    Basically docker let you setup multiple (fake) computers inside your computer. For those that want to correct this, I know. But I’m trying to explain the top view here.

    So, your computer (host) is hosting multiple containers, each containers will have there set of available ports. And as stated earlier each container will have an application that may or may not need to expose ports. But since each have their own ports you can have hundreds of containers using the port 80 INSIDE the container, an using 8100 to 8200 OUTSIDE the container (on your host). The only real limit would be the amount of ports available (somewhere along the lines of 65535).

    There. Now go have fun and read up on docker and reverse proxy! Don’t forget to use ssl on your nextcloud instance since it’ll be facing the internet! And… Have fun! :-)


  • OK you are thinking at it the wrong way : 80 and 443 are the default ports for the web access of any web application.

    You are using docker with the nextcloud aio image. Which mean, you are deploying a docker container which contain the web application.

    What you are doing is using arbitrary ports for the container. This could be 7777. Then, this is redirected to 443 inside the container, to the web application.

    This is why you can actually use any port you want for your container. You are not really switching the port for nextcloud, only for the container.

    This is why I suggested doing 444:443 in the docker-compose.yml file: you are exposing 444 to the container, to 443 inside the container.

    And this is why you can actually use any ports for every web app you are going to host : apache will redirect to the port you want to the container, a’d docker will redirect inside the container to either 80 or 443 (or anything else needed for that web application).


  • In fact 80 and 443 refer to http and https, those are default ports.

    You can in fact use the ports you want for the service you want. I have multiple web services behind the ports 80 and 443, you need one service that is able to get the request at the correct port. This is the role of the reverse proxy.

    Apache can assume that role, you go to anything.yourdomain.com and apache will then redirect “anything” to the correct service (with the internal ip and port). So say you want to put nextcloud at 7777 you can tell docker to expose 7777 and redirect it to 443 on nextcloud.

    The chain is like that in the case : nextcloud.yourdomain.com > apache > nextcloud is at ip:7777 > redirect the request to 7777 > nextcloud homepage is shown