fix(blueprint): rybbit v1.2.0

[nktnet1]

Changes:

• remove /api stripping
• remove caddy reverse proxy
• added clickhouse config in volume mount

Release notes:

• https://github.com/rybbit-io/rybbit/releases/tag/v1.0.0

Migration guide:

• https://www.rybbit.io/docs/v1-migration

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	d82b1e5

[nktnet1]

@Siumauricio can you help test Rybbit's v1.0.0 migration?

I tried it and everything works only when "isolated compose" is turned off, otherwise I get a 504 Gateway error.

This is similar to the issue I faced with the seafile template (#135), where I get a 504 gateway timeout when accessing the rybbit_backend service.

[Siumauricio]

Check the video is working fine
https://github.com/user-attachments/assets/2f9b4f3d-c9c7-45b8-9258-60d4fcb8fb1e

[nktnet1]

Check the video is working fine https://github.com/user-attachments/assets/2f9b4f3d-c9c7-45b8-9258-60d4fcb8fb1e

Thanks for setting it up @Siumauricio - however, that's only the frontend client right?
Are you able to sign up? I think the issue is more so with the backend.

You could also try visiting

• https://your.domain/api/health

to see if it can be reached.

[Siumauricio]

Check the video is working fine https://github.com/user-attachments/assets/2f9b4f3d-c9c7-45b8-9258-60d4fcb8fb1e

Thanks for setting it up @Siumauricio - however, that's only the frontend client right? Are you able to sign up? I think the issue is more so with the backend.

You could also try visiting

• https://your.domain/api/health

to see if it can be reached.

It returns 'Ok'

Additionally when i register I see this 401 errors...

[nktnet1]

That's odd...

I followed your directions in the video and removed all the network configurations, and things are working correctly now, even for sign-up.

I'm using a custom domain though, so will try again with default traefik.

[nktnet1]

@Siumauricio alright, I was able to reproduce your error with traefik domains.

I can create a user, but not organisations.

Only when I switched to using HTTPS on my own domain that I go past the organisation state. Not sure if this is some better-auth quirks.

[Siumauricio]

Is the service likely to have certain restrictions on proxy and url handling?

[nktnet1]

Is the service likely to have certain restrictions on proxy and url handling?

not 100% sure. What I have deduced is:

1. Before removing the "networks" configuration in docker-compose.yaml (0b44930)

   1. isolated deployment enabled
      • ❌ backend always unreachable (gets 504 Gateway Timeout)
   2. isolated deployment disabled
      • ✅ works with traefik domain (HTTP)
      • ✅ works with custom domain (HTTPS)

2. After removing the "networks" configurations (0b44930)

   1. isolated deployment enabled
      • ⚠️ partially works with traefik domain (HTTP), can create users, but not organizations (gets 401 Unauthorized)
      • ✅ works with custom domain (HTTPS)
   2. isolated deployment disabled
      • ❌ backend always unreachable (visiting /api/health always redirects to client)

Pretty confusing 😕.

[nktnet1]

@Siumauricio I got confirmation that Rybbit only supports HTTPS, so issues with traefik is not within scope:

• gateway timeout on dokploy rybbit-io/rybbit#322 (comment)

I've updated the documentation in 1e79ddf.

I think the PR is ready to merge - it was confirmed to be working by another user here:

• gateway timeout on dokploy rybbit-io/rybbit#322 (comment)