[#139] Links in email notifications, when running behind nginx

I have configured gmcapsule with a custom port and I'm serving it as a backend to nginx stream. So gmcapsule is listening on port 1967 but nginx serves it on standard port 1965, which doesn't need to be declared in URL.

Mail notifications from Bubble have links reporting "gemini://bubble.domain.tld:1967/something" which would be actually correct, but that's not the real address I'm serving Bubble to, so it should be "gemini://bubble.domain.tld/something".

Any way this can be tweaked?

Mar 09 · 9 months ago

6 Comments ↓

Another similar issue with "port" I'm having is Titan editing: it fails saying the port is not correct and if I connect directly, bypassing nginx, i.e. visiting bubble.domain.tld:1967 and editing a draft, it tries to go again to port 1965 - manually adjusting the port value at this step results in a successful uplaod.

If this is not fixable, can I disable titan globally?

Thanks

Ok, sorry if I keep commenting here, but.. anytime I post something on my bubble, it redericts me to `URL:port/something` where gmcapsule is listening, bypassing nginx.

This still works because gmcapsule listens on 0.0.0.0 and the port is open, but it's not really what I want.

This kind of network configuration was never considered when I wrote Bubble, so I'm not surprised it's not quite working. There currently isn't a way to define a "public" hostname/port vs. the internal one coming from GmCapsule, but that seems like a useful feature to add.

This should fix all the redirects, too.

There is no global option to disable Titan. I could add a Bubble option for that.

Thanks. I guess there is no need to disable Titan if you're going to fix the issue wirh nginx/redirects, should be related.

Hello. Any update on this?

Not yet, but I'm planning to do a "sprint" of Bubble development soon.