HTTPS over port 443

fugee ohu fugee279 at gmail.com
Tue Aug 7 23:18:20 UTC 2018


If I have `listen 80 ssl;` would that do the redirect automatically
for me without the explicit redirect you gave me?

On Tue, Aug 7, 2018 at 6:23 PM, Jeff Dyke <jeff.dyke at gmail.com> wrote:
> how about adding
> server {
>    listen 80;
>    redirect https://$host$request_uri 301;  //YYMV as to what destination
> you need them to end up at.
> }
>
> On Tue, Aug 7, 2018 at 3:58 PM, fugee ohu <fugee279 at gmail.com> wrote:
>>
>> What do you mean by "also have a port 80 config" ? The port 80 configs
>> are my other sites that I haven't created certificates for yet The
>> port 80 config for the site in question is commented out in favor of
>> `listen 443 ssl;`
>>
>>
>> On Tue, Aug 7, 2018 at 3:45 PM, basti <mailinglist at unix-solution.de>
>> wrote:
>> > 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 <mailinglist at 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 at nginx.org
>> >>>> http://mailman.nginx.org/mailman/listinfo/nginx
>> >>>>
>> >>> _______________________________________________
>> >>> nginx mailing list
>> >>> nginx at nginx.org
>> >>> http://mailman.nginx.org/mailman/listinfo/nginx
>> >> _______________________________________________
>> >> nginx mailing list
>> >> nginx at nginx.org
>> >> http://mailman.nginx.org/mailman/listinfo/nginx
>> >>
>> > _______________________________________________
>> > nginx mailing list
>> > nginx at nginx.org
>> > http://mailman.nginx.org/mailman/listinfo/nginx
>> _______________________________________________
>> nginx mailing list
>> nginx at nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
>
>
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx


More information about the nginx mailing list