The redirect is happening because the asset is not found (Ghost auto redirects all routes to trailing-slash).
You say you’re using Docker but haven’t told us anything about the specifics of your setup, that might be a good place to start for someone to be able to help you. Docker isn’t a supported platform so you may need to wait for someone in the community who knows it to give you some ideas of where to start digging into what’s gone wrong.
The setup:
I am running ghost:latest ( was running 1.24 before, which had the same problem ) inside a docker container. There is a router in front of it which checks if the url starts with blog. and then forwards the complete request to ghost.
This setup worked perfectly fine for a couple of years but somehow now it has this issue on the admin page.
What baffles me is that the browser decides to request /assests/… and not /ghost/assests even though its a relative url.
it sounds like your local router was somehow not allowing Ghost to do it’s normal trailing slash redirect, typically any request to /ghost would return a 301 to /ghost/
Yes, it is weird that this worked in the past though. Might be that the bookmark I normaly used already included a trailing slash or is this behaviour a recent addition?
Anyways, thank you for your help and this can be closed.