DEV Community: Koffer.

AKKY, DIGITAL OCEAN DNS, AND letsencrypt CERTIFICATES.

Koffer. — Thu, 25 Sep 2025 16:27:19 +0000

The LetSenCrypt certificate for a .com.mx domain hosted on Digital Ocean (on a droplet) expired, and I couldn't re-register it. I was getting the error "DNSSEC: DNSKEY Missing" and that IPv6 wasn't configured. Below I'll go through what I discovered step by step:

1- First I added some AAAA records and configured the IPv6 address for the droplet to work, but it didn't work (although this helped later).
2- I discovered that in the domain configuration at AKKY (the Mexican company that manages MX domains), they had added an option called REGISTRO DS (Delegation Signer), which adds the data for a KSK key, which adds security to the domain registration. The problem is that this option, which appears to be the same as DNSSEC, is not compatible with Digital Ocean's DNS, so I had to delete that record.
3- Checking the DNS connection on a site called DNSViz, it indicated that it was already configured. The DNS issue was resolved.
4- The certificate still wasn't generated, but the error changed to one indicating that IPv6 was not authorized. All I did was add IPv6 to the NGINX server definition so it would use IPv6 along with IPv4.

server { listen 443 ssl http2; listen [::]:443 ssl http2; # Listen on all available IPv6 addresses on port 443 server_name your_domain.com www.your_domain.com; ... other configurations }

With that, the certificate renewal worked, and the domain was visible again.

Spanish version AKKY, DIGITAL OCEAN Y CERTIFICADOS letsencrypt.

A un dominio .com.mx hospedado en digital ocean (en un droplet) se le venció el certificado de letsencrypt y no podia volver a registrarlo me marcaba el error :DNSSEC: DNSKEY Missing" y que ipv6 no estaba configurado. a continuación voy por pasos lo que fui descubriendo:

1- agregue unos records AAAA y configure la dirección ipv6 para que funcionara el droplet, pero no funciono (aun que mas adelante esto me sirvio).
2- Descubri que en al configuración del dominio en AKKY (la empresa mexicana que administra los dominios mx) agregaron una opción que se llama REGISTRO DS (Delegation Signer) y que agrega los datos de una llave ksk que agrega seguridad a el registro del dominio. El problema es que esta opción que parece ser lo mismo que DNSSEC, no es compatible con el DNS de Digital ocean asi que tuve que borrar ese registro.
3- Revisando la conexion de dns en un sitio que se llama DNSViz me indicaba que ya estaba resuelto el problema del DNS.
4- El certificado de todas manera no se generaba, pero cambio el error a uno en el que me indicaba que la ipv6 no esta autorizada. Lo unico que hice fue agregar en la definición del servidor NGINX para que usara ipv6 junto con ipv4

server { listen 443 ssl http2; listen [::]:443 ssl http2; # Listen on all available IPv6 addresses on port 443 server_name your_domain.com www.your_domain.com; ... other configurations }

con eso ya funciono la renovación de certificado y el dominio se volvio a ver.

How to configure akky email with Digital ocean hosting

Koffer. — Sun, 21 Jul 2024 22:50:51 +0000

Sometimes you have to connect service from a Mexican Domain Registrar with a US web histoing company and some problems arise. Let's be clear, the problem is that AKKY's domain and email administration is a bit confusing, which is why I am writing this text, so This is a brief documentation.

The basic idea is that you change the Akky DNS server to the Digital Ocean servers and from that side you configure the email with the data provided by AKKY.

the values should remain as

ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

Steps to follow

1- The first thing is to have a DOMAIN purchased in AKKY, generally it will be a .com.mx or .mx domain, this is almost a prerequisite.

2 The next step is to buy an email address in AKKY and follow the steps to configure it, in that part it is not complicated, there is a page with documentation

AKKY Email Documentation in spanish.

AKKY assumes that the domain is hosted at least with the DNS addresses in AKKY and not with another hosting provider, but on that same documentation page it indicates which values will be used in digital ocean.

EMAIL records:


Nombre/Host/Alias	TTL	Tipo	Prioridad	Valor/Destino
@ o dejar en blanco	3600 o 1 hora	MX	10	mx001.cloudus.xion.oxcs.net
@ o dejar en blanco	3600 o 1 hora	MX	10	mx002.cloudus.xion.oxcs.net
@ o dejar en blanco	3600 o 1 hora	MX	10	mx003.cloudus.xion.oxcs.net
@ o dejar en blanco	3600 o 1 hora	MX	10	mx004.cloudus.xion.oxcs.net


Nombre/Host/Alias	TTL	Tipo	Valor/Destino
@ o dejar en blanco	3600 o 1 hora	TXT	v=spf1 include:spf.cloudus.xion.oxcs.net ~all

These values may change and it is best to review the values in the AKKY documentation.

3- In the administration of the domain in digital ocean, the MX records must be created with the values above and the A records are left with the values of digital ocean. In this way, the email has been configured with AKKY and the site in digital ocean.

It is important not to get confused with the advanced DNS section that appears in the AKKY administration where it seems that everything can be configured, that section only works if you want to continue using all the services in akky and only add a record.

Version en español

Como configurar el correo de akky con el hospedaje de Digital ocean

Algunas veces se tiene que conectar servicio de una compañia mexicana con una compañia de hospedaje web de USA y surgen algunos problemas. En realdiad seamos claro el problema esta en que la administración de dominios y correo de AKKY es un poco confusa, preo en parte por eso escribo este texto, para que quede una breve documentación.

La idea basica es que se cambian el servidor de DNS de akky a los servidores de digital ocean y de ese lado se configura el correo con los datos que da AKKY.

deben quedar como

ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

Pasos a seguir

1- Lo primero es tener un DOMINIO comprado en AKKY, generalmente sera un dominio .com.mx o .mx esto es casi un prerequisito.

2 El siguiente paso es contratar una dirección de correo en AKKY y seguir los pasos para configurarlo, en esa parte no es complicado existe una pagina con documentación

Documentación email AKKY.

AKKY asume que el dominio esta alojado por lo menos con las direcciones DNS en AKKY y no con otro proveedor de hospedaje, pero en esa misma pagina de documentación indica cuales son los valores que se usaran en digital ocean.

Son estos:


Nombre/Host/Alias	TTL	Tipo	Prioridad	Valor/Destino
@ o dejar en blanco	3600 o 1 hora	MX	10	mx001.cloudus.xion.oxcs.net
@ o dejar en blanco	3600 o 1 hora	MX	10	mx002.cloudus.xion.oxcs.net
@ o dejar en blanco	3600 o 1 hora	MX	10	mx003.cloudus.xion.oxcs.net
@ o dejar en blanco	3600 o 1 hora	MX	10	mx004.cloudus.xion.oxcs.net


Nombre/Host/Alias	TTL	Tipo	Valor/Destino
@ o dejar en blanco	3600 o 1 hora	TXT	v=spf1 include:spf.cloudus.xion.oxcs.net ~all

Estos valores pueden cambiar y lo mejor es irse a revisar los valores en la documentación de AKKY.

3- En la administración de el dominio en Digital Ocean se tienen que crear los records MX con los valores de arriba y los records A se quedan con los valores de digial ocean de esta manera se tienen configurado el correo con AKKY y el sitio en digital ocean.

Es importante no confundirse con la sección de DNS avanzado que aparece en la adminsitración de AKKY donde pareciera que se puede configurar todo, eso solo sirve si se quiere seguir usando todos los servicios en AKKY y solo agregar algun record adicional.

local installation of Open Journal Systems (OJS) with DDEV

Koffer. — Sun, 08 Oct 2023 00:55:55 +0000

Like some know DDEV is an open source tool for launching local web development environments. DDev work by default to install Drupal sites, Wordpress, Typo3 and Laravel (and other cms projects) but OJS is not in the list. OJS is a specialized CMS to publish scientific journals.

To get a local installation this is the steps:
1-Get OJS 3.4 program for the pkp site.
2-Locally create a directory and get there all OJS files, this is the directory where you will run the ddev project.
Actually go inside it using terminal

3- Follow the DDEV instructions to begin with a PHP project

3.1 Write the command: ddev config to begin the project. DDEV will give you the kind of project you can begin with it.
Choose (write) PHP. DDev will ask for another information like project name etc. DDEV begin downloading and creating docker images to run the project.
3.2 Type the command: CD .ddev to go inside the ddev project folder.
Then type the command: nano config.yaml (or vim or the editor you like to use) to change the configuration of project.
3.3 You need to change the php, web server and database the project use, to get the closer you can, to OJS requirements. This is the configuration I use:

name: ojs type: php docroot: "" php_version: "8.0" webserver_type: apache-fpm xdebug_enabled: false additional_hostnames: [] additional_fqdns: [] database: type: postgres version: "10"

Check your configuration very carefully before copying this config. The most important part is to get a php 8.0, apache-fpm and postgres 10.

do the change and save configuration file.
Return to main directory (where you copy ojs files)

Dont modify any other information insde conf file.

4- Type the command: ddev start to run DDEV. If all the configuration change are correct you will get a OJS ready to install.
Type the command: ddev launchto open the browser and get the OJS installation page.

5- The OJS installation page will ask for all the information require to install, like a username and a password and database information.
The basic problem I get to install OJS was to get all the requirements needed, many of the version of database OJS ask for are old. I try but cant install the program with mysql, but I get a installation with postgress.
It is important to get database information to not get frustrated. The fast answer is DDEV create a database with name DB a user DB with a password DB and dont write localhost to find the database, type DB, really easy dont? if you want to know more about what DDEV is running just type the command: ddev describe to get all the information of the project.
After all this configuration you will get a OJS site to test local.

Join images with ImageMagick and automate with Automator

Koffer. — Fri, 20 Jan 2023 03:54:15 +0000

Objective

Throwing images to a folder and the script generates a single image with all the images that were copied and this image is optimized.

Script with ImageMagick

The main script is create with imagemagick. I find a good example in this Link.

This is the code:

convert -append IMG_*.JPG out.jpg

The append command is the one that allows you to join the images. If you use -append joins them horizontally and if you use +append the images align vertically.

the optimized version is this one:

convert -append IMG_*.JPG -quality 65 -strip -interlace JPEG out-ok.jpg

Trigger folder

We open the Automator program in MacOS and create a new folder action

Then we select the folder where the action is to be performed.
We needd The run shell script action to add our script and the view results to get some information when we running the automator actions.

You will end with a worflow like this:

The script grow a little bit:

if [ -x /usr/libexec/path_helper ]; then eval/usr/libexec/path_helper -s`
fi
if [ -f "$HOME"/.profile ]; then
source "$HOME"/.profile
elif [ -f "$HOME"/.bash_profile ]; then
source "$HOME"/.bash_profile
elif [ -f "$HOME"/.bashrc ]; then
source "$HOME"/.bashrc
fi

convert -append /Users/username/Desktop/prueba/IMG_*.JPG -quality 65 -strip -interlace JPEG /Users/username/Desktop/prueba/out-ok.jpg
`

The if part is just a way to catch all the posible path to let Automator see the commands in zsh. You can test another options like:

sometimes with a link to this file work

source ~/.zshrc

if you want to know more about this error in Automator follow this question in stackexchange.

The second part of the script is the same script we see at begining but with absolute links to image pattern (IMG_*.JPG) and to final image.

Test the folder action in Automator and when it work without any error there is a last step.

Folder action setup

Now you need to link the folder action to the folder whe image will be process. Select the folder and with the right mouse show options. Select Folder action setup and will pop up with a warnig about Confirm Service, touch the service button.

then in the right part of this window touch the + button and select the folder action you create and save in Automator.

Check the action is selected and if all the steps are correct the script will run and images will be join in this folder!