Search results

Please update to Platform v1.5.0 according to the documentation. After upgrade instructions, please run: dashmate ssl cleanup

Please generate a report and send it to [email protected]: dashmate doctor report

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 might get this error due to timeout: you aren't getting results in 5 seconds.

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.

Yes, correct.

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.

@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. dashmate config set platform.gateway.ssl.providerConfigs.zerossl.apiKey [YOUR-NEW-KEY] dashmate config set...

No, you don't need to if you follow the instructions from the tutorial above. We have plans to build it but we haven't had an opportunity to do it yet. Please be more specific and constructive.

Nope, the `reset` command without the `--hard` flag won't touch configuration.

I would recommend doing this until we have a new upgrade process implemented just to be on the safe side.

@qwizzie 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...

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.

I strongly recommend to run dashmate reset --keep-data (after a new version is installed) when you migrate from version 0.25

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...

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...

Hello! I wish the best to Incubator, but such as @QuantumExplorer, I don't feel I should be a part of this decision. Especially, I don't know the reasoning and consequences.

I see. Not sure it’s possible without computation on chain. We have plans to introduce VM with smart contracts and data triggers - smart contracts triggered by events form data contract providing additional validation functionality.

> A real world equivalent: To get a valid vehicle tax certificate here two other documents are needed, a valid insurance certificate and a valid roadworthiness cert (all from different sources). I was thinking along those lines, the tax doc couldn't be created without valid doc id's for the...

Hello! Thank you for your questions. Some of the things that you asking are available already, some of them are planned, some of them we probably didn't think of yet. Let me go through them one by one: > can a valid Dash address be a required field for example? You can mark as required any...