Discourse on a Raspberry Pi | Blog

Your website is offline.

Also if it’s accurate happy birthday :tada:


Oh thanks for the reminder. It got lost when I moved houses a few months ago. Turned it on again just now and updated it to latest.



hi @Falco, thank you for sharing such a wonderful piece of information.
I got my first own forum running!!! Thanks to you!!!
Is it possible for me to access the forum with the machine local ip address? When my discourse hostname is already set to a domain (got it from freenom).
When i tried to access the forum with the machine’s ip address, the page always stuck at loading and never managed to load.
I got a use case where my client machine is connected to some VPN and have no access to internet. The only way for me to access the forum is through the local network ip address.

1 Like

You might find this discussion useful. You are asking for support on a very non-standard install:

1 Like

Thanks @merefield.
I find when using curl on the server’s local ip address it returns the page but not with a browser.
It’s got to do with the settings on the browser?

You need to access the app via domain name for several reasons. IP access is not supported afaik

1 Like

Got it! Thanks on the confirmation.

Maybe hardcode that IP in your local hosts file?


Thanks Falco! I will check that out.


I tried hardcode the IP in my client’s hosts file, and the browser always redirect me to the external connection.
Is it possible to provide more than one domain name to the DISCOURSE_HOSTNAME?
Do i need to set DISCOURSE_FORCE_HTTPS: to false to allow local connection? I got this from one of your article.

I am trying to install Discourse on my Raspberry Pi 4 using Dietpi OS and some apps working with Nginx like Nextcloud. I am trying to use Cloudflared service as a tunnel but after the Discourse installation is complete I can’t access Discourse site and i got 502 bad gateway error.

What kind of customization is required on Nginx? Which port should we use?

I applied this guide but without success

1 Like

My guide assumes that Discourse is the only app on the Pi, and then runs the tunnel exposing the port 80 that is assigned to the Discourse container.

Running multiple apps that share a reverse proxy, while possible, is a more advanced setup and out of the scope of this guide.

1 Like

I got this working by setting DISCOURSE_BACKUP_HOSTNAME to machinename.local and DISCOURSE_FORCE_HTTPS to false. Now i can access with my domain name and local network domain name.


Well done. Maybe should be a How To in #howto:admins ?

Thanks @merefield. Sure!
There is one problem when using a backup hostname, the images doesn’t display properly.
If the post’s images created with main hostname and when access with the backup hostname, the images will be missing. This also happens in vice-versa.

1 Like

What happens when you rebake a Post? (Rebuild HTML)

Perhaps you will need to stick to one access address.

Yeah, Rebuild HTML works. But the vpn access is broken because it depends on the local address (backup hostname).

i guess there is no solution to this…

Will this work on an armv7l?

1 Like

No it won’t. I did try, but there are some missing packages on the 32 bit ARM debian repositories that made it a no go.