Doron Katz
Doron Katz
PPostiz
Created by Support on 11/9/2024 in #💭│community-support-tickets
Ticket: Blank Pages in Browser with Postiz & Caddy Proxy Setup
Did you figure it out ?
4 replies
PPostiz
Created by Support on 12/3/2024 in #💭│community-support-tickets
Ticket: Sign In/Up Redirection and Authentication Issues
What was the fix
58 replies
PPostiz
Created by Support on 1/17/2025 in #💭│community-support-tickets
Ticket: Docker+Caddy setup login issue; no browser error on access
Complete set of steps and log: HI folks * Goal: Setup and login to local instance of service * Environment: MacOS running Docker, and caddy * Changed: Installed via docker-compose, setting environment in docker-compose.yml, on port 5001:5000. Caddyfile:
:443 {
bind tailscale/social
tls {
get_certificate tailscale
}
tailscale_auth
reverse_proxy * localhost:5001
}
:443 {
bind tailscale/social
tls {
get_certificate tailscale
}
tailscale_auth
reverse_proxy * localhost:5001
}
* * Results*: While I can access the URL, and register even, when I login, it doesn’t do anything. Doesn’t give me a browser error or anything. The log is as follows:


The database is already in sync with the Prisma schema.


▲ Next.js 14.2.22
- Local: http://localhost:4200

✓ Starting...
✓ Ready in 203ms


[Nest] 192 - 01/17/2025, 1:55:03 AM LOG [NestFactory] Starting Nest application...
Email service provider: resend
[Nest] 192 - 01/17/2025, 1:55:03 AM LOG [InstanceLoader] BullMqModule dependencies initialized +13ms
[Nest] 192 - 01/17/2025, 1:55:03 AM LOG [InstanceLoader] DatabaseModule dependencies initialized +0ms
[Nest] 192 - 01/17/2025, 1:55:03 AM LOG [InstanceLoader] AppModule dependencies initialized +0ms
[Nest] 186 - 01/17/2025, 1:55:03 AM LOG [NestFactory] Starting Nest application...
Email service provider: resend 2ms


2025-01-17 01:55:06,133 INFO success: caddy entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)
2025-01-17 01:55:06,133 INFO success: cron entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)
2025-01-17 01:55:06,133 INFO success: frontend entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)
2025-01-17 01:55:06,134 INFO success: workers entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)
2025-01-17 01:55:13,185 INFO success: backend entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)


The database is already in sync with the Prisma schema.


▲ Next.js 14.2.22
- Local: http://localhost:4200

✓ Starting...
✓ Ready in 203ms


[Nest] 192 - 01/17/2025, 1:55:03 AM LOG [NestFactory] Starting Nest application...
Email service provider: resend
[Nest] 192 - 01/17/2025, 1:55:03 AM LOG [InstanceLoader] BullMqModule dependencies initialized +13ms
[Nest] 192 - 01/17/2025, 1:55:03 AM LOG [InstanceLoader] DatabaseModule dependencies initialized +0ms
[Nest] 192 - 01/17/2025, 1:55:03 AM LOG [InstanceLoader] AppModule dependencies initialized +0ms
[Nest] 186 - 01/17/2025, 1:55:03 AM LOG [NestFactory] Starting Nest application...
Email service provider: resend 2ms


2025-01-17 01:55:06,133 INFO success: caddy entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)
2025-01-17 01:55:06,133 INFO success: cron entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)
2025-01-17 01:55:06,133 INFO success: frontend entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)
2025-01-17 01:55:06,134 INFO success: workers entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)
2025-01-17 01:55:13,185 INFO success: backend entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
5 replies