buh
This commit is contained in:
parent
690b2a109b
commit
481bec0857
|
|
@ -21,124 +21,148 @@
|
|||
|
||||
<div class="content">
|
||||
<h1 style="margin-bottom:0;">ANNOUNCEMENTS !!!</h1>
|
||||
<p style="text-align: center ; font-size: small; color: rgb(255, 203, 48);">
|
||||
For less important announcements, I use Telegram or Mastodon, it doesn't matter which one do you prefer since I will post the same thing in the 2 platforms.
|
||||
</p>
|
||||
<p style="text-align: center; font-size: small; color: rgb(255, 203, 48);"><a href="https://noc.social/@fijxu">Mastodon</a> | <a
|
||||
href="https://t.me/zzlsann">Telegram</a></p>
|
||||
<ul>
|
||||
<li>
|
||||
<a style="color: rgb(255, 107, 107);"> 2023-10-04 @ ~19:55 UTC+0
|
||||
<b>NVMe Self-hosted Server Maintenance</b></a>
|
||||
<p style="color: rgb(255, 107, 107);">
|
||||
At Saturday 7 of this month (2023-10-07) I will be replacing
|
||||
the NVMe Drive from the Self-hosted server to a new
|
||||
one because the one that I have right now is kinda dead lol
|
||||
and I don't want to have problems in the future. It is
|
||||
supposed to have just 150TBW (Terabytes Writen) but it is the
|
||||
double of that WTF!!!!!!!!! I don't know how this
|
||||
thing is still alive... So, probably
|
||||
probably, on Saturday 7 at 23:59 UTC+0 the server will be down
|
||||
for a few hours, probably about 4 hours or more,
|
||||
taking advantage of the time of installation, I'll think about
|
||||
adding LUKS2 encryption but I don't think it's
|
||||
necessary anyway... What I do plan to do is to see if I can
|
||||
disable Intel
|
||||
ME since it is not necessary at all and it is only one more
|
||||
door for vulnerabilities...
|
||||
<p><img class="lol"
|
||||
src="../assets/imgs/fuckingwhatthefuck.png"></p>
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
<a style="color:rgb(133, 224, 103)"> 2023-08-22 @ ~21:35 UTC+0 <b>Wind
|
||||
+ Rain...</b></a>
|
||||
<p>If services are FOR SOME REASON are DOWN without any advice,
|
||||
it could be because <b>Power Outage</b> or <b>Internet
|
||||
Problems</b> thanks to the high speed Wind and upcoming
|
||||
rain in some hours where I live.</p>
|
||||
<img class="center" src="../assets/wind.gif"> <a class="center"><i>Wind
|
||||
in Santiago de Chile...</i></a>
|
||||
<p>Join the <a href="https://t.me/zzlsann">telegram announcements
|
||||
channel</a> if you want more frequent updates, etc, etc.</p>
|
||||
</li>
|
||||
<li>
|
||||
<a style="color:rgb(205, 92, 92)"> 2023-06-05 @ ~20:05 UTC+0
|
||||
(Posted at 01:20 UTC+0) <b>Power Outage</b></a>
|
||||
<p>Well, nothing to say, i wasn't able to change this page since
|
||||
i didn't charge any of my devices so
|
||||
i needed to wait until the power restores. Sorry :p. Where i
|
||||
live things like this never happen, but i
|
||||
guess is the price of living in a third country world.</p>
|
||||
<p>Anyways, if you don't like instability feel free to use other
|
||||
instances other than mine, or even make
|
||||
your own instance, is not that hard even
|
||||
if you use docker</p>
|
||||
</li>
|
||||
<li>
|
||||
<a> 2023-05-19 @ 04:59 UTC+0 <b>About the LibreX search engine...</b></a>
|
||||
<p>As everybody knows, LibreX almost NEVER retrieves the results
|
||||
and it always returns a blank page</p>
|
||||
<p>So I'am going to try to fix the rate limiting issue in LibreX,
|
||||
it doesn't only happen on my instance,
|
||||
it's
|
||||
on all instances on general. Since this a homeserver the
|
||||
percentage of getting rate limited is low
|
||||
compared to rented VPSs from Linode or Vultr.</p>
|
||||
<p><a href="https://github.com/hnhx/librex/issues/226">https://github.com/hnhx/librex/issues/226</a></p>
|
||||
<p>Time to fix...</p>
|
||||
<p>And also, i will fix the I2P and Tor addresses too, they seem
|
||||
to be broken.</p>
|
||||
<p style="color:greenyellow">RESOLVED: LibreX is no fully working</p>
|
||||
</li>
|
||||
<li>
|
||||
<a> 2023-05-17 @ 00:30 UTC+0 <b>Self-hosted services ARE DOWN</b></a>
|
||||
<p>Because I'm stupid and shut down the fiber connection remotely
|
||||
(via ssh), I didn't realize that and ended
|
||||
up cutting my connection to the remote server. Yes I know,
|
||||
laugh at me (╯°□°）╯︵ ┻━┻</p>
|
||||
<p>The server is expected to be back up in less than 12 hours,
|
||||
probably at 13:00 UTC+0.</p>
|
||||
<p>Sorry Invidious users ;(</p>
|
||||
<p style="color:greenyellow">RESOLVED</p>
|
||||
</li>
|
||||
<li>
|
||||
<a>2023-04-23 @ 23:30 UTC+0 | <b>Self-hosted services will be
|
||||
down</b></a>
|
||||
<p>Self-hosted services will PROBABLY fail to connect between
|
||||
05:00-12:00 UTC+0 tomorrow (2023-04-24). This
|
||||
is because my ISP
|
||||
is going to change the GPON router I currently have in my
|
||||
house. I will try to restore as soon as
|
||||
possible. Sorry about this :p</p>
|
||||
<p>
|
||||
This includes:
|
||||
<ul>
|
||||
- Invidious
|
||||
</ul>
|
||||
<ul>
|
||||
- Matrix server (Although I am the ony one using it)
|
||||
</ul>
|
||||
<ul>
|
||||
- ayaya.beauty
|
||||
</ul>
|
||||
<ul>
|
||||
- LibreX
|
||||
</ul>
|
||||
<ul>
|
||||
- Forgejo (Git server)
|
||||
</ul>
|
||||
<ul>
|
||||
- Privatebin
|
||||
</ul>
|
||||
<ul>
|
||||
- Other things that i host but nobody cares
|
||||
</ul>
|
||||
</p>
|
||||
<p style="color:greenyellow">RESOLVED</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p style="text-align: center ; font-size: small; color: rgb(255, 203, 48);">
|
||||
For less important announcements, I use Telegram or Mastodon, it doesn't matter which one do you prefer since I will post the same thing in the 2 platforms.
|
||||
</p>
|
||||
<p style="text-align: center; font-size: small; color: rgb(255, 203, 48);"><a href="https://noc.social/@fijxu">Mastodon</a> | <a
|
||||
href="https://t.me/zzlsann">Telegram</a></p>
|
||||
<ul>
|
||||
<li>
|
||||
<a style="color:rgb(133, 224, 103)"> 2024-01-09 @ ~19:15 UTC+0
|
||||
<b>Domain Name Changes :D</b></a>
|
||||
<p style="white-space: pre-line; color:rgb(133, 224, 103)">Ok so I just bought nadeko.net and I will be slowly replacing my old domain zzls.xyz by nadeko.net. Since months I always wanted to change the zzls domain for a new one with a good tld.
|
||||
|
||||
</body>
|
||||
The zzls.xyz one was one that I bought like 2 or 3 years ago when I first started doing things on the internet, mainly for my first personal projects like Twitch Logs, a bot for a shit streaming site that now it's dead (Booyah.tv) and other things. Then I started to host privacy aware services and using zzls.xyz as domain name seemed pretty shit because, just look at it, what does zzls even means + a ugly, low reputation TLD, xyz, used mostly for scam sites because the first year it costs like 1 dollar and everyone can just use them for whatever they want. Sharing a link that contains .xyz also raises a few eyebrows because everyone knows that they are no that trustable (thanks to the scammers, trash sites, ads, etc)
|
||||
|
||||
</html>
|
||||
zzls.xyz will be still available if you use it, for now I will just make the services use those 2 domains at the same time and for not that used services (like 4get, https://count.ayaya.beauty, https://git.zzls.xyz) I will be adding a redirect, so if you access trough git.zzls.xyz for example, it will redirect you to git.nadeko.net. So you don't really need to change something in your end unless you want to see nadeko.net instead of zzls.xyz in your URL bar. This will apply until I see low traffic trough the zzls.xyz domain.
|
||||
|
||||
<b style="color:yellow">Technically you are all set, you can start using nadeko.net instead of zzls.xyz for all selfhosted services. It will work the same way, in case of a bug or an error, just <a href="https://nadeko.net/contact/index-en.html">contact me</a></b>
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
<a style=""> 2024-01-01 @ ~16:31 UTC+0
|
||||
<b>No internet or Power outage...</b></a>
|
||||
<p style="">
|
||||
Selfhosted services are down. Why? I have no idea because I am not in my home. This could be either a Internet problem or a Power outage.
|
||||
|
||||
If it was a power outage the server should start up by itself but if is there no internet then I can't really do something about it.
|
||||
|
||||
My guess is that there is no internet connection because my DNS records are updated automatically if my IP address changes. I tried to scan a specific port that I have open (not a common one like http or ssh) in the IP range that I have assigned but there was no response from any of the IPs soooo there is nothing I can do about it to fix it. Just wait...
|
||||
</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a style="color: rgb(255, 107, 107);"> 2023-10-04 @ ~19:55 UTC+0
|
||||
<b>NVMe Self-hosted Server Maintenance</b></a>
|
||||
<p style="color: rgb(255, 107, 107);">
|
||||
At Saturday 7 of this month (2023-10-07) I will be replacing
|
||||
the NVMe Drive from the Self-hosted server to a new
|
||||
one because the one that I have right now is kinda dead lol
|
||||
and I don't want to have problems in the future. It is
|
||||
supposed to have just 150TBW (Terabytes Writen) but it is the
|
||||
double of that WTF!!!!!!!!! I don't know how this
|
||||
thing is still alive... So, probably
|
||||
probably, on Saturday 7 at 23:59 UTC+0 the server will be down
|
||||
for a few hours, probably about 4 hours or more,
|
||||
taking advantage of the time of installation, I'll think about
|
||||
adding LUKS2 encryption but I don't think it's
|
||||
necessary anyway... What I do plan to do is to see if I can
|
||||
disable Intel
|
||||
ME since it is not necessary at all and it is only one more
|
||||
door for vulnerabilities...
|
||||
<p><img class="lol"
|
||||
src="../assets/imgs/fuckingwhatthefuck.png"></p>
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
<a style="color:rgb(133, 224, 103)"> 2023-08-22 @ ~21:35 UTC+0 <b>Wind
|
||||
+ Rain...</b></a>
|
||||
<p>If services are FOR SOME REASON are DOWN without any advice,
|
||||
it could be because <b>Power Outage</b> or <b>Internet
|
||||
Problems</b> thanks to the high speed Wind and upcoming
|
||||
rain in some hours where I live.</p>
|
||||
<img class="center" src="../assets/wind.gif"> <a class="center"><i>Wind
|
||||
in Santiago de Chile...</i></a>
|
||||
<p>Join the <a href="https://t.me/zzlsann">telegram announcements
|
||||
channel</a> if you want more frequent updates, etc, etc.</p>
|
||||
</li>
|
||||
<li>
|
||||
<a style="color:rgb(205, 92, 92)"> 2023-06-05 @ ~20:05 UTC+0
|
||||
(Posted at 01:20 UTC+0) <b>Power Outage</b></a>
|
||||
<p>Well, nothing to say, i wasn't able to change this page since
|
||||
i didn't charge any of my devices so
|
||||
i needed to wait until the power restores. Sorry :p. Where i
|
||||
live things like this never happen, but i
|
||||
guess is the price of living in a third country world.</p>
|
||||
<p>Anyways, if you don't like instability feel free to use other
|
||||
instances other than mine, or even make
|
||||
your own instance, is not that hard even
|
||||
if you use docker</p>
|
||||
</li>
|
||||
<li>
|
||||
<a> 2023-05-19 @ 04:59 UTC+0 <b>About the LibreX search engine...</b></a>
|
||||
<p>As everybody knows, LibreX almost NEVER retrieves the results
|
||||
and it always returns a blank page</p>
|
||||
<p>So I'am going to try to fix the rate limiting issue in LibreX,
|
||||
it doesn't only happen on my instance,
|
||||
it's
|
||||
on all instances on general. Since this a homeserver the
|
||||
percentage of getting rate limited is low
|
||||
compared to rented VPSs from Linode or Vultr.</p>
|
||||
<p><a href="https://github.com/hnhx/librex/issues/226">https://github.com/hnhx/librex/issues/226</a></p>
|
||||
<p>Time to fix...</p>
|
||||
<p>And also, i will fix the I2P and Tor addresses too, they seem
|
||||
to be broken.</p>
|
||||
<p style="color:greenyellow">RESOLVED: LibreX is no fully working</p>
|
||||
</li>
|
||||
<li>
|
||||
<a> 2023-05-17 @ 00:30 UTC+0 <b>Self-hosted services ARE DOWN</b></a>
|
||||
<p>Because I'm stupid and shut down the fiber connection remotely
|
||||
(via ssh), I didn't realize that and ended
|
||||
up cutting my connection to the remote server. Yes I know,
|
||||
laugh at me (╯°□°）╯︵ ┻━┻</p>
|
||||
<p>The server is expected to be back up in less than 12 hours,
|
||||
probably at 13:00 UTC+0.</p>
|
||||
<p>Sorry Invidious users ;(</p>
|
||||
<p style="color:greenyellow">RESOLVED</p>
|
||||
</li>
|
||||
<li>
|
||||
<a>2023-04-23 @ 23:30 UTC+0 | <b>Self-hosted services will be
|
||||
down</b></a>
|
||||
<p>Self-hosted services will PROBABLY fail to connect between
|
||||
05:00-12:00 UTC+0 tomorrow (2023-04-24). This
|
||||
is because my ISP
|
||||
is going to change the GPON router I currently have in my
|
||||
house. I will try to restore as soon as
|
||||
possible. Sorry about this :p</p>
|
||||
<p>
|
||||
This includes:
|
||||
<ul>
|
||||
- Invidious
|
||||
</ul>
|
||||
<ul>
|
||||
- Matrix server (Although I am the ony one using it)
|
||||
</ul>
|
||||
<ul>
|
||||
- ayaya.beauty
|
||||
</ul>
|
||||
<ul>
|
||||
- LibreX
|
||||
</ul>
|
||||
<ul>
|
||||
- Forgejo (Git server)
|
||||
</ul>
|
||||
<ul>
|
||||
- Privatebin
|
||||
</ul>
|
||||
<ul>
|
||||
- Other things that i host but nobody cares
|
||||
</ul>
|
||||
</p>
|
||||
<p style="color:greenyellow">RESOLVED</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -27,9 +27,32 @@
|
|||
<p style="text-align: center; font-size: small; color: rgb(255, 203, 48);"><a href="https://noc.social/@fijxu">Mastodon</a> | <a
|
||||
href="https://t.me/zzlsann">Telegram</a></p>
|
||||
<ul>
|
||||
<li>
|
||||
<a style="color:rgb(133, 224, 103)"> 2024-01-09 @ ~19:15 UTC+0
|
||||
<b>Cambios de Nombre de Dominio :D</b></a>
|
||||
<p style="white-space: pre-line; color:rgb(133, 224, 103)">Ok, acabo de comprar nadeko.net y poco a poco iré sustituyendo mi antiguo dominio zzls.xyz por nadeko.net. Desde hace meses siempre quise cambiar el dominio zzls por uno nuevo con un buen tld.
|
||||
|
||||
zzls.xyz fue uno que compré hace como 2 o 3 años cuando empecé a hacer cosas en internet, principalmente para mis primeros proyectos personales como Twitch Logs, un bot para un sitio de streaming de mierda que ahora está muerto (Booyah.live) y otras cosas. Entonces empecé a alojar servicios enfocados a la privacidad y usar zzls.xyz como nombre de dominio me pareció una mierda porque, míralo, ¿qué significa zzls? + un TLD feo y de baja reputación, xyz, usado principalmente para sitios de estafa porque el primer año cuesta como 1 dólar y todo el mundo puede usarlo para lo que quiera. Compartir un enlace que contiene .xyz también levanta algunas cejas porque todo el mundo sabe que no son confiables (gracias a los estafadores, sitios basura, anuncios, etc)
|
||||
|
||||
zzls.xyz seguirá estando disponible si lo usas, por ahora sólo haré que los servicios usen esos 2 dominios al mismo tiempo y para los servicios no tan usados (como 4get, https://count.ayaya.beauty, https://git.zzls.xyz) añadiré una redirección, así que si accedes a través de git.zzls.xyz por ejemplo, te redirigirá a git.nadeko.net. Así que realmente no necesitas cambiar nada en tu extremo a menos que quieras ver nadeko.net en lugar de zzls.xyz en tu barra de URL. Esto se aplicará hasta que vea poco tráfico a través del dominio zzls.xyz.
|
||||
|
||||
<b style="color:yellow">Tecnicamente ya esta todo listo, puedes empezar a usar nadeko.net en vez de zzls.xyz para todos los servicios selfhosted. Funcionara de igual forma, en caso de un bug o error, solo <a href="https://nadeko.net/contact/">contactame</a></b>
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
<a style=""> 2024-01-01 @ ~16:34 UTC+0
|
||||
<b>Sin internet o corte de energia</b></a>
|
||||
<p style="">
|
||||
Acabo de despertarme y los servicios selfhosted no funcionan. ¿Por qué? No tengo ni idea porque no estoy en mi casa. Esto podría ser un problema de Internet o un corte de energía.
|
||||
|
||||
Si se tratara de un corte de energía, el servidor debería inciar por sí mismo, pero si no hay Internet, entonces realmente no puedo hacer nada al respecto.
|
||||
|
||||
Supongo que no hay conexión a Internet porque los registros DNS se actualizan automáticamente si mi dirección IP cambia. Intenté escanear un puerto específico que tengo abierto (no uno común como http o ssh) en el rango IP que tengo asignado (que es 186.104.0.0/15) pero no hubo respuesta de ninguna de las IPs así que no hay nada que pueda hacer para solucionarlo. Solo esperar...
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
<a style="color: rgb(255, 107, 107);"> 2023-10-04 @ ~19:55 UTC+0 <b>Mantenimiento NVMe del Servidor Self-hosted</b></a>
|
||||
<p style="color: rgb(255, 107, 107);">
|
||||
<a style=""> 2023-10-04 @ ~19:55 UTC+0 <b>Mantenimiento NVMe del Servidor Self-hosted</b></a>
|
||||
<p style="">
|
||||
El Sábado 7 de este mes (2023-10-07) Voy a reemplazar el NVMe de mi servidor Self-hosted a uno nuevo porque
|
||||
el que tengo ahora mismo esta algo muerto y no quiero tener problemas en el futuro, se supone que tiene solo
|
||||
150TBW (Terabytes escritos) pero tiene el doble de eso WTFF que wea, y por alguna razón sigue vivo. Así que
|
||||
|
|
@ -44,4 +67,4 @@
|
|||
|
||||
</body>
|
||||
|
||||
</html>
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -30,9 +30,10 @@
|
|||
<p><a>IRC</a> <code>(OFTC, Libera Chat)</code>: <code>/query Fijxu</code> <a>(Or whatever you use to send private messages
|
||||
via IRC)</a></p>
|
||||
<p><a href="https://noc.social/@fijxu@noc.social">Mastodon</a> <code>(https://noc.social/@fijxu@noc.social)</code></p>
|
||||
<p><i>If you are starting to host privacy aware services (or just misc services) and you want to know how I set up X service, like invidious or anything else, just talk to me without fear. Feel free to ask</i></p>
|
||||
</div>
|
||||
<img src="./assets/1661562598453167.png" class="center">
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -29,9 +29,10 @@
|
|||
<p><a href="https://matrix.to/#/@fijxu:zzls.xyz">Matrix</a><code> (https://matrix.to/#/@fijxu:zzls.xyz)</code></p>
|
||||
<p><a>IRC</a> <code>(OFTC, Libera Chat)</code>: <code>/query Fijxu</code> <a>(O lo que sea que uses para mandar mensajes privados por IRC)</a></p>
|
||||
<p><a href="https://noc.social/@fijxu@noc.social">Mastodon</a> <code>(https://noc.social/@fijxu@noc.social)</code></p>
|
||||
<p><i>Si estás empezando a alojar servicios enfocados a la privacidad (o simplemente servicios varios) y quieres saber cómo configurar X servicio, como invidious o cualquier otra cosa, habla conmigo sin miedo. No dudes en preguntar.</i></p>
|
||||
</div>
|
||||
<img src="./assets/1661562598453167.png" class="center">
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -48,11 +48,11 @@
|
|||
<a href="https://noc.social/@fijxu">Mastodon</a> |
|
||||
<a href="https://zzls.xyz/trafficstats">Internet Traffic Stats</a> |
|
||||
<a href="https://blog.zzls.xyz/en">Blog</a>
|
||||
<a href="https://status.zzls.xyz/">Services Status</a>
|
||||
</div>
|
||||
<div class="content">
|
||||
<h1 class="tilttext">>.></h1>
|
||||
<p class="lastupdate">Last Updated: 2023-12-07</p>
|
||||
<p class="lastupdate">12.23 : Now there is a page with the status of all services at <a href="https://status.zzls.xyz/">https://status.zzls.xyz</a></p>
|
||||
<p class="lastupdate">Last Updated: 2024-01-05</p>
|
||||
<p>
|
||||
Hiiiiiii, I am dedicated on
|
||||
hosting privacy related services and other types of services mainly for South
|
||||
|
|
|
|||
|
|
@ -47,13 +47,12 @@
|
|||
<a href="./minecraft">Server de Minecraft (TOTALMENTE VIVO!)</a> |
|
||||
<a href="https://noc.social/@fijxu">Mastodon</a> |
|
||||
<a href="https://zzls.xyz/trafficstats">Estadísticas de tráfico de Internet</a> |
|
||||
<a href="https://blog.zzls.xyz/es">Blog</a>
|
||||
<a href="https://blog.zzls.xyz/es">Blog</a> |
|
||||
<a href="https://status.zzls.xyz/">Estado de los servicios</a>
|
||||
</div>
|
||||
<div class="content">
|
||||
<h1 class="tilttext">>.></h1>
|
||||
<p class="lastupdate">Ultima Actualización: 2023-12-23</p>
|
||||
<p class="lastupdate">12.23 : Ahora hay una pagina para ver el estado de todos los servicios aquí: <a href="https://status.zzls.xyz/">https://status.zzls.xyz</a></p>
|
||||
|
||||
<p class="lastupdate">Ultima Actualización: 2024-01-05</p>
|
||||
<p>
|
||||
Holaalalalalalal, me dedico a alojar servicios
|
||||
enfocados a
|
||||
|
|
|
|||
Loading…
Reference in New Issue