Open jdevang opened 3 years ago
The error message you encountered suggests that the host journal.xxxx.com is not recognized or allowed in the configuration. This issue can occur if the host is not explicitly defined in the application's configuration files.
To resolve this problem, you can try the following steps:
Open the production.rb file located in the config directory of your Journal application.
Look for the config.hosts configuration line. It should be an array that allows specific hosts for the application. If the line is not present, you can add it at the end of the file.
Add the host journal.xxxx.com to the config.hosts array. It should look like this:
config.hosts << "journal.xxxx.com"
Replace journal.xxxx.com with the actual domain you want to use.
Save the changes to the production.rb file.
If you made changes to the production.rb file inside the Docker container, rebuild the container to apply the modifications. Use the appropriate commands based on your Docker setup.
Once you've added the journal.xxxx.com host to the config.hosts array, the application should recognize and allow requests to that domain. Make sure to restart your Docker container to ensure the changes take effect.
Check your reverse proxy configuration mentioned in the docs. In my case I was using Synology's GUI to setup nginx and I left a rogue semi-colon while copy-pasting.
You will also have issues if you try to pass multiple domains to the env variable:
SITE_DOMAIN=journal.my-domain.com,diary.my-domain.com
This is because the ruby code will not split your domains into an array.
I'm running this is docker. Took the changes from the unmerged pull request as well for the docker-compose file Error:
This happens even though I have a SITE_DOMAIN env in the production.rb file. Tried hardcoding the domain instead of passing it as an env, still having the issue.