There is a problem with the validation of the oauth discovery document. Please check your configuration (ex: AccessUri)

Hello,

Thank you for your feedback.

This error could be related to an incorrect Access URI format. Could you please confirm that you are using the right one to reach your DVLS instance?
https://docs.devolutions.net/server/knowledge-base/knowledge-base-articles/access-uri-format

Let us know if that helps.

Best regards,

Thanks for the quick reply.
How do I connect the Devolution Server console to the Docker installation?

Hello cusan,

Thank your for your question,the Devolutions Server Console does not connect to a Docker installation. The Console manages the IIS metabase, so it applies only to instances installed on Windows under IIS; there is no Console for the container. On Docker, the Access URI is set from the container's environment variables instead, which is why the article you were pointed to does not match your deployment.
That is most likely the cause of the error as well. The documented Docker procedure starts the container with HOSTNAME=localhost, WEB_SCHEME=https and PORT=5000, so the instance is initialized with localhost on port 5000 as its Access URI. The server then builds the URLs in its OAuth discovery document from that stored value, while the web page validates them against the address you actually typed. Open the page under any other address, such as the server's name or IP, a different port, or plain http, and the two no longer match, which is the message you quoted.
Two things to try, in this order:

1. On the Docker host itself, open the address given in step 4 of the deployment article and confirm the login page appears. If it does, the installation is sound and only the address you were using is wrong.
2. To reach the instance under another name, recreate the runtime container with that name in its environment, keeping the same database and volume arguments you used before. Set both HOSTNAME=your.server.name and EXTERNAL_WEB_HOSTNAME=your.server.name. The second is what makes the container rewrite the stored Access URI when it starts; the first is the name the container issues its self-signed certificate for, so leaving that one on localhost would give you a certificate warning at the new address. EXTERNAL_WEB_SCHEME and EXTERNAL_WEB_PORT do the same for the scheme and the port if you place the instance behind a reverse proxy.

The startup rewrite needs EXTERNAL_WEB_HOSTNAME specifically, and it is available on 2026.1.13 and newer, so please update the image first if yours is older. You will not find that variable in the table on the page below, but the container does honour it.
The other variables are listed here: https://docs.devolutions.net/server/knowledge-base/how-to-articles/devolutions-server-docker-deployment/advanced-docker-configuration-for-devolutions-server
Best regards,
Michel

root@container:~# docker volume create dvls-init-data
dvls-init-data
root@container:~# docker run --rm \
>   -e DATABASE_HOST=10.0.8.2 \
>   -e DATABASE_NAME=doc-dvls-0 \
>   -e DATABASE_USERNAME=DVLS_O \
>   -e DATABASE_PASSWORD='SECACCESSPASS' \
>   -e HOSTNAME=localhost \
>   -e WEB_SCHEME=https \
>   -e PORT=5000 \
>   -e EXTERNAL_WEB_HOSTNAME=dvls.external-access.de \
>   -e EXTERNAL_WEB_SCHEME=https \
>   -e EXTERNAL_WEB_PORT=443 \
>   -e DVLS_ADMIN_USERNAME=aDmin972 \
>   -e DVLS_ADMIN_PASSWORD='SECACCESSPASS' \
>   -e DVLS_INIT=true \
>   -v dvls-init-data:/opt/devolutions/dvls/App_Data \
>   -p 5000:5000 \
>   devolutions/devolutions-server:release-2026.3
Generating self-signed TLS certificate for 'localhost'...
Initializing Devolutions Server...
Initialization completed successfully.
Launching Devolutions Server: https://dvls.external-access.de/

Hello, and thank you for the detailed response.
I've now made some more adjustments to my Dockerfile.
Now I can successfully access my server from outside the network.

Thank you for your help.