• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Evonode upgrade tutorial

Ivan Shumkov

Ivan Shumkov

New member
Dash Core Group
There are three options to proceed with upgrading Evonode. Please choose one which is suitable for you:
  • Upgrade existing Dashmate node. If you already have Evomasternode with Dashmate that meets minimum requirements then you just need to update Dashmate and obtain SSL certificates.
  • Set up a dashmate node on a new host. If you are running an Evomasternode with dashd on a host that doesn’t match minimal system requirements we recommend setting up a new server and migrating your Evomasternod. Additional considerations:
    • You need to set up a new server and keep existing and new running while the new Core node is syncing.
    • You should be able to move your current public IP to the new server. Another option is to update the IP address with ProUpServTx.
    • Your existing node will continue to serve while you do setup so any problems with the new node won’t affect the existing one.
    • You have a good opportunity to upgrade the OS and software.
  • Set up a dashmate node on the existing host. If you prefer to install Dashmate on the same node, then you should have enough disk space to store 2 core blockchains at the same time during the migration (for about 10 mins).

Prerequisites​

  1. X86-64 or ARM64 Linux host (Ubuntu is recommended) that meets minimum requirements
  2. Public IPv4 address
  3. Network configuration (firewall, security groups) allowing public access to the following TCP ports:
    1. 9999/tcp
    2. 443/tcp
    3. 26656/tcp
    4. 80/tcp (in case if you are going to use ZeroSSL).
  4. Backup of any existing Dash Core and Dashmate configuration, including private keys
  5. ZeroSSL API access key or SSL certificate for the public IPv4 address (not DNS name).

Upgrade existing Dashmate v0.25 node​

Make sure you are on the right path​


Code: 
dashmate --version

Install a new Dashmate version​

  1. Stop Dashmate:
    Code: 
    dashmate stop
  2. Install Dashmate => 1.0.2
  3. Reset previous services to ensure compatibility with a new version:
    Code: 
    dashmate reset --keep-data

Setup SSL certificate​

There are two ways to setup SSL certificates:
  • Register in the ZeroSSL service and set your API key. We recommend not using your personal email. The free plan provides free 3 certificates or 3 renewals of 1 certificate. In order to obtain the certificate you need to log-in to your zeroSSL account, press "Developer" on your left and grab the ZeroSSL API Key. Do not create a 'New certificate", just get the API key. Other plans require a credit card to pay. ZeroSSL provides API so Dashmate will update your certificates automatically.
  • You can obtain SSL certificates for your IP address using any available provider and upload certificate files. SSL Dragon and SuperbitHost are selling certificates with crypto.

ZeroSSL​

  1. Register on https://zerossl.com/
  2. Set your Zero SSL API key:
    Code: 
    dashmate config set platform.gateway.ssl.enabled true
dashmate config set platform.gateway.ssl.provider zerossl
dashmate config set platform.gateway.ssl.providerConfigs.zerossl.apiKey [YOUR-KEY]
dashmate ssl obtain

Files​

  1. Update Dashmate config:
    Code: 
    dashmate config set platform.gateway.ssl.enabled true
dashmate config set platform.gateway.ssl.provider file
  2. Copy bundle.crt and private.key to Dashmate home directory: $HOME/.dashmate/mainnet/platform/gateway/ssl

Start Dashmate node​

  1. Start the node:
    Code: 
    dashmate start
  2. Make sure the node works properly:
    Code: 
    dashmate status
dashmate status core
dashmate status platform

​

Upgrade existing Dashmate v1 node​

Make sure you are on the right path​


Code: 
dashmate --version

​

Install a new Dashmate version​

  1. Stop Dashmate:
    Code: 
    dashmate stop
  2. Install dashmate => 1.0.2
  3. Reset previous services to ensure compatibility with a new version:
    Code: 
    dashmate reset --keep-data
dashmate update

Start Dashmate node​

  1. Start the node:
    Code: 
    dashmate start
  2. Make sure the node works properly:
    Code: 
    dashmate status
dashmate status core
dashmate status platform

