The Redirect URI in Client Credentials\Redirect URI is still displaying incorrectly.
Is this the correct location for the site_config.json?
No, it’s going to go in your sites folder in
/home/frappe/frappe-bench/sites/your-site-name-here/site_config.json
Best way to set this is with the bench command from the folder where your docker-compose.yaml lives:
docker compose exec backend bench set-url-root your-site-name-here https://your-server-url-here
OK I am not sure why or how this is even working but the path to bench is:
/home/administrator/.local/share/pipx/venvs/frappe-bench/lib/python3.12/site-packages.
There is no compose.yaml or sites folder in there.
/home/administrator/frappe_docker`
contains a compose.yaml. The contents of that file state:
x-backend-defaults: &backend_defaults<<: [*depends_on_configurator, *customizable_image]volumes:
sites:/home/frappe/frappe-bench/sites ←- This path does not exist.
websocket:<<: [*depends_on_configurator, *customizable_image]platform: linux/amd64command:
/home/frappe/frappe-bench/apps/frappe/socketio.js ←- This path does not exist.volumes:
sites:/home/frappe/frappe-bench/sites ←- This path does not exist.
At the end of the file is this:
ERPNext requires local assets access (Frappe does not)
volumes:sites:
What is the point of this section?
Docker Root Directory is:
/var/snap/docker/common/var-lib-docker
Docker service status:
docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; preset: enabled)
Active: active (running) since Tue 2025-12-16 15:27:21 PST; 1 day 20h ago
Docker running containers:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2edd1de8ed51 frappe/erpnext:v15.91.1 “nginx-entrypoint.sh” 8 days ago Up 44 hours 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp frappe_docker-frontend-1
310c8efbed8a frappe/erpnext:v15.91.1 “node /home/frappe/f…” 8 days ago Up 44 hours frappe_docker-websocket-1
119151ecf460 redis:6.2-alpine “docker-entrypoint.s…” 8 days ago Up 44 hours 6379/tcp frappe_docker-redis-queue-1
775ee0534a21 frappe/erpnext:v15.91.1 “bench worker --queu…” 8 days ago Up 44 hours frappe_docker-queue-long-1
d9cd1c5cfbb7 mariadb:10.6 “docker-entrypoint.s…” 8 days ago Up 44 hours (healthy) 3306/tcp frappe_docker-db-1
385af853194f redis:6.2-alpine “docker-entrypoint.s…” 8 days ago Up 44 hours 6379/tcp frappe_docker-redis-cache-1
aa6876186cba frappe/erpnext:v15.91.1 “/home/frappe/frappe…” 8 days ago Up 44 hours frappe_docker-backend-1
2b13d2324060 frappe/erpnext:v15.91.1 “bench schedule” 8 days ago Up 44 hours frappe_docker-scheduler-1
91217b2b0706 frappe/erpnext:v15.91.1 “bench worker --queu…” 8 days ago Up 44 hours frappe_docker-queue-short-1
All of that said I have in path /var/lib/docker/volumes/frappe_docker_sites/_data and file called common_site_config.json which contains the following:
{
“db_host”: “db”,
“db_port”: 3306,
“default_site”: “frontend”,
“redis_cache”: “redis://redis-cache:6379”,
“redis_queue”: “redis://redis-queue:6379”,
“redis_socketio”: “redis://redis-queue:6379”,
“socketio_port”: 9000
}
I am adding the hostname to this file and testing now.
and of course that didn’t work. Does frappe have a place to view where its running directories are, like IIS or Apache etc though the portal?
OK I finally got this working. In my travels I ran across portainer. I viewed the container details, and the frappe_site_name_header was called “frontend”.
I used your command but modified:
docker compose exec backend bench set-url-root frontend https://myserver and the Redirect URI changed to https://myserver.
I understand the commands, but I don’t understand why the site_config.json located in /var/lib/docker/volume/frappe_docker_sites/_data/frontend which is listed above with correct syntax did not work. Clearly it has to be running under “frontend” as your command worked with that name. To that end I am unclear as to why it is using “frontend”.
Maybe someone with more docker linux experience can explain to me what the hell is going on.
Docker is different. Looking around for your container’s files in the host file system is not the way to go about things. It’s like trying to install a screw with a hammer. If you want to use docker for frappe (and it’s FAR from the only way to do frappe), then you’ll need to learn container basics or you’ll find yourself banging your head against the wall. Here’s what I’d suggest from my personal experience. Use a bare metal server or virtual machine to get started with frappe instead of docker. Then you only need to learn ONE new thing instead of TWO new things at once. Then, in your free time, experiment with docker, for learning and for fun- but not with frappe, do basic stuff like single containers, learn how volumes work to persist data, learn how compose files function with easy stuff, etc. from docker documentation. Once you’re reasonably comfortable with how frappe works and how docker works, you can combine them and you will have torn out far fewer hairs on your head. =)
Thanks, my understanding of how docker backend functioned was off. I understand now and explains a ton of why I couldn’t find what I was looking for. Thanks for the help and insights 
We the community are here to help you on your erpnext journey
We only request that you help others the same way you were helped and spread the FOSS love
Let us know if you need anything else