Replies: 2 comments 1 reply
-
If you set it to localhost:port for example but then all urls created by the client (ex. api requests) and server (ex. links in emails) will point to localhost which is probably not what you want. That said I do plan on pushing an update soon that will make make configuring this parameter optional which should make this easier. |
Beta Was this translation helpful? Give feedback.
-
[..]
Did you work out how to get this working? I struggled too initially, but have it working properly now with Docker and using Nginx as a reverse proxy. |
Beta Was this translation helpful? Give feedback.
-
Hello there, im struggling to setup rallly on my homeserver. I'm fairly new to selfhosting and want to learn in the process.
My problem is as follows:
If i setup rallly on my homeserver with >NEXT_PUBLIC_BASE_URL=PrivateIP:Port< i can use it in my homenet. Normally i now just setup a reverse proxy (ngninx proxy manager) to expose the program to the internet, so that my friends can use the rallly instance.
I setup my domain name and forward to >privateIP:Port<. In other selfhosted projects i can now request a new SSL certificate.
That process won't work in rallly.
I read in other threads that:
im really stuck here :(
Best regards
Beta Was this translation helpful? Give feedback.
All reactions