You don't have permission to access / on this server

Product Support Self-hosting

AI-generated summary

Discussion Title: You don’t have permission to access / on this server.

The discussion revolves around chfcb experiencing issues with their Discourse installation. Initially, they encountered problems with email delivery and were later met with an error message when trying to access their website. After a while, the website stopped working, despite no changes being made.

chfcb provided a step-by-step installation setup, which included installing Ubuntu Server, Docker, and using the official Discourse installation guide. Docker output revealed that the Discourse container was not running.

supermathie suggested that another web server might be installed and running, causing the issue. They recommended removing other web server packages and using the command sudo ss -ltp | grep http to check for running processes on port 80.

After some troubleshooting, chfcb ran the command as root, but it showed no output. supermathie noted that the initial warning message could be ignored and pointed out the conflicting facts: a web server is responding, but no web server is listening on port 80.

chfcb expressed a desire to start from scratch, as the issue is puzzling and occurred without any changes being made.

1

Hi,

I had a lot of problems with the installation, most with email delivery.

But now I get this error message when trying to open my website.

I did nothing… it worked at first and after a while it didn’t work anymore.

I’m not only a beginner, but my English is also very bad. Sorry for that!

I hope somebody can help me?

2

It sounds like you have some other web server running on the system. You should not have apache or nginx installed.

3

hi

my installation setup step by step

bought virtaul server
install ubuntu server
install docker
use this install guide for discourse (discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub)

write server ip adress in domain setup at my serverprovider

docker issues me the following output

> docker ps -a
CONTAINER ID        IMAGE                 COMMAND                  CREATED             STATUS                    PORTS               NAMES
43ecc553dc2c        local_discourse/app   "/bin/bash -c 'cd /p…"   23 hours ago        Exited (1) 23 hours ago                       nervous_morse
4d4d9b1b7938        local_discourse/app   "/sbin/boot"             2 days ago          Exited (6) 37 hours ago                       app
4

This means that Discourse is not running, probably since it was unable to start due to another web server being installed and running.

You’ll want to remove other webserver packages from your host, e.g.: apache2, nginx

The command:

sudo ss -ltp | grep http

should let you know what’s running on that port.

5

sudo ss -ltp | grep http
sudo: unable to resolve host localhost.localdomain

:roll_eyes:

6

You can try this instead:

sudo ss -ltpn | grep 80

Or, run it as root without sudo.

7

user@localhost:~$ sudo ss -ltp | grep 80
sudo: unable to resolve host localhost.localdomain
[sudo] password for user:
user@localhost:~$ sudo ss -ltp | grep 80
sudo: unable to resolve host localhost.localdomain
user@localhost:~$ sudo -s
sudo: unable to resolve host localhost.localdomain
root@localhost:~# ss -ltp | grep 80
root@localhost:~# ss -ltpn | grep 80
root@localhost:~# ss -ltpn | grep http
root@localhost:~#

as you can see show me “unable the resolve …” first and then ask for the password

as root it shows nothing ?

8

oh, OK, it’s just a warning you can ignore.

You have two conflicting facts here:

  • a webserver is responding: You don’t have permission to access / on this server
  • no webserver is listening on port 80
9

yes i see …

but i did nothing and it works for 2h

and then this …

in my opinion it would be best to start at zero :roll_eyes: