Ugh. I guess it's time to upgrade my Mastodon instance. I have to upgrade through two releases. This always gives me heartburn, but it's got to be done before it gets out of hand.
If I disappear, it's because I flubbed the upgrade, not because I've been disappeared. Things aren't that dire yet.
For the last few years, I've worked with servers, starting with Windows and now using only Linux systems. Well, I believe in a free internet, 'my data, my rules.' Setting up a server from scratch was new to me, from domain to production. The Mastodon instance was eye-opening; fun yet frustrating due to hard-to-find info. I am Happy i took this step, and to dive deeper in my cozy corner of the internet.
PowerShell Automatic Variables Tip #1 #ITTraining #CodingForBeginners #AzureAutomation #CyberSecurity #TechTutorial #LearnPowerShell #PowerShellTutorial #ITPros #Automation #Scripting #PowerShellScripting #DevOps #windows #windowsserver #serveradmin #cloudcomputing#vscode#softwareengineering #systemadministrator
OK, finally got back on the Mastodon Good Server Owner Bandwagon and updated to the latest 4.3.x release. One note: using `yarn install --immutable` got me errors, but `yarn install` did not. So...while my mutability has suffered, the security of my Mastodon server has increased.
At the first #software #company I worked at, we had a #server #administrator who named the servers after astrological signs. In my current company, I'm doing server administration, and I use names of gods from Greek mythology. Not because I'm interested in Greek mythology, but simply because I needed a quick naming scheme. I now want to switch to a new scheme. There are probably better/funnier naming schemes. What scheme do you use?
#serveradmin #devops
Logged into my #opennediavault dashboard yesterday to find the disk that acts as storage for my #yunohost VM was failing. Copied the disk images to a different filesystem, and now I have a project for when I'm back from vacation
Probably should have remembered I set it up to use the random HDD that came in my cheap #eBay computer before I actually started relying on it.
Glad it wasn't one of my fairly new 2TB drives though
Fun (actually not fun at all) fact about Caddy:
This expression will be merged with AND
:
@matcher {
path /foo
header Header-Name value
}
OR
, despite being functionally identical:@matcher {
expression `path('/foo')`
expression `header({'Header-Name': 'value'})`
}
AND
unless two matchers of the same time are adjacent. In the latter case, they may be merged with AND
or OR
depending on matcher-specific logic, which is not publicly documented.@admin Solved as follows:
The SSL let's encrypt cert is created out of the http file of the given domain or subdomain:/etc/apache2/sites-available/domain.org.conf
standard domain.org.conf
<VirtualHost *:80>
ServerAdmin admin@domain.org
ServerName domain.org
DocumentRoot /var/www/domainorg
# AllowOverride is specifically added for the friendica server
<Directory /var/www/domainorg>
AllowOverride All
</Directory>
# AllowOverride is specifically added for the friendica server
ErrorLog ${APACHE_LOG_DIR}/domainorg_error.log
CustomLog ${APACHE_LOG_DIR}/domainorg_access.log combined
</VirtualHost>
-le-ssl
to the existing domain.org.conf name. The port for SSL connections is 443 while the standard http connection is over port 80.domain.org-le-ssl.confThis is the content of the file created for a multi domain VPS server. This contenet matches the content that was in the original 000-default-le-ssl.conf file of the single domain VPS setup, created by the certbot routine. The SSL certificate is supposed to be updated automatically every year. For now it is not clear if the changes made will be affected negatively by that automatic SSL cert update.
<IfModule mod_ssl.c>
<VirtualHost *:443>
ServerAdmin admin@domain.org
ServerName domain.org
DocumentRoot /var/www/domainorg
# AllowOverride is specifically added for the friendica server
<Directory /var/www/domainorg>
AllowOverride All
</Directory>
# AllowOverride is specifically added for the friendica server
ErrorLog ${APACHE_LOG_DIR}/domainorg_error.log
CustomLog ${APACHE_LOG_DIR}/domainorg_access.log combined
ServerName domain.org
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/domain.org/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/domain.org/privkey.pem
</VirtualHost>
</IfModule>
activating and deactivating .conf flesTo make the changes come into effect the new conf file has to be activated, the old one that shouldn't apply anymore should be deactivated and the apache server itself has to be reloaded or to be restarted:
rootname@VPShosting:~# a2ensite domain.org
rootname@VPShosting:~# a2ensite domain.org-le-ssl.conf
rootname@VPShosting:~# a2dissite 000-default.conf
rootname@VPShosting:~# a2dissite 000-default-le-ssl.conf
rootname@VPShosting:~# systemctl restart apache2
Reloading the site took a while longer than nomal, indicating that new background tasks where happening.
testing the new folder structure and if site configuration was actually in place.
Renaming the index file of the old /html folder.
Reloading the site did still work so the old /html folder structure wasn't active anymore.
Renaming the entire old /html folder structure taking it out of access completely.
Creating a new /html folder.
Creating a new html. index file in /var/www/html.
rootname@VPShosting:~# mv /var/www/html/index.php /var/www/html/index_old.php
rootname@VPShosting:~# mv /var/www/html/ /var/www/html_old/
rootname@VPShosting:~# mkdir /var/www/html/
rootname@VPShosting:~# nano /var/www/html/index.html
<html>
<title>name-based virtual hosting setup</title>
<h1>Welcome to the /html/ index.html fall back file.</h1>
<p>This is a test file for a name-based virtual hosting setup</p>
</html>
This was a challenging video to make because I’m very skeptical of my own bias, genuinely interested to hear from people who run instances if they think I managed to walk the line.
#DevOps #ServerAdmin
From: @fedihost
https://video.fedihost.co/videos/watch/9cf467b1-7b24-4f5f-846a-151822b0fcbc
I'm considering editing my robots.txt file to mention a subdirectory that explicitly says "no robots allowed" and only install nepenthese ( https://www.404media.co/email/7a39d947-4a4a-42bc-bbcf-3379f112c999/?ref=daily-stories-newsletter ) in that directory so only disrespectful crawlers will access it.
Might see how I can tweak the code, or make something myself so it'd be harder to fingerprint and avoid by crawlers.
New #introduction post!
My name is Rory! I'm a fluffy red panda and yes, I do like apples, naps, and big scares.
I work for a county government as a #water / #wastewater treatment plant operator. I love what I do and enjoy talking about all things water and wastewater including how to better utilize these resources better for a more sustainable future.
I have a background in #EmergencyManagement and #EnvironmentalScience / #Sustainability / and #HumanEcology. Hit me up and let's nerd out about population dynamics and how they impact resource usage, sometime!
I have interests in: #GIS #boardgames #gaming #pc #playstation #NintendoSwitch #CloudComputing #ClusterComputing #RaspberryPi #serveradmin #linux #SteamDeck #linuxgaming #reading #audiobooks #photography #conventions
Oof. I just tried to upgrade my mastodon server to Ubuntu 24.04.1 LTS and it failed spectacularly. Fortunately, I was able to recover with last night's backup. I may have lost some posts or replies, so if you're missing something, I apologize.
Keep regular backups, people!
Technical storytime! This actually happened.
A dedicated server on a generic host. A client with 6 sites and 45 domains, one of them lucrative.
The server went completely offline multiple times. I had to reboot through VPN. So I contacted support.
Me: The server keeps going down. It's completely offline. I think it might be hardware related.
Support: Reboot the server through your WPN/IPMI connection.
1/