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
The application was set up with HTTPS, like recommended on the the docks. Im using NGINX proxy manager. However, the application does not perform the login properly. We dont have any kind of error on the browser console nor the container logs.
👟 Reproduction steps
The application was set up with the following docker compose file
name: Postizservices:
postiz:
image: ghcr.io/gitroomhq/postiz-app:latestcontainer_name: postizrestart: alwaysenvironment:
# You must change these. Replace `postiz.your-server.com` with your DNS name - what your web browser sees.MAIN_URL: "https://postiz.darth-maul.duckdns.org"FRONTEND_URL: "https://postiz.darth-maul.duckdns.org"NEXT_PUBLIC_BACKEND_URL: "https://postiz.darth-maul.duckdns.org/api"JWT_SECRET: "random string that is unique to every install - just type random characters here!"# These defaults are probably fine, but if you change your user/password, update it in the# postiz-postgres or postiz-redis services below.DATABASE_URL: "postgresql://postiz-user:postiz-password@postiz-postgres:5432/postiz-db-local"REDIS_URL: "redis://postiz-redis:6379"BACKEND_INTERNAL_URL: "http://localhost:3000"IS_GENERAL: "true"# Required for self-hosting.# The container images are pre-configured to use /uploads for file storage.# You probably should not change this unless you have a really good reason!STORAGE_PROVIDER: "local"UPLOAD_DIRECTORY: "/uploads"NEXT_PUBLIC_UPLOAD_DIRECTORY: "/uploads"volumes:
- postiz-config:/config/
- postiz-uploads:/uploads/ports:
- 5000:5000networks:
- postiz-networkdepends_on:
postiz-postgres:
condition: service_healthypostiz-redis:
condition: service_healthypostiz-postgres:
image: postgres:17-alpinecontainer_name: postiz-postgresrestart: alwaysenvironment:
POSTGRES_PASSWORD: postiz-passwordPOSTGRES_USER: postiz-userPOSTGRES_DB: postiz-db-localvolumes:
- postgres-volume:/var/lib/postgresql/datanetworks:
- postiz-networkhealthcheck:
test: pg_isready -U postiz-user -d postiz-db-localinterval: 10stimeout: 3sretries: 3postiz-redis:
image: redis:7.2container_name: postiz-redisrestart: alwayshealthcheck:
test: redis-cli pinginterval: 10stimeout: 3sretries: 3volumes:
- postiz-redis-data:/datanetworks:
- postiz-networkvolumes:
postgres-volume:
external: falsepostiz-redis-data:
external: falsepostiz-config:
external: falsepostiz-uploads:
external: falsenetworks:
postiz-network:
external: false
👍 Expected behavior
it should login normally as Im meeting all the specifications on the documenation.
It should at least throw some error message, so I could undestant what is wrong
👎 Actual Behavior with Screenshots
The applications seems to redirect and go back the current screen.
📜 Description
The application was set up with HTTPS, like recommended on the the docks. Im using NGINX proxy manager. However, the application does not perform the login properly. We dont have any kind of error on the browser console nor the container logs.
👟 Reproduction steps
The application was set up with the following docker compose file
👍 Expected behavior
it should login normally as Im meeting all the specifications on the documenation.
It should at least throw some error message, so I could undestant what is wrong
👎 Actual Behavior with Screenshots
The applications seems to redirect and go back the current screen.
Heres a video showing the behaviour
https://youtu.be/6qY2rO4wTqc
💻 Operating system
Linux
🤖 Node Version
Im using the docker compose file from the docs
📃 Provide any additional context for the Bug.
It seems to me anything related to tokens or redirection
👀 Have you spent some time to check if this bug has been raised before?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: