The user jo-andre is experiencing an issue with a new Discourse installation where instead of the expected Discourse registration page, a default Apache test page appears. Despite multiple reinstallations and server restarts, the problem persists. merefield, Jagster, Fluttercode, and Stephen suggest that Apache is interfering, likely due to misconfigured vhosts or DNS settings. Jagster notes that Apache isn’t part of the standard Discourse setup and shouldn’t be installed. Stephen questions whether the DNS is incorrectly set. jo-andre later realizes the issue may be DNS-related, as the server’s IP was pointing to both the main domain and subdomain, and resolves the issue by removing the main domain from DNS. jo-andre thanks the contributors for their help.
Hello. I’ve installed Discourse a few times now without problem. And I did one install yesterday. And it all went ok. But I reinstalled it for some reason. I’ve done as previously. But now I don’t get the discourse register page but a Apache test page instead. I’ve restarted my server. Full wipe. And reinstalled it. Same problem.
My site > Forum.byggforum.no
Installation steps used
Thanks for any tips!
what happens when you turn off the apache service on your VPS?
How did you setup vhost AND app.yml? Because installation you followed won’t work per se. Apache will hijack ports 80 and 443.
And I don’t know if you are using www.byggforum.no but http gives 302 redirection and https serves error 500. So — Apache2 is broken.
Not to insult anyones intelligence, but I always look at the error_log file whenever I get a default Apache page. It’s usually just a permission error or pointing to a wrong directory.
You aren’t insulting anyone’s intelligence, it’s more that Apache isn’t part of discourse and won’t be installed anywhere if you’re following the standard install.
@jo-andre You need to provide more information about the server and why Apache is present in the first place.
Hey sorry for late respons!
i have no idea why Apache is running. or installed. this is a fresh server.
edit: Cant even find it …
Could your DNS be set incorrectly?
Does Apache still respond during a server reboot? That’s usually a good clue that it’s not the same system responding.
yeah, probably. That’s my thing!
The ip of the server where pointing too the main domain & sub-domain.
i removed the one pointing to main domain and ill try again.
edit Thanks! i would never tought of that! 
Many thanks for helping out @merefield @Jagster @Fluttercode & @Stephen 
That is how it should work, because both are on same IP address. Your vhosts aren’t right, I guess. But one way to fix that is remove ”main domain” from DNS.