PrestaShop / PrestaShop/docker
Unable to access back office on fresh docker creation
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 281
- Forks
- 190
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I launched the docker demo and the home page works. When I connect to /admin, it tells me I have to delete /install and rename /admin. I deleted /install and that cleared that message, but when I try to rename /admin I get a 500 error.
Say I rename it to /admin123 and I try to browse to /admin123
Oops! An Error Occurred
The server returned a "500 Internal Server Error".
Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.
below is the docker-compose-yaml I used - this is all I've done so far
services:
mysql:
container_name: some-mysql
image: mysql:5.7
restart: unless-stopped
ports:
- 3306:3306
environment:
MYSQL_ROOT_PASSWORD: admin
MYSQL_DATABASE: prestashop
networks:
- prestashop_network
prestashop:
container_name: prestashop
image: prestashop/prestashop:latest
restart: unless-stopped
depends_on:
- mysql
ports:
- 8080:80
environment:
DB_SERVER: some-mysql
DB_NAME: prestashop
DB_USER: root
DB_PASSWD: admin
PS_INSTALL_AUTO: 1
PS_DOMAIN: localhost:8080
ADMIN_MAIL: demo@presashop.com
ADMIN_PASSWD: prestashop_demo_1234
networks:
- prestashop_network
networks:
prestashop_network:
The docker logs just show the request, but i'll try to turn on verbose and catch the 500 error message
172.19.0.1 - - [13/Nov/2025:22:46:21 +0000] "GET /admin123/ HTTP/1.1" 500 1205 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:146.0) Gecko/20100101 Firefox/146.0"
What is the secret sauce to getting into the /admin interface using the docker demo? I'll start trying to debug, but just thought I'd log a ticket since it seems the happy path might be broken.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the provided docker-compose YAML, removing /install, renaming /admin, and requesting /admin123. Inspect the container logs with verbose error reporting enabled; done means the renamed back-office URL loads without a 500 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, mysql
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100