Devolutions ForumDevolutions Forum

Changing Access URI of Docker Installation

Changing Access URI of Docker Installation

avatar
siniawskijj

I have a 2025.3 instance running in docker, and I am able to connect and log into it.

My problem is that I would like to run this behind an nginx reverse proxy and have nginx had all of the ssl certificate and everything behind that run in http. The reverse proxy sends data to the DVLS over port 5000, and so when I have DVLS configured to talk over port 5000 and http, going to http://dvls.domain.com:5000 works, but going to https://dvls.domain.com doesnt and I get
Error during OAuth server initialization. Please contact your administrator.

I assume this is because the Access uri, as showing in the settings page is http://dvls.domain.com:5000 and doesnt match.

but it seems I am unable to change, or the switch is not documented on how to update the access URI for the docker installation.

All Comments (1)

avatar
Michel Audi

Hello Justin,
Thank you for reaching to our forum.

This error is typically caused by a mismatch between the public URL users browse to and the DVLS “Access URI” (DVLS uses this as the OAuth redirect/base URL). In your case, DVLS is currently advertising itself as http://dvls.domain.com:5000, while users access it as https://dvls.domain.com.
To resolve this in a Docker deployment, set DVLS to generate its base URL using the external/public values (the reverse proxy URL), then restart the container. In practice, update the DVLS container environment variables so they reflect the public URL:

  • HOSTNAME=dvls.domain.com
  • WEB_SCHEME=https
  • PORT=443

After restarting DVLS, confirm in the DVLS settings page that the Access URI now shows:
https://dvls.domain.com
(no :5000, since that port is only internal between nginx and DVLS)
Also make sure nginx forwards the proxy headers DVLS needs to understand the external scheme/host:

  • Host: dvls.domain.com
  • X-Forwarded-Proto: https
  • X-Forwarded-Host: dvls.domain.com
  • X-Forwarded-Port: 443

If you are publishing DVLS on a non-standard external port or behind a URL path (for example https://dvls.domain.com/dvls), the Access URI must match that exact public URL.
If you share your docker-compose (or docker run) environment block and your nginx server/location block, I can point out exactly what needs to be adjusted.

Best regards,

Michel Audi