​

Setup a Dashmate node on a new host​

Setup a new node​

  1. Set up a new server
  2. Install Dashmate => 1.0.2

Sync a full node​

To minimize downtime we need to sync the Core blockchain without interrupting the existing node. The easiest way to achieve this is to sync a full node and then switch it to an Evomasternode.
  1. Set up a Dashmate full node to have Core synced first:
    Code: 
    dashmate setup
  2. Please choose a network and then “full node”
  3. Enable platform-required indexes and then start Dashmate to sync:
    Code: 
    dashmate config set core.indexes '["tx"]'
dashmate start
  4. Make sure it syncing:
    Code: 
    dashmate status core

Setup evo masternode​

  1. Reset configuration and services, but keep synced data:
    Code: 
    dashmate stop
dashmate reset --keep-data --hard
  2. Transfer IP address to the new node. Alternatively, you can use a new IP address and update Evomasternode service with the protx update_service_evo command.
  3. Set up an Evomasternode:
    Code: 
    dashmate setup
  4. Please choose a network -> “evo masternode” -> “already registered” -> “do not import existing data”
  5. Import keys of your existing masternode
  6. Obtain SSL certificate

Shutdown existing masternode​

  1. Please shut down your existing server or dashd process.
  2. Ensure you don’t have any startup schedulers configured (systemd, cron, etc) if you keep the node running.

Start a Dashmate node​

  1. Start a node:
    Code: 
    dashmate start
  2. Make sure the node works properly:
    Code: 
    dashmate status
dashmate status core
dashmate status platform

​

Setup a Dashmate node on the existing host​

Setup a Dashmate node​

  1. Install dashmate >= 1.0.2
  2. Set up an Evomasternode:
    Code: 
    dashmate setup
  3. Choose a network -> “evo masternode” -> “already registered” -> “import existing data”
  4. Import keys of your existing masternode
  5. Obtain SSL certificate

Stop existing dashd​

  1. Please stop the existing dashd process.
  2. Make sure you don’t have any startup schedulers configured (systemd, cron, etc).

Start a Dashmate node​

  1. Start a node:
    Code: 
    dashmate start
  2. Make sure the node works properly:
    Code: 
    dashmate status
dashmate status core
dashmate status platform

Cleanup old dashd data​

Now you can remove old dashd data if all is good
 
Last edited by a moderator:
@Ivan Shumkov

The free plan provides free 3 certificates or 3 renewals of 1 certificate. Other plans require a credit card to pay. ZeroSSL provides API so Dashmate will update your certificates automatically.
Click to expand...

Just for clarity : i created a free account with Zero SSL, got an API Key from them, Dashmate (installed on 2 different servers) created 2 free SSL certs for 90 days for two Evonodes with 2 different IP addresses under 1 API key.

Those can be auto-renewed after 90 days by Dashmate without any problem and without any action from my side ?
Maybe it will be helpfull if you could tell us more about Dashmate auto-renewal process with regards to these free 90 days SSL certs ?
 
Last edited:
qwizzie said:
@Ivan Shumkov



Just for clarity : i created a free account with Zero SSL, got an API Key from them, Dashmate (installed on 2 different servers) created 2 free SSL certs for 90 days for two Evonodes with 2 different IP addresses under 1 API key.

Those can be auto-renewed after 90 days by Dashmate without any problem and without any action from my side ?
Maybe it will be helpfull if you could tell us more about Dashmate auto-renewal process with regards to these free 90 days SSL certs ?
Click to expand...
Yeah, that's a good question, because it's not very obvious how ZeroSSL free plan works and it needs additional clarification.

They provide 3 certificates. Each for 90 days. Renewal is not "renewal" in terms of common understanding but just reissuing a new certificate. Thus, in your case, only one certificate will be updated with Dashmate in 87 days and you will get an error for the second one due to the free plan limitation. If you would have only one certificate you would get 3 "renewals" (87 + 87 + 87 in total).
 
@Ivan Shumkov

