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.
See this is not an issue with self-host Forem. Depending upon your DNS provider check the documentation to create a 301 Redirect. 301 Redirect for @ -> www
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.
As you installed forem on subdomain www, you cannot access your Forem via root domain.
I haven't check this yet, but rather than using www as subdomain => try using @(means root). Now you can access your community on https://your-domain.com only.
Let me know your result in the above sever configuration => if it works then its good, or else I will look into it.
I tried switching to @ instead of www and now I get this error and I couldn't access it at all. Now I tried switching back to the default settings and I get this 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.
See this is not an issue with self-host Forem. Depending upon your DNS provider check the documentation to create a
301 Redirect. 301 Redirect for@ -> wwwwhat I'm hoping to do is not have www. at all, I deployed following the selfhost guide and used
forem_subdomain_name: wwwin my setup.ymlI'm hoping to not have to have to use
wwwand redirecting from www. to @ doesn't work.I see others are having this same issue:
github.com/forem/selfhost/issues/24
As you installed forem on subdomain
www, you cannot access your Forem viarootdomain.I haven't check this yet, but rather than using
wwwas subdomain => try using@(means root). Now you can access your community onhttps://your-domain.comonly.I tried switching to
@instead ofwwwand now I get this error and I couldn't access it at all. Now I tried switching back to the default settings and I get this error 😭You switch to @, but why do you seach for a domain with www
Also, make sure you edited domain settings in your ansible settings and push those changes to digital ocean => then chage DNS settings.
I didn't get this error when I switched to @. Apologies, I must have not edited my comment.
this is what I get after reverting all changes back to the original settings.