I am an Engineering Physics graduate from IIT Guwahati, but merely not restricted to Physics itself. In the past few years, I involved in many Cybersecurity blogging and now on Open-source.
Hey @markomannux
, If you have a domain, try to follow this and let me know what is the status.
This is how I eliminated most of the issues related to onboarding message errors and InvalidAuthenticityToken error
I have a domain in Cloudflare, so I created a CNAME record on the subdomain(ex: dev.leewardslope.com) and attached the external IP address. Only the IP, no need of port.
As the Forem service is running on the port 3000, we need to look at this issue too, so I installed Nginx and port forwarded the fort 3000 to 80. So that there is no need to use the port 3000 anymore. Here is a more detailed guide which might be useful in configuring IP: PORT to a domain name.
In .env file, change the APP_DOMAIN to your domain, in my case: dev.leewardslope.com
Also, don't forget to update these in GitHub too, the URL for authentication, I guess you used localhost:3000 or your IP:3000.
Also if you don't have a domain of your own and don't want to invest some bucks right now, you can use this site to create a free domain for now.
Hey @akhil
, thanks for your hint: it put me on the right track. I had no clue hostname could be an issue.
Since I don't actually need social login, turns out the setup is even simpler.
I tried to set APP_DOMAIN with no luck but I noticed that container-compose.yml declared it as rails.
So I added an entry in my hosts file like this
127.0.0.1 rails
navigated to http://rails:3000 (no need to change the port) and no more InvalidAuthenticityToken error 🎉
I am an Engineering Physics graduate from IIT Guwahati, but merely not restricted to Physics itself. In the past few years, I involved in many Cybersecurity blogging and now on Open-source.
Hey @markomannux , If you have a domain, try to follow this and let me know what is the status.
This is how I eliminated most of the issues related to
onboarding message errors
andInvalidAuthenticityToken error
Thanks @akhil ! I'll try your suggestions as soon as possible and keep you posted.
Hey @akhil , thanks for your hint: it put me on the right track. I had no clue hostname could be an issue.
Since I don't actually need social login, turns out the setup is even simpler.
I tried to set APP_DOMAIN with no luck but I noticed that container-compose.yml declared it as
rails
.So I added an entry in my hosts file like this
navigated to
http://rails:3000
(no need to change the port) and no moreInvalidAuthenticityToken
error 🎉Thanks again!
Rather than modifying the host file, what about changing it in the
container-compose.yml
?If I had a DNS record pointing to my environment, that would be certainly better.
For a local setup for testing purposes without DNS, I think the hosts file record is the only viable option.
Thanks again!