I hear these is some interest from certain Evonode owners / operators in using Zero SSL Basic plan $10 per month (i assume $120 per year) :

Knipsel.JPG


With the current Free plan Dashmate can only create a 90-Day cert (up to 3)
With the Basic plan there is both 90-Day Certificates (endless) and 1-Year Certificates (up to 3) available to users

How will Dashmate handle the Basic plan option ? Will Dashmate create a 90-day cert and endlessly renew them by creating new ones or will Dashmate first create a 1-Year cert (up to 3) and then switch to 90-day certs (endless) ?

For me personally Dashmate already created two 90 days certs through Free plan and now i need to wait untill those expired / reached end of renewal :

Knipsel.JPG

so for now i am just curious about the Basic plan and how Dashmate handles the two type of certs available to users there with regards to creating a cert through API.

Also i wonder what happens when an Evonode gets into a situation of an expired ssl cert ? What are the consequences for that Evonode ?
Will that Evonode stop receiving rewards on L2 due to TLS encryption on DAPI endpoint not working on that Evonode ?

Knipsel.JPG


With regards to updating Dashmate to a newer version, i normally issue

dashmate stop --safe (--safe flag introduced with Dashmate v1.0.0)
npm install -g dashmate
dashmate update
dashmate start

but it seems for Platform this gets extended to

dashmate stop --safe
npm install -g dashmate
dashmate reset --keep-data
dashmate update
dashmate start

Is that correct ? Does dashmate reset --keep-data need to be issued with each new npm install -g dashmate now ? (or at least after Platform activation ?)
 
Last edited:
Hi.
To install evonode I used these commands
Bash: 
curl -fsSL https://get.docker.com -o get-docker.sh && sh ./get-docker.sh
sudo usermod -aG docker $USER
newgrp docker


curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.5/install.sh | bash
source ~/.bashrc
nvm install 20
npm install -g dashmate

Please tell me how I can make an update?

VERSION
dashmate/0.25.22 linux-x64 node-v20.16.0

dashmate update - don't work ((
Bash: 
╔═════════════════╤═════════════════════════════════╤════════════╗
║ Service         │ Image                           │ Updated    ║
╟─────────────────┼─────────────────────────────────┼────────────╢
║ Dashmate Helper │ dashpay/dashmate-helper:0.25.22 │ up to date ║
║ Core            │ dashpay/dashd:20                │ up to date ║
╚═════════════════╧═════════════════════════════════╧════════════╝

#dashmate stop --safe
› Error: Nonexistent flag: --safe
› See more help with --help


#dashmate reset --keep-data
› Error: Nonexistent flag: --keep-data
› See more help with --help
 
Last edited:
@lucky_coin

Try :

dashmate stop
npm install -g dashmate
dashmate update
dashmate start

That should update your Dashmate to v1.0.2 and Core to v21.0.0

From dashmate v1.0.2 you can use commands like dashmate stop --safe and dashmate reset --keep-data if necessary.
If that does not help try :

dashmate stop
npm install -g [email protected]
dashmate update
dashmate start
 
Last edited:
#npm install -g dashmate - Failed (((((((((

