Lemmy Support

4718 readers

2 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago

MODERATORS

[email protected]

Encountering OriginNotAllowed error during fresh install (self.lemmy_support)

submitted 2 years ago by Ambrotos to c/[email protected]

4 comments fedilink hide all child comments

Rookie Lemmy admin here, trying to get an instance off the ground. I've followed the docker install instructions located here: https://join-lemmy.org/docs/administration/install_docker.html

Everything starts correctly, no errors in any logs, I can access lemmy-ui at the correct domain as expected. But when I try to login nothing happens. If I check the lemmy logs I see the following error:

WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Origin is not allowed to make this request

I'm pulling my container from dessalines/lemmy:latest, which means I'm running v0.18 (I'm installing on a fresh install of Ubuntu 22.04 LTS, if that matters). I see from the Lemmy change log there have been several changes related to CORS, including the addition of a LEMMY_CORS_ORIGIN environment variable. I thought maybe the example configs included in the installation documentation were out of date, so I added that environment variable to my docker compose file and restarted lemmy. No change in behaviour. I've tried setting that ENV to every combination of host/port I can think of with no success. I also enabled debug level logging on the lemmy docker, hoping that the log message would tell me the explicit origin that it was seeing so I'd know what to set the ENV to, but no luck.

Can anyone provide me with some tips? What am I supposed to set the LEMMY_CORS_ORIGIN variable to? Has anyone else encountered this error?

top 4 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 2 years ago

I think I encountered the same problem setting up today. After digging around in https://github.com/LemmyNet/lemmy/pull/3421 for a while, I came to the conclusion that this is broken in latest/18 right now (probably shouldn't have been pointed there anyway). Switching my docker compose file to point at the 17 release resolved this issue for me without me having to set the CORS ORIGIN env var.

[–] [email protected] 1 points 2 years ago (1 children)

did you figure it out?

[–] [email protected] 1 points 2 years ago (1 children)

figured it out on mine in my docker compose I had my external url to https and I was using http, will force redirect to https now

[–] Ambrotos 1 points 2 years ago

Thanks for posting your solution. Hopefully it'll help others in the future. For me, I wound up restarting from scratch with the ansible based deployment solution. I'd seen comments from others who'd had problems getting docker-compose to deploy properly. The ansible playbook spun up an instance first time no problem for me.