Discourse site loads via IP but via domain only header

Support
23

You should start over from scratch and rebuild. Something is deeply wrong with your configuration.

2 Likes
25

Learned from a PM:

When targeting your (non-cloudflared) reverse proxy:

○ → curl -k https://forum.pivx.org/assets/ember_jquery-07f49b58317ea9292d939348ec0091eb50a9d8aaabd9e86cc074ef5f049918aa.js | wc -c
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  8  575k    8 48746    0     0  73901      0  0:00:07 --:--:--  0:00:07 73857
curl: (56) GnuTLS recv error (-9): A TLS packet with unexpected length was received.
48746

When targeting your actual server:

○ → curl -k http://192.0.2.100/assets/ember_jquery-07f49b58317ea9292d939348ec0091eb50a9d8aaabd9e86cc074ef5f049918aa.js | wc -c
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  575k  100  575k    0     0  1016k      0 --:--:-- --:--:-- --:--:-- 1017k
589450

Your reverse proxy is broken and you need to fix it. This is not a Discourse problem.

6 Likes
26

When pointing the cloudflare A record to the normal server IP it doesn’t connect to the site. Only over the reverse proxy. thanks for the assistance thus far.

27

I’m getting these same errors too, on a fresh install. I have cloudflare for my root domain, but it’s bypassing on the subdomain I’ve installed discourse to https://forum.theopen.institute. I followed the instructions here for running other sites on the same machine.

The strange thing is, each time, I am able to get most of the way through the welcome and installation process before I start getting the ERR_SPDY_PROTOCOL_ERROR responses in console.

28

t turns out that (in my case at least) the problem was indeed outside Discourse. I had a permissions problem in my /var/lib/nginx/fastcgi folder. chowning back over to my nginx got discourse working.

It sounds like OP’s issue was different, but since the symptoms and error messages were similar I thought I’d post an update for anyone coming through in the future.

29

My issue is solved, Turns out the reverse proxy was running out of disk space and thus couldn’t process the files.

3 Likes