Changes between Initial Version and Version 1 of Ticket #931


Ignore:
Timestamp:
03/13/16 23:02:51 (9 years ago)
Author:
Maxim Dounin
Comment:

The server_name in the configuration snippet you've provided is wrong. You should use ​punycode-encoded name instead, xn--80aaagiydsciqb5hsf.xn--p1ai (as seen in the Host header of the HTTP request).

This is likely what causes your other issues. Note that according to the log provided the error is returned no by nginx but by your backend server. Likely this backend is configured in the default server{} block - as no matching server_name is found, the default server{} block is used by nginx to process the request.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #931

    • Property Status new → closed
    • Property Resolution → invalid

  • Ticket #931 – Description

    initial v1  
    44
    55debug.log:
     6{{{
    672016/03/13 09:32:20 [debug] 16419#0: accept on 0.0.0.0:80, ready: 0
    782016/03/13 09:32:20 [debug] 16419#0: posix_memalign: 00007F6A8C587EB0:256 @16
    … …  
    1971982016/03/13 09:32:20 [debug] 16419#0: *16 recv() not ready (11: Resource temporarily unavailable)
    1981992016/03/13 09:32:20 [debug] 16419#0: *16 free: 00007F6A8C4C6B30
     200}}}
    199201
    200202more error.log
     203{{{
    2012042016/03/13 09:18:04 [notice] 16418#0: signal process started
     205}}}
    202206(note that was some time before my attempt to connect).
    203207
    … …  
    206210My nginx.conf:
    207211
     212{{{
    208213server {
    209214    server_name людмилавахнина.рф;
    … …  
    226231    }
    227232}
     233}}}
    228234
    229235I don't have much memory on the machine, but probably that should be enough,
     236{{{
    230237$ free
    231238              total        used        free      shared  buff/cache   available
    232239Mem:         262144      136308       19444        5756      106392       46756
    233240Swap:             0           0           0
     241}}}