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
This section will ask you to install & configure several services exaplained below.
22
+
23
+
### Network Requirements
24
+
25
+
#### HTTPS / HTTP Requirement
26
+
27
+
Postiz marks it's login cookies as Secure, this is called “secure context” in modern web browsers.
28
+
29
+
If you want to use an secure Login Process, you need to set up an Certificate, which can be done via Reverse Proxy like Caddy or Nginx.
30
+
31
+
If you cannot use a certificate (HTTPS), add the following environment variable to your `.env` file:
32
+
```env
33
+
NOT_SECURED=true
34
+
```
35
+
**Security Warning**: Setting `NOT_SECURED=true` disables secure cookie requirements. This should only be used in development environments or when you fully understand the security implications. Not recommended for production use.
36
+
37
+
#### Network Ports
38
+
39
+
-**5000/tcp**: for a single **single entry point** for postiz when running in a container. This is the one port your reverse proxy should talk to.
40
+
-**4200/tcp**: for the **Frontend** service (the web interface). Most users **do not** need to expose this port publicly.
41
+
-**3000/tcp**: for the **Backend** service (the API). Most users **do not** need to expose this port publicly.
42
+
-**5432/tcp**: for the **Postgres** container. Most users **do not** need to expose this port publicly.
43
+
-**6379/tcp**: for the **Redis** container. Most users **do not** need to expose this port publicly.
44
+
45
+
If you are using docker images, we recommend just exposing port 5000 to your external proxy. This will reduce the likelihood of misconfiguration, and make it easier to manage your network.
0 commit comments