Hi! I am Russel Taylor. I am married to Donna and we have four growing boys: Preston, Russell, Todd, and Elliott. We live in Holliday, Texas and are Christians who worship our Lord at the Church of the Good Shepherdin Wichita Falls, Texas.
I am the GIS Specialist for Gunn Oil Company. Donna is a Middle School English teacher.
I kept having issues with Docker in Almalinux 8/Cloudlinux 8/Centos 8. Basically, any time that the server would reboot, my Docker containers would fail to start. If I restarted the Docker service manually, it would start working. The problem is that Docker manipulates iptables, but when the Firewall would start, Docker’s iptables would be overwritten. After doing a lot of Googling, it seems I have found a solution.
To resolve this create the following in /etc/csf/csfpre.sh
iptables -t nat -N DOCKER iptables -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER iptables -t nat -A OUTPUT ! -d 127.0.0.0/8 -m addrtype --dst-type LOCAL -j DOCKER iptables -t nat -A POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE
My oldest boy, Preston, is in the 8th grade. They allow 8th graders to participate in Holliday High School’s marching band. Because of a lot of work and practice, the band placed 6th in the 2021 Texas State Marching Band Championships (Class 3A). I am super proud of all of the band kids, but especially Preston! Great job!
After a lot of trial and error, I have finally managed to get Seafile working with my DirectAdmin panel. I am posting my configuration here so that it will be much easier to do the next time!
First, here is my docker-compose.yml file:
- MYSQL_ROOT_PASSWORD=************ # Requested, set the root's password of MySQL service.
- /app/seafile/seafile-mysql/db:/var/lib/mysql # Requested, specifies the path to MySQL data persistent store.
entrypoint: memcached -m 256
- "ES_JAVA_OPTS=-Xms1g -Xmx1g"
- /app/seafile/seafile-elasticsearch/data:/usr/share/elasticsearch/data # Requested, specifies the path to Elasticsearch data persistent store.
- "8443:443" # If https is enabled, cancel the comment.
- /app/seafile/seafile-data:/shared # Requested, specifies the path to Seafile data persistent store.
- DB_ROOT_PASSWD=*********** # Requested, the value shuold be root's password of MySQL service.
- TIME_ZONE=America/Chicago # Optional, default is UTC. Should be uncomment and set to your local time zone.
- SEAFILE_ADMIN_EMAIL=********@***********.com # Specifies Seafile admin user, default is 'email@example.com'
- SEAFILE_ADMIN_PASSWORD=************ # Specifies Seafile admin password, default is 'asecret'
- SEAFILE_SERVER_LETSENCRYPT=false # Whether to use https or not
- SEAFILE_SERVER_HOSTNAME=************.com # Specifies your host name if https is enabled
And now, here is the DirectAdmin Reverse Proxy code that should be pasted in to the Custom HTTPD section:
ProxyPass / https://seafile.EXAMPLE.COM:8443/
ProxyPassReverse / https://seafile.EXAMPLE.COM:8443/
Once the container is up and running, copy your ssl security information. I copy my user ssl.crt and ssl.ca into a single file: tls.crt, which should be installed at /app/onlyoffice/DocumentServer/data/certs/.
Next, copy the ssl.key to /app/onlyoffice/DocumentServer/data/certs/tls.key. Make it read-only by doing chmod 400 tls.key.
Restart the docker container, and you’re good to go. You can access the status page at https://yourwebsite:32769.
First, I create the directory: /app/portainer/local-certs.
Next, I copy the ssl certificates to the directory I just created. They are are same as the onlyoffice ones, except I rename them portainer.crt and portainer.key.
Hey, it’s July! That means we’re more than halfway through the year…thank God! 2020 has been a challenge for most people, I think. We’ve had the Coronavirus/Covid-19 that has been crippling our economy and killing people right and left. We’ve had the Black Lives Matter protests which have turned into riots (they do matter). And through it all, President Trump has been our fearless leader… or not. He seems to think that if he ignores everything it will all work out. I hope he’s right; I really do.
Looking on the bright side, though, we get to go see my mom in Michigan in a couple of days! To be honest, I think I’ve already checked out in my mind… I do dread the drive, though. Two long days… We’re splitting it up so that it is one super-long day, followed by one medium-long day. Hopefully that will make it work.
Whenever I first install Solus Linux, the installer never adds Solus to the UEFI Boot Menu. Here are the steps to fix that issue:
Boot from your live CD/USB. Connect to the internet, and do the following:
Install efibootmgr: sudo eopkg it efibootmgr
(This paragraph probably isn’t necessary, but I am including it to remember how to clean up the UEFI Boot Menu 🙂 ) Run efibootmgr with no arguments. You should see an entry for Linux Boot Manager, which for some reason doesn’t show up in your actual boot menu but does here. There’s a number listed for that entry. Delete it with sudo efibootmgr -b [num] -B
Now you can recreate it. If your EFI partition is /dev/sda1 then do this: sudo efibootmgr -c -d /dev/sda -p 1 -l "\EFI\systemd\systemd-bootx64.efi" -L "Linux Boot Manager"