Bash: 
npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm error code 1
npm error path /root/.nvm/versions/node/v20.16.0/lib/node_modules/dashmate/node_modules/diskusage
npm error command failed
npm error command sh -c node-gyp rebuild
npm error gyp info it worked if it ends with ok
npm error gyp info using [email protected]
npm error gyp info using [email protected] | linux | x64
npm error gyp info find Python using Python version 3.10.12 found at "/usr/bin/python3"
npm error gyp info spawn /usr/bin/python3
npm error gyp info spawn args [
npm error gyp info spawn args '/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
npm error gyp info spawn args 'binding.gyp',
npm error gyp info spawn args '-f',
npm error gyp info spawn args 'make',
npm error gyp info spawn args '-I',
npm error gyp info spawn args '/root/.nvm/versions/node/v20.16.0/lib/node_modules/dashmate/node_modules/diskusage/build/config.gypi',
npm error gyp info spawn args '-I',
npm error gyp info spawn args '/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
npm error gyp info spawn args '-I',
npm error gyp info spawn args '/root/.cache/node-gyp/20.16.0/include/node/common.gypi',
npm error gyp info spawn args '-Dlibrary=shared_library',
npm error gyp info spawn args '-Dvisibility=default',
npm error gyp info spawn args '-Dnode_root_dir=/root/.cache/node-gyp/20.16.0',
npm error gyp info spawn args '-Dnode_gyp_dir=/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp',
npm error gyp info spawn args '-Dnode_lib_file=/root/.cache/node-gyp/20.16.0/<(target_arch)/node.lib',
npm error gyp info spawn args '-Dmodule_root_dir=/root/.nvm/versions/node/v20.16.0/lib/node_modules/dashmate/node_modules/diskusage',
npm error gyp info spawn args '-Dnode_engine=v8',
npm error gyp info spawn args '--depth=.',
npm error gyp info spawn args '--no-parallel',
npm error gyp info spawn args '--generator-output',
npm error gyp info spawn args 'build',
npm error gyp info spawn args '-Goutput_dir=.'
npm error gyp info spawn args ]
npm error gyp ERR! build error
npm error gyp ERR! stack Error: not found: make
npm error gyp ERR! stack at getNotFoundError (/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/which/lib/index.js:16:17)
npm error gyp ERR! stack at which (/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/which/lib/index.js:77:9)
npm error gyp ERR! stack at async doWhich (/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:112:22)
npm error gyp ERR! stack at async loadConfigGypi (/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:77:7)
npm error gyp ERR! stack at async build (/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:35:3)
npm error gyp ERR! stack at async run (/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js:81:18)
npm error gyp ERR! System Linux 5.15.0-117-generic
npm error gyp ERR! command "/root/.nvm/versions/node/v20.16.0/bin/node" "/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm error gyp ERR! cwd /root/.nvm/versions/node/v20.16.0/lib/node_modules/dashmate/node_modules/diskusage
npm error gyp ERR! node -v v20.16.0
npm error gyp ERR! node-gyp -v v10.1.0
npm error gyp ERR! not ok
npm error A complete log of this run can be found in: /root/.npm/_logs/2024-07-31T19_38_52_513Z-debug-0.log
 
qwizzie said:
@lucky_coin

Try :

dashmate stop
npm install -g dashmate
dashmate update
dashmate start

That should update your Dashmate to v1.0.2 and Core to v21.0.0

From dashmate v1.0.2 you can use commands like dashmate stop --safe and dashmate reset --keep-data if necessary.
If that does not help try :

dashmate stop
npm install -g [email protected]
dashmate update
dashmate start
Click to expand...
Thank you, it all worked!
I should have install "make and g++"
 
qwizzie said:
@lucky_coin

Try :

dashmate stop
npm install -g dashmate
dashmate update
dashmate start

That should update your Dashmate to v1.0.2 and Core to v21.0.0

From dashmate v1.0.2 you can use commands like dashmate stop --safe and dashmate reset --keep-data if necessary.
If that does not help try :

dashmate stop
npm install -g [email protected]
dashmate update
dashmate start
Click to expand...
I strongly recommend to run dashmate reset --keep-data (after a new version is installed) when you migrate from version 0.25
 
Ivan Shumkov said:
I strongly recommend to run dashmate reset --keep-data (after a new version is installed) when you migrate from version 0.25
Click to expand...
@Ivan Shumkov

How about updating dashmate from v1.0.2 to future v1.0.3 or v2.0.0 : also run dashmate reset --keep-data ?
Or is this only regarding the migration from v0.25 to v1.0.2 ?

@lucky_coin

Since you were migrating from version 0.25 you will need to do dashmate reset --keep-data as well (which will reset previous services to ensure compatibility with v1.0.2)

  1. dashmate stop --safe (this should work this time as your are already on dashmate v1.0.2)
  2. npm install -g dashmate
  3. dashmate reset --keep-data
  4. dashmate update
  5. dashmate start
 
