first of all use wget or curl for testing to bypass browser cache. when you have also a port 80 config and call http://example.com you *must* have a redirect to https. when you call https://example.com it should work, i think (not tested)
On 07.08.2018 21:39, fugee ohu wrote: > server { > listen 443 ssl; > ssl_certificate /etc/ssl/certs/sitename/certificate.crt; > ssl_certificate_key /etc/ssl/certs/sitename/private.key; > server_name *.sitename.com www.sitename.com sitename; > charset utf-8; > location / { > root /usr/home/fugee/websites/sitename/public; > rails_env production; > passenger_enabled on; > } > } > > On Tue, Aug 7, 2018 at 3:28 PM, basti <mailingl...@unix-solution.de> wrote: >> please show us your config >> >> On 07.08.2018 21:22, fugee ohu wrote: >>> I'm trying to enable site wide ssl over port 443 on a site that runs >>> on http port 80 >>> In nginx.conf i have `listen 443 ssl;` for the server but requests for >>> the server get routed to the first available host on port 80, another >>> of my sites also in the nginx.conf How can I diagnose this to see >>> what's going on? >>> _______________________________________________ >>> nginx mailing list >>> nginx@nginx.org >>> http://mailman.nginx.org/mailman/listinfo/nginx >>> >> _______________________________________________ >> nginx mailing list >> nginx@nginx.org >> http://mailman.nginx.org/mailman/listinfo/nginx > _______________________________________________ > nginx mailing list > nginx@nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx > _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx