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

Evonode upgrade tutorial

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...
I noticed these three commands before, but i was not sure it would trigger Dashmate to also start creating a new certificate again and store it in Dashmate ssl directory. Hopefully removing the previous certificate ID will start that process again and store new certs in the ssl directory.

By the way : where can i find that previous certificate ID ? Are we talking about any (or all) of these files in Dashmate ssl directory ?

Knipsel.JPG


Or do you mean something else ?
 
Last edited:
qwizzie said:
where can i find that previous certificate ID ?
Click to expand...
Code: 
dashmate config get platform.gateway.ssl.providerConfigs.zerossl.id
In case if you haven’t nulled it already. Also, you can go to ZeroSSL panel and see all you certs there.

Yes, these files are certificates and csr to request a next one.
 
@Ivan Shumkov

So when Zero SSL sends me an certificate expiration warning email three days before the (last) cert expires (90-90-90), i can just nullify the last certificate ID (during that grace period of three days) in Dashmate by issuing :

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

Which will let Dashmate create a new bundle.crt and private.key through a new api key within that 3 days grace period and puts them in the ssl directory, replacing the expired bundle.crt and private.key files ? Only the crs.pem file remains untouched for issuing new certs.

Am i understanding it correctly this way ?
 
Last edited:
It's a development release. Please do not install anything with pre release segment in version (`-pr.1713.2`). If you see a dash in version that means it's a pre release. Also, GitHub tells you what is the latest release and what is a pre-release.
 

Attachments

  • Screenshot 2024-08-06 at 12.09.09.png
    Screenshot 2024-08-06 at 12.09.09.png
    123.3 KB · Views: 39
i have been update dashmate to version 1.4.0

before update
dashmate 1.3.0
Platform Version 1.3.0


after update
dashmate 1.4.0
Platform Version 1.3.0 - ?? it is normal ??
 
Yes, I think you are seeing what Sam mentioned on Discord earlier (see image). He also said you could do this to double check:

Code: 
docker image inspect dashpay/drive:1 | grep org.opencontainers.image.version
 

Attachments

  • Screenshot from 2024-10-10 12-40-35.png
    Screenshot from 2024-10-10 12-40-35.png
    22.6 KB · Views: 31
thephez said:
Yes, I think you are seeing what Sam mentioned on Discord earlier (see image). He also said you could do this to double check:

Code: 
docker image inspect dashpay/drive:1 | grep org.opencontainers.image.version
Click to expand...
When do we see an official announcement of 1.4.0 in this forum ?

We only have two days to get Evonode operators to update to v1.4.0 to get this update locked in.
Time is really of the essence here. The sooner the official announcement get released in here, the better.
 
I have already updated dashmate. I want to update the OS on the server. That's why I asked how long a node can be offline to avoid getting banned
 
lucky_coin said:
I have already updated dashmate. I want to update the OS on the server. That's why I asked how long a node can be offline to avoid getting banned
Click to expand...
Depends on when quorums are restarting again. If your server is offline due to a reboot to finish some OS updates (or if you stopped dashmate for whatever reason) when they restart and happen to select your node for quorum duty, you get PoSe scored. If that happens for 2 quorums or more at the same time, you get PoSe banned.

Usually you can take a few minutes / ten minutes to update your server OS, but there will always be a risk, specially for Evonodes as there are less Evonodes on the network so you could get selected much more frequently and faster for quorum duty, compared to masternodes.
 
Last edited:
executing the command :

dashmate status platform

I receive periodically

HTTP port │ 443 ERROR
P2P port │ 26656 ERROR

after repeating the command, the problem disappears... but there were no such problems on the previous server... the port seems to be working at the same time... IPv6 seems to be disabled...
there is a feeling that the evonode is slowing down somewhere
 
tfoto said:
executing the command :

dashmate status platform

I receive periodically

HTTP port │ 443 ERROR
P2P port │ 26656 ERROR

after repeating the command, the problem disappears... but there were no such problems on the previous server... the port seems to be working at the same time... IPv6 seems to be disabled...
there is a feeling that the evonode is slowing down somewhere
Click to expand...
You might get this error due to timeout: you aren't getting results in 5 seconds.
 
tfoto said:
I changed the server provider, and the issue disappeared.
Click to expand...
Excellent! I recommend testing the port availability in case you get the `ERROR` status over time because there is always a possibility of an issue on the port check service side or somewhere in between.
 
You must log in or register to reply here.
Back
Top