huston9

I have tried accessing both by my local network and remotely via Tailscale. Neither case has worked for me so far.

I did that - I also set ACCOUNT_REGISTRATION=true, but no luck yet. Am I supposed to be doing anything with the JWT_SECRET variable? Thanks for the advice btw; this seems...

> `export HTTP_ALLOWED=true` fixes it As in enter that line into my environmental variables? I'm new-ish to Docker, and am unfamiliar with how to use `export` in a compose file.

Tried that, but it didn't work. Here is the environmental variables section of my docker-compose.yml: ``` environment: - JWT_SECRET=password # will use randomUUID() if unset - ACCOUNT_REGISTRATION=true - export HTTP_ALLOWED=true...

Ok, so taking `export` out, I then call `sudo docker compose restart`; do I then do `sudo docker attach` and run `export` from there?

That didn't work... Also, what would the point of using `export` be? I'm not sure where it would come in if I don't use it in either the compose file...

Ok, you're right - despite the `environment` section of my compose file being this (as above) > ``` > environment: > - JWT_SECRET=password # will use randomUUID() if unset >...

Oh, I did - I just copied the lines from my previous comment, and forgot I had `export` in there. This is what I have: > ``` > environment: >...

> HTTP_ALLOWED=true only works for `localhost` serving. Ahhhh, that makes sense then. Yep, I'm trying to access the service from other machines on my LAN and Tailscale network. The server...

Yeah @tdigu, exactly the same here, just different hardware. Haven't found a resolution yet, but I remain optimistic. Looks like @C4illin just added a bug ticket two days ago, so...