#staff | Logs for 2024-05-09
« return
[03:19:24] <sylvester> 2024-05-09 05:19:24 04mail.soylentnews CRITICAL SMTP STARTTLS Certificate00 CRITICAL - Certificate *.soylentnews.org expired on Sun 05 May 2024 03:53:45 AM GMT +0000.
[11:54:12] <sylvester> 2024-05-09 13:54:11 04mail.soylentnews CRITICAL IRC Certificate00 CRITICAL - Certificate *.soylentnews.org expired on Sun 05 May 2024 03:53:45 AM GMT +0000.
[16:47:58] -!- drussell has quit [Ping timeout: 252 seconds]
[16:48:30] -!- drussell [drussell!~drussell@a4627691kd3g1a0z4.wk.shawcable.net] has joined #staff
[17:18:09] <sylvester> 2024-05-09 19:18:09 08mail.soylentnews WARNING PING IPv400 PING WARNING - Packet loss = 0%, RTA = 241.00 ms
[17:23:13] <sylvester> 2024-05-09 19:23:13 03mail.soylentnews OK PING IPv400 PING OK - Packet loss = 0%, RTA = 125.56 ms
[17:52:30] <janrinok> I've got it now thanks
[17:53:46] <janrinok> fab23, what was the IP address of that box that you found was responsible for email and IRC?
[18:24:20] <chromas> is it different from the one with the domain name?
[18:24:30] <kolie> janrinok, your key and user are added to that box. recommend sudo su devops and going to /home/devops after you ssh in.
[18:24:42] <kolie> 45.33.14.29
[18:25:18] <kolie> chat.soylentnews.org has most of the services
[18:25:29] <kolie> berrylium
[18:26:17] <kolie> it runs postfix and dovecot
[18:27:08] <kolie> basically /etc/letsencrypt/live and then copying them into the places specified for irc and postfix/dovecot is usually enough.
[18:27:33] <kolie> the servers cert for IRC needs to match the server block connections in all connecting computers, updating it makes a new hash
[18:27:58] <kolie> so check the /home/sylnt/solanum/ircd.conf
[18:28:23] <kolie> and /etc/dovecot and/or /etc/postfix for the ssl cert
[18:28:57] <kolie> I remember having to copy the certs off of magnesium.
[18:30:09] <kolie> check /root/notes.txt
[18:30:11] <janrinok> It still won't let me in to dev. I've confirmed the key because I can still log in to berrylium
[18:30:36] <kolie> ssh user janrinok @ 45.33.14.29
[18:31:18] <kolie> are you setup for a pubkey login?
[18:31:44] <janrinok> janrinok@45.33.14.29: Permission denied (publickey).
[18:32:25] <kolie> the key is installed, if your sending another it wont work
[18:33:00] <kolie> ill confirm again, but ssh and your user is setup i did test.
[18:33:00] <janrinok> i am trying to ssh in like I do for every other box. I am not sending another. I am using the one that I gave you, and I know that it works because it works on berrylium
[18:34:31] <janrinok> I am in! I don't know why it wouldn't accept me the last couple of times. I have done nothing different at this end.
[18:39:16] <janrinok> chromas, yes, there was one server that was causing about 50% packet loss but we couldn't decide what it was for...
[18:54:37] <janrinok> damn! it is the end of my day again!
[21:46:25] <fab23> janrinok: the server with packet loss was www.soylentnews.org (or just soylentnews.org) with IPv6 2600:3c00::f03c:91ff:fe98:90b
[21:47:09] <fab23> janrinok: and the one with IRC / mail and still the old certificate is mail.soylentnews.org (72.14.184.41 /
[21:47:18] <fab23> 2600:3c00::f03c:91ff:fe6e:311b)