Changing Devolutions Server URL
Hi!
Our Devolutions Server instance is still called https://dps.example.com/dps and I'm considering changing it to https://passwords.example.com/dvls or something similar.
- What's the procedure to change the host name and URL path?
- Would it be possible to make the old URL still work during the transition, so we don't have to reconfigure all clients at once?
- What's the best way to create a redirect from "/" to "/dvls" and also from http to https, so it works when you type only the server same into the browser? I configured that in IIS before but it breaks every time you update DVLS.
Thank you!
All Comments (6)
Hello Daniel,
The Access URI parameter will allow you to have 2 or more different URLs to reach your DVLS.
https://docs.devolutions.net/kb/devolutions-server/knowledge-base/access-uri/#settings
About the http to https redirection, I will check with the engineering team if there is another method. Is it required on your environment to keep the http binding on the website?
For the '/' to '/dvls redirection, could it be easier to have the DVLS web application set as a web site instead? So no need to have the /dvls in the URL. The following instructions explains how to move the DVLS web application to the root of the web site.
https://docs.devolutions.net/kb/devolutions-server/how-to-articles/move-server-default-web-site-root/
Best regards,
Érica Poirier
Thank you!
I will just change the hostname and move the site to the root directory with the update to version 2023.
As far as I understand you can have multiple hostnames, but the part behind the '/' must be the same for all - unless you configure URL Rewriting or a reverse proxy or something.
> Is it required on your environment to keep the http binding on the website?
I wouldn't say it's required, but when you type just the host name in the address bar for the first time, it will only try to connect using HTTP. Only after the website has been visited once using HTTPS, the browser will store the HSTS flag and switch to HTTPS automatically in the future. Usually Websites using HSTS have an open HTTP port, but will always redirect to HTTPS. I don't know what's the best way to configure that in DVLS without updates breaking it. Also we need to make sure an update doesn't somehow disable the redirect while still allowing HTTP.
Best regards,
Daniel
I did some testing and added the new hostname. FYI one thing that came up is I needed to add the redirect URL into our Azure AD App Registration (https://dvls.example.com/dps/api/external-provider-response) so authentication works with the new hostname.
Thanks again!
Hello Daniel,
Thank you for your feedback.
We will add the information in the article that after moving the DVLS web site, we nned to modify the Access URI and, if required like your setup, update the URI in the Azure AD application.
Best regards,
Érica Poirier
Hi Erica!
I moved the installation from "/dps" to "/" following the instructions at https://docs.devolutions.net/kb/devolutions-server/how-to-articles/move-server-default-web-site-root/
After step 18 I had to edit the Access URI in the Server Settings to reflect the changes, which was not mentioned in the article.
Before that I got an error
error:invalid_token error_description:The specified token is invalid. error_uri:https://documentation.openiddict.com/errors/ID2004
Hello Daniel,
Thank you pointing that missing information.
The article will be updated by the end of the day to include a step to modify the Access URI properly.
Best regards,
Érica Poirier