So if you remove your reverse proxy it works? Then the problem is the reverse proxy configuration
Yes!
So if you remove your reverse proxy it works? Then the problem is the reverse proxy configuration
Yes!
@Falco I’ve finally found my solution! Tryed reverse proxying in HTTP with HAPROXY, NGINX, APACHE and everytime site was working but delete problem was there waiting for me.
Last night I gave a last try because I’d really like Discourse, so I told myself: go on, try with HTTPS, it will make no difference but why don’t give it a try before giving up?
Well, with HTTPS all works perfectly. For me it’s perfect this way, I’ll throw HTTP in the garbage bin
This are the relevant parts of Apache config:
<VirtualHost *:443> ServerName discourse.apicolturaitalianafb.it SSLEngine on SSLCertificateFile "/usr/local/ssl/crt/certificate.crt" SSLCertificateKeyFile "/usr/local/ssl/crt/private.key" SSLCertificateChainFile "/usr/local/ssl/crt/ca_bundle.crt" <Location /> ProxyPreserveHost On RequestHeader set Host "discourse.apicolturaitalianafb.it:8443" ProxyPass http://discourse.apicolturaitalianafb.it:8880/ </Location> </VirtualHost>
and Discourse’s app.yml:
templates: - "templates/postgres.template.yml" - "templates/redis.template.yml" - "templates/web.template.yml" - "templates/web.ratelimited.template.yml" # - "templates/web.socketed.template.yml" ## Uncomment these two lines if you wish to add Lets Encrypt (https) #- "templates/web.ssl.template.yml" #- "templates/web.letsencrypt.ssl.template.yml" ## which TCP/IP ports should this container expose? ## If you want Discourse to share a port with another webserver like Apache or nginx, ## see https://meta.discourse.org/t/17247 for details expose: - "8880:80" # http # - "8443:443" # https
It’s long past time!
Glad you got it sorted.