Last edited:
lucky_coin said:
#npm install -g dashmate - Failed (((((((((

Bash: 
npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm error code 1
npm error path /root/.nvm/versions/node/v20.16.0/lib/node_modules/dashmate/node_modules/diskusage
npm error command failed
npm error command sh -c node-gyp rebuild
npm error gyp info it worked if it ends with ok
npm error gyp info using [email protected]
npm error gyp info using [email protected] | linux | x64
npm error gyp info find Python using Python version 3.10.12 found at "/usr/bin/python3"
npm error gyp info spawn /usr/bin/python3
npm error gyp info spawn args [
npm error gyp info spawn args '/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
npm error gyp info spawn args 'binding.gyp',
npm error gyp info spawn args '-f',
npm error gyp info spawn args 'make',
npm error gyp info spawn args '-I',
npm error gyp info spawn args '/root/.nvm/versions/node/v20.16.0/lib/node_modules/dashmate/node_modules/diskusage/build/config.gypi',
npm error gyp info spawn args '-I',
npm error gyp info spawn args '/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
npm error gyp info spawn args '-I',
npm error gyp info spawn args '/root/.cache/node-gyp/20.16.0/include/node/common.gypi',
npm error gyp info spawn args '-Dlibrary=shared_library',
npm error gyp info spawn args '-Dvisibility=default',
npm error gyp info spawn args '-Dnode_root_dir=/root/.cache/node-gyp/20.16.0',
npm error gyp info spawn args '-Dnode_gyp_dir=/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp',
npm error gyp info spawn args '-Dnode_lib_file=/root/.cache/node-gyp/20.16.0/<(target_arch)/node.lib',
npm error gyp info spawn args '-Dmodule_root_dir=/root/.nvm/versions/node/v20.16.0/lib/node_modules/dashmate/node_modules/diskusage',
npm error gyp info spawn args '-Dnode_engine=v8',
npm error gyp info spawn args '--depth=.',
npm error gyp info spawn args '--no-parallel',
npm error gyp info spawn args '--generator-output',
npm error gyp info spawn args 'build',
npm error gyp info spawn args '-Goutput_dir=.'
npm error gyp info spawn args ]
npm error gyp ERR! build error
npm error gyp ERR! stack Error: not found: make
npm error gyp ERR! stack at getNotFoundError (/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/which/lib/index.js:16:17)
npm error gyp ERR! stack at which (/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/which/lib/index.js:77:9)
npm error gyp ERR! stack at async doWhich (/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:112:22)
npm error gyp ERR! stack at async loadConfigGypi (/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:77:7)
npm error gyp ERR! stack at async build (/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:35:3)
npm error gyp ERR! stack at async run (/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js:81:18)
npm error gyp ERR! System Linux 5.15.0-117-generic
npm error gyp ERR! command "/root/.nvm/versions/node/v20.16.0/bin/node" "/root/.nvm/versions/node/v20.16.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm error gyp ERR! cwd /root/.nvm/versions/node/v20.16.0/lib/node_modules/dashmate/node_modules/diskusage
npm error gyp ERR! node -v v20.16.0
npm error gyp ERR! node-gyp -v v10.1.0
npm error gyp ERR! not ok
npm error A complete log of this run can be found in: /root/.npm/_logs/2024-07-31T19_38_52_513Z-debug-0.log
Click to expand...
When you install the NPM package it builds some of the dependencies from sources so you need to have build tools installed. We recommend installing Dashmate with a Debian package. It's already self-contained. We are going to introduce Debian repo and package signing for secure distribution soon.
 
@qwizzie
qwizzie said:
How will Dashmate handle the Basic plan option ? Will Dashmate create a 90-day cert and endlessly renew them by creating new ones or will Dashmate first create a 1-Year cert (up to 3) and then switch to 90-day certs (endless) ?
Click to expand...
There is no difference for Dashmate which Plan you are using. DCG uses the Basic Plan for testnet, for example. ZeroSSL API is the same for both Plans. At least endpoints what we use. Dashmate always registers 90-day certificates and then renews them 3 days in advance of expiration time.

qwizzie said:
With regards to updating Dashmate to a newer version, i normally issue

dashmate stop --safe (--safe flag introduced with Dashmate v1.0.0)
npm install -g dashmate
dashmate update
dashmate start

but it seems for Platform this gets extended to

dashmate stop --safe
npm install -g dashmate
dashmate reset --keep-data
dashmate update
dashmate start

Is that correct ? Does dashmate reset --keep-data need to be issued with each new npm install -g dashmate now ? (or at least after Platform activation ?)
Click to expand...

First of all, I wouldn't recommend using NPM as a distribution channel for production. As I wrote above, we recommend installing Dashmate with a Debian package. It's already self-contained. We are going to introduce a Debian repo to ease upgrade and package signing for secure distribution soon.

Regarding dashmate reset --keep-data. We faced some issues upgrading Dashmate 0.25. I believe It's related to the incompatibility of docker containers created with the previous version of the docker-compose config and the new version. There are some breaking changes that docker can't handle properly. So what we recommend to do is to remove all existing containers before you start the new one. In the future, we will provide a more user-friendly upgrade process.
 
qwizzie said:
How about updating dashmate from v1.0.2 to future v1.0.3 or v2.0.0 : also run dashmate reset --keep-data ?
Or is this only regarding the migration from v0.25 to v1.0.2 ?
Click to expand...
I would recommend doing this until we have a new upgrade process implemented just to be on the safe side.
 
Do we need to mess with our existing ZeroSSL setup if we're just updating Dashmate to run latest version?

I also don't understand why we have to reinstall dashmate, why isn't there an automatic update made?
 
Last edited:
TanteStefana said:
Do we need to mess with our existing ZeroSSL setup if we're just updating Dashmate to run latest version?
Click to expand...
No, you don't need to if you follow the instructions from the tutorial above.

TanteStefana said:
I also don't understand why we have to reinstall dashmate, why isn't there an automatic update made?
Click to expand...
We have plans to build it but we haven't had an opportunity to do it yet. Please be more specific and constructive.
 
@Ivan Shumkov

New Dashmate feature request.

Lets say Evonode operators have a Free tier account registered with Zero SSL for one Evonode / ip address, which ends after 9 months (3x 90 days).
This Free account can then no longer be used by Dashmate to create new certs, so Evonode operators will need to close it and create a new Free account for another 9 months (3x 90 days certs).

This will most likely need to be registered with a different emailadres (personally i am thinking about registering a new anonymous main gmailaccount and then use anonymous gmail aliases with certificate expiration emails from Zero SSL going to the main gmailaccount). This new Free tier account will most likely get Evonode operators a new Zero SSL api key, which need to be adjusted in Dashmate.

This could be done by creating a new Dashmate certificate renewel command that will asks for the new zero ssl api key and then initiate a new ssl certificate setup similar to what is happening during dashmate setup (basically from the part where Dashmate asks for the zero ssl api key and then start to create a zero ssl certificate through api and stores ssl certificate files in dashmate ssl folder). This new process should overwrite the expired certs files in the ssl directory.

Thoughts ?
 
Last edited:
@qwizzie I have good news for you. We already have this command: `dashmate ssl obtain`. What you should do is set a new API key and remove the previous certificate ID.

Code: 
dashmate config set platform.gateway.ssl.providerConfigs.zerossl.apiKey [YOUR-NEW-KEY]
dashmate config set platform.gateway.ssl.providerConfigs.zerossl.id null
dashmate ssl obtain
 
Ivan Shumkov said:
@qwizzie I have good news for you. We already have this command: `dashmate ssl obtain`. What you should do is set a new API key and remove the previous certificate ID.

Code: 
dashmate config set platform.gateway.ssl.providerConfigs.zerossl.apiKey [YOUR-NEW-KEY]
dashmate config set platform.gateway.ssl.providerConfigs.zerossl.id null
dashmate ssl obtain
Click to expand...
Tested and works good! Thnx Ivan.
 
You must log in or register to reply here.
Back
Top