Blank page after create admin user due to request.base_url mismatch

[colindomoney]

I am attempting to install Forem on DigitalOcean using the instructions provided on the Forem community. Everything has worked fine until the point that I attempt to create an Admin user and I encounter the blank page after login issue described previously here #13696, #4955 and was apparently fixed in #13792.

It's also been reported on the Forem community many times: https://forem.dev/manuel/forem-blank-page-after-login-using-docker-221d

I have tried a number of browsers, and incognito mode. I've destroyed my installation and re-run it and it is perfectly repeatable.

Looking at the Forem logs I can see the following: Sep 04 15:33:49 42Community.ayepeye.online forem-rails[2333]: W, [2022-09-04T15:33:49.976150 #10] WARN -- : [03fa6965-d49f-403a-a74d-5f323cc7286c] [dd.env=production dd.service=rails-production dd.trace_id=2356142424308383989 dd.span_id=0] HTTP Origin header (https://42community.ayepeye.online) didn't match request.base_url (https://42community.ayepeye.online)

I believe this relates to the APP_DOMAIN variable so I tried to manually override this and restart Forem but without luck.

What else can I do to diagnose this issue?

[github-actions[bot]]

Thanks for the issue, we will take it into consideration! Our team of engineers is busy working on many types of features, please give us time to get back to you.

Feature requests that require more discussion may be closed. Read more about our feature request process on forem.dev.

To our amazing contributors: issues labeled bug are always up for grabs, but for feature requests, please wait until we add a ready for dev before starting to work on it.

To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem-team. The OSS Community Manager or the engineers on OSS rotation will follow up.

For full info on how to contribute, please check out our contributors guide.

[wojtekxtx]

Installing Forem on DO is not so simple ( in fact not only on DO: everywhere is not so simple ).

Try fucker/joomla-shit disqally:

[mercy-thuyle]

Hello @colindomoney , Did you solved this? I stuck like you :((( I also run in EC2 with docker-compose file and overried the APP_DOMAIN.

[colindomoney]

Hey @mercy-thuyle - no I didn't solve it, and gave up on Forem which is a pity. So many people see this issue in various forms and report it yet no-one seems to respond definitively or fix it upstream. If I knew Rails better I would look into it but I will go back to WordPress 😬

[ChaelCodes]

I ran into this issue as well but using the docker setup on my local machine.

I changed the app_domain variable in the docker-compose.yml file to my domain, restarted the containers, and I was able to login.

[richmonde]

I also met this with docker setup on my server. The post said it may be .env's problem but as I made a mistake in .env the python-dotenv would show a waring message about it. I tried modifying the APP_DOMAIN item of docker-compose.yml and .env to 0.0.0.0:3000 and it still didn't work 😟 However,I modified APP_DOMAIN of docker-compose.yml to my server's ip and I succeeded in login.