You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 7, 2024. It is now read-only.
I have tried for a while to get my strapi dashboard showing when I go to /d/admin, but it won't work. I have been able to setup the upstream so that strapi detects the request, but instead of going to the admin dashboard it simply tries to get some content with the address /d/admin.
I am running strapi in docker and behind nginx reverse proxy.
This seems to be an issue with Strapi since I cannot change the url and make strapi understand it. Or is it because I don't use the module.exports function where you declare a url for the admin panel? (If that's the case, please give me a guide since I cannot find any on how to do that with docker-compose). What I mean is that I don't see any tutorial on how to add those server settings to docker-compose when starting the docker containers.
I have tried for a while to get my strapi dashboard showing when I go to /d/admin, but it won't work. I have been able to setup the upstream so that strapi detects the request, but instead of going to the admin dashboard it simply tries to get some content with the address /d/admin.
I am running strapi in docker and behind nginx reverse proxy.
This seems to be an issue with Strapi since I cannot change the url and make strapi understand it. Or is it because I don't use the module.exports function where you declare a url for the admin panel? (If that's the case, please give me a guide since I cannot find any on how to do that with docker-compose). What I mean is that I don't see any tutorial on how to add those server settings to docker-compose when starting the docker containers.
https://stackoverflow.com/questions/68292999/strapi-w-docker-compose-how-do-i-create-a-config-server-to-attach-strapi-to-a?noredirect=1#comment120756199_68292999
The text was updated successfully, but these errors were encountered: