Good morning, folks.
I believe you may have a huge boo-boo in your release notes that I saw in the new beta release I updated to:
"Breaking changes: Changed license validation URL from https://api.devolutions.com to https://quoting.devolutions.com. Make sure your network allows access to this URL."
Shouldn't those URL's be .NET instead of .COM?
--- Chuck
Overgaard, AZ (-7 MST / Zulu Year-Round)
RDM Version: 2025.3.11.0 64-Bit - MSSQL - Daily Usage
RDM Version: 2025.2.28.0 64-Bit - MSSQL - VM
Hello,
Thank you for your feedback.
It's .COM for these 2 URLs according to our documentation. Ensure your firewall or proxy allows access to this URL https://quoting.devolutions.com/ since you are using 2025.1!
https://docs.devolutions.net/rdm/kb/knowledge-base/internet-endpoints-access/
Best regards,
Érica Poirier
Hello,
Thank you for your feedback.
It's .COM for these 2 URLs according to our documentation. Ensure your firewall or proxy allows access to this URL https://quoting.devolutions.com/ since you are using 2025.1!
https://docs.devolutions.net/rdm/kb/knowledge-base/internet-endpoints-access/
Best regards,
The rest of your site is available via .NET, and in fact, looks like your website has 301's from .COM to .NET.
For those of us in huge organizations that have to spell out entries for all destination sites, and have to go through governmental approvals for changes, can you **PLEASE** stick with one or the other?
I currently have .NET approved open in our firewall, and won't approve .COM.
So what are my options I will encounter when it can't communicate because of firewalls not opened.
This should be a better practice from Devolutions.
--- Chuck
Overgaard, AZ (-7 MST / Zulu Year-Round)
RDM Version: 2025.3.11.0 64-Bit - MSSQL - Daily Usage
RDM Version: 2025.2.28.0 64-Bit - MSSQL - VM
Hello,
Thank you for your feedback.
For the licensing validation, you can still download the .lic file from the Devolutions Portal and import it in RDM.
I will transfer your comment to the development team.
Best regards,
Érica Poirier
Hello,
Thank you for your feedback.
For the licensing validation, you can still download the .lic file from the Devolutions Portal and import it in RDM.
I will transfer your comment to the development team.
Best regards,
Perfect!
Who will be responsible for associating our corporate license to my Portal ID since I maintain our RDM software?
See how much of a PITA this will become for your end-users?
--- Chuck
Overgaard, AZ (-7 MST / Zulu Year-Round)
RDM Version: 2025.3.11.0 64-Bit - MSSQL - Daily Usage
RDM Version: 2025.2.28.0 64-Bit - MSSQL - VM
Hello,
Thank you for your feedback.
I got the following information from our developer team. The reason the URL changes from .net to .com is due to the decommissioning of our former CRM API, as licensing has been transferred to quoting-API. Additionally, Lucid uses .com and has never supported .net.
The rule we are trying to follow:
In your scenario, adding devolutions.com to your allowed URLs would be the best solution.
Let us know if you have any more questions about this.
Best regards,
Érica Poirier