Trouble with backend/server PUBLIC_URL: either 500 error or no admin panel

[keunes]

Hello,

I've recently set up AdventureLog using Docker compose, with Nginx running bare metal on my RaspberryPi. I've got it working, but have this issue:
When clicking on the 'Admin panel' link I get redirected to http://localhost:48644/admin/ which doesn't work because I'm not accessing from localhost.

I suppose this link is coming from the server/backend's PUBLIC_URL environment variable, which currently has the value http://localhost:48644

However, when I change the server/backend's PUBLIC_URL to be the front-end's ORIGIN which is https://adventures.mydomain.nl in my case, then when opening https://adventures.mydomain.nl I get a '500' error.

From comments like #639 (reply in thread) and #361 (reply in thread) I get the impression that I either need to set up port forwarding for the back-end or set up a dedicated back-end domain. Both I would like to avoid, because it'd mean I would have to manage additional ports on my router or manage additional domains in my nameserver and Nginx.

Is there any way to work around this?

[seanmorley15]

Hi @keunes, typically for setups I recommend exposing both the frontend and backend services on separate subdomains/ports to make it clear. This will clear any confusion and make it a simpler config. Let me know if you have any questions!

[keunes]

Thanks @seanmorley15. I don't have a technical background so I can't really see why it's set up this way, but as a (beginning) self-hoster it would be great not to maintain additional ports or (sub-domains) for a back-end (because that means setting up extra DNS records and/or ports, Nginx entries).

I managed (with the help of GenAI) to make the back-end stuff available from the main domain (see #639 (reply in thread)) but it seems I'm now hitting an issue with saving content - the same as #634.

Do you think there's any chance of having an 'all in one' solution or set-up? If yes, I'd be very happy to add a feature/improvement request for this. You note that having two domains makes for a simpler config - does that mean that it should already be possible?

Many thanks for your work on AdventureLog!

[seanmorley15]

@keunes, right now with the way the app is structured, having 2 separate subdomains is easiest because of the different frontend/backend apps using totally different languages. Although it is possible with some special config like in #639 which I just took a look at and is great, but is it more work for most people. I haven not tested the "all in one" setup but if you want to share your compose I can try and double check it, it would say its important to make sure that the PUBLIC_URL, FRONTEND_URL, ORIGIN, and CSRF_TRUSTED_ORIGINS are all the same in this case. Let me know!