-
Notifications
You must be signed in to change notification settings - Fork 154
Issue: Django admin using insecure assets #69
Comments
If you set If you are doing that, can you share details about your configuration to help investigate? |
I'm experiencing this issue too. I have a proxy in front of my taiga. I think this is a duplicate of #28. Please have a look there for a workaround. |
Resolved adding this to local.py
|
I just came across the same issue myself. I solved it by building a Docker image from the current master branch (the one on Docker Hub appears to not be up to date). You can find my image here: https://hub.docker.com/r/cmdjohnson/taiga/ I also updated Taiga to 4.2.11. If you previously ran benhutchins/taiga, then you'll have to perform some database migrations before using my image: I just
Now everything works as expected, without any other changes. |
Django admin using insecure assets
https://domain.tld/static/admin/...
.- TAIGA_SSL_BY_REVERSE_PROXY='True'
take no effect
Other services are working properly
The text was updated successfully, but these errors were encountered: