Python Django应用程序中“inet类型的输入语法无效”db错误,postgres和Gunicorn+Nginx作为反向代理

Python Django应用程序中“inet类型的输入语法无效”db错误,postgres和Gunicorn+Nginx作为反向代理,python,django,postgresql,nginx,gunicorn,Python,Django,Postgresql,Nginx,Gunicorn,你能帮我破译这个相当深奥的错误吗?当我启动应用程序时,一切都正常,但在我尝试登录时崩溃 在/登录时发生数据库错误/ inet类型的输入语法无效:第1行:…00101 Firefox/41.0', “2015-12-12 09:39:55.590036+00:00” 异常位置: /home/mhb11/.virtualenvs/redditpk/local/lib/python2.7/site-packages/django/db/backends/postgresql\u psycopg2/ba

你能帮我破译这个相当深奥的错误吗?当我启动应用程序时,一切都正常,但在我尝试登录时崩溃

在/登录时发生数据库错误/

inet类型的输入语法无效:第1行:…00101 Firefox/41.0', “2015-12-12 09:39:55.590036+00:00”

异常位置: /home/mhb11/.virtualenvs/redditpk/local/lib/python2.7/site-packages/django/db/backends/postgresql\u psycopg2/base.py 在execute中,第54行

我知道的一个事实是,服务器接受IPv4和IPv6主机和网络,但不接受域名

回溯如下:

Traceback:
File "/home/mhb11/.virtualenvs/redditpk/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
  187.                 response = middleware_method(request, response)
File "/home/mhb11/.virtualenvs/redditpk/local/lib/python2.7/site-packages/user_sessions/middleware.py" in process_response
  46.                     request.session.save()
File "/home/mhb11/.virtualenvs/redditpk/local/lib/python2.7/site-packages/user_sessions/backends/db.py" in save
  86.                     obj.save(force_insert=must_create, using=using)
File "/home/mhb11/.virtualenvs/redditpk/local/lib/python2.7/site-packages/django/db/models/base.py" in save
  546.                        force_update=force_update, update_fields=update_fields)
File "/home/mhb11/.virtualenvs/redditpk/local/lib/python2.7/site-packages/django/db/models/base.py" in save_base
  650.                 result = manager._insert([self], fields=fields, return_id=update_pk, using=using, raw=raw)
File "/home/mhb11/.virtualenvs/redditpk/local/lib/python2.7/site-packages/django/db/models/manager.py" in _insert
  215.         return insert_query(self.model, objs, fields, **kwargs)
File "/home/mhb11/.virtualenvs/redditpk/local/lib/python2.7/site-packages/django/db/models/query.py" in insert_query
  1661.     return query.get_compiler(using=using).execute_sql(return_id)
File "/home/mhb11/.virtualenvs/redditpk/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py" in execute_sql
  937.             cursor.execute(sql, params)
File "/home/mhb11/.virtualenvs/redditpk/local/lib/python2.7/site-packages/django/db/backends/util.py" in execute
  41.             return self.cursor.execute(sql, params)
File "/home/mhb11/.virtualenvs/redditpk/local/lib/python2.7/site-packages/django/db/backends/postgresql_psycopg2/base.py" in execute
  58.             six.reraise(utils.DatabaseError, utils.DatabaseError(*tuple(e.args)), sys.exc_info()[2])
File "/home/mhb11/.virtualenvs/redditpk/local/lib/python2.7/site-packages/django/db/backends/postgresql_psycopg2/base.py" in execute
  54.             return self.cursor.execute(query, args)

Exception Type: DatabaseError at /login/
Exception Value: invalid input syntax for type inet: ""
LINE 1: ...00101 Firefox/41.0', '2015-12-12 09:39:55.590036+00:00', '')
url.py中的/login/url是urlr“^login/$”、“django.contrib.auth.views.login”、{template_name':“login.html”},name=login

环境是:

Django 1.5.1具有postgresql后端,驻留在Ubuntu 14.04计算机上。特别要注意的是,在我使用端口80将nginx设置为gunicorn后面的反向代理之后,这个错误就开始出现了。当我单独使用gunicorn和waitress时,情况非常好,这是端口8080上的另一个纯python web服务器

/etc/nginx/可用站点/myproject:

server {
    listen 80;
    server_name example.cloudapp.net;

    location = /favicon.ico { access_log off; log_not_found off; }
    location /static/ {
        root /home/mhb11/folder/myproject;
    }

    location / {
        include proxy_params;
        proxy_pass http://unix:/home/mhb11/folder/myproject/myproject.sock;
    }
   error_page 500 502 503 504 /500.html;
   location = /500.html {
        root /home/mhb11/folder/myproject/templates/;
   }
}
/etc/nginx/proxy_参数:

proxy_set_header Host $http_host;
proxy_set_header User-Agent $http_user_agent;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
/etc/nginx/nginx.conf:

user www-data;
worker_processes 4;
pid /run/nginx.pid;

env ON_AZURE=1;
env awsaccesskeyid=something;
env awssecretkey=something;

events {
        worker_connections 1024;
        multi_accept on;
        use epoll;
}

http {

        ##
        # Basic Settings
        ##

        sendfile on;
        tcp_nopush on;
        tcp_nodelay on;
        keepalive_timeout 65;
        types_hash_max_size 2048;
        # server_tokens off;

        # server_names_hash_bucket_size 64;
        include /etc/nginx/mime.types;
        default_type application/octet-stream;

        ##
        # Logging Settings
        ##

        access_log /var/log/nginx/access.log;
        error_log /var/log/nginx/error.log;

        ##
        # Gzip Settings
        ##
        gzip on;
        gzip_disable "msie6";

        # gzip_vary on;
        # gzip_proxied any;
        # gzip_comp_level 6;
        # gzip_buffers 16 8k;
        # gzip_http_version 1.1;
        # gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascrip$

        ##
        # nginx-naxsi config
        ##
        # Uncomment it if you installed nginx-naxsi
        ##

        #include /etc/nginx/naxsi_core.rules;

        ##
        # nginx-passenger config
        ##
        # Uncomment it if you installed nginx-passenger
        ##

        #passenger_root /usr;
        #passenger_ruby /usr/bin/ruby;

        ##
        # Virtual Host Configs
        ##

        include /etc/nginx/conf.d/*.conf;
        include /etc/nginx/sites-enabled/*;
}


#mail {
#       # See sample authentication script at:
#       # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
#
#       # auth_http localhost/auth.php;
#       # pop3_capabilities "TOP" "USER";
#       # imap_capabilities "IMAP4rev1" "UIDPLUS";
#
#       server {
#               listen     localhost:110;
#               protocol   pop3;
#               proxy      on;
#       }
#
#       server {
#               listen     localhost:143;
#               protocol   imap;
#               proxy      on;
#       }
#}
发生什么事了


注意:如果您需要,请询问我更多信息,例如我的gunicorn.conf和nginx.conf的外观、安装的软件包或您是否需要与数据库相关的内容。随便问吧

您的程序正在尝试向某个远程IP为空的日志记录表添加一行。我假设,当您使用反向代理时,程序不知道远程IP,因为它被代理的IP所遮蔽

由于它是空的,我想程序试图忽略代理的IP,但它没有找到更好的。它应该使用X-Forwarded-For报头


如果没有合理的IP来记录,程序应该简单地将NULL作为IP记录。

您的程序正在尝试向某个远程IP为空的记录表添加一行。我假设,当您使用反向代理时,程序不知道远程IP,因为它被代理的IP所遮蔽

由于它是空的,我想程序试图忽略代理的IP,但它没有找到更好的。它应该使用X-Forwarded-For报头


如果没有合理的IP来记录,程序只需将NULL作为IP记录。

您没有转发代理IP。以下是我在nginx配置中设置的转发头集:

location / {
    proxy_set_header    Host                    $http_host;
    proxy_set_header    User-Agent              $http_user_agent;
    proxy_set_header    X-Real-IP               $remote_addr;
    proxy_set_header    X-Forwarded-For         $proxy_add_x_forwarded_for;
    proxy_set_header    X-Forwarded-Proto       $scheme;
    proxy_pass          ......;
}
nginx文档中的更多选项-

然后在Django,您可以执行以下操作:

user_ip = request.META['HTTP_X_REAL_IP`] or request.META['REMOTE_ADDR']
请注意,在将Django与SSL一起使用时,X-Forwarded-Proto是必需的,在这种情况下,您还需要稍微配置Django:

SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')

更多Django文档-

您没有转发代理IP。以下是我在nginx配置中设置的转发头集:

location / {
    proxy_set_header    Host                    $http_host;
    proxy_set_header    User-Agent              $http_user_agent;
    proxy_set_header    X-Real-IP               $remote_addr;
    proxy_set_header    X-Forwarded-For         $proxy_add_x_forwarded_for;
    proxy_set_header    X-Forwarded-Proto       $scheme;
    proxy_pass          ......;
}
nginx文档中的更多选项-

然后在Django,您可以执行以下操作:

user_ip = request.META['HTTP_X_REAL_IP`] or request.META['REMOTE_ADDR']
请注意,在将Django与SSL一起使用时,X-Forwarded-Proto是必需的,在这种情况下,您还需要稍微配置Django:

SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')

Django文档中的更多内容-

添加自定义中间件解决了这一问题:

class XForwardedForMiddleware():
    def process_request(self, request):
        if request.META.has_key("HTTP_X_FORWARDED_FOR"):
            request.META["HTTP_X_PROXY_REMOTE_ADDR"] = request.META["REMOTE_ADDR"]
            parts = request.META["HTTP_X_FORWARDED_FOR"].split(",", 1)
            request.META["REMOTE_ADDR"] = parts[0]

添加自定义中间件解决了这一问题:

class XForwardedForMiddleware():
    def process_request(self, request):
        if request.META.has_key("HTTP_X_FORWARDED_FOR"):
            request.META["HTTP_X_PROXY_REMOTE_ADDR"] = request.META["REMOTE_ADDR"]
            parts = request.META["HTTP_X_FORWARDED_FOR"].split(",", 1)
            request.META["REMOTE_ADDR"] = parts[0]

嗯,好吧,为了试试看,我应该为$remote\u addr添加代理\u set\u头X-Forwarded;在my/etc/nginx/sites available/myproject文件中?或者我应该将其添加到我的nginx.conf中?请给出建议。在仔细查看了从nginx传递到Django应用程序的request.META之后,我发现REMOTE_ADDR是“”,尽管HTTP_X_REAL_IP和HTTP_REMOTE_ADDR设置正确。Postgresql IP属于INET类型,而不是字符串,并且“”也不是您猜测的可接受值。如何为REMOTE\u ADDR设置一个值?嗯,好的,为了尝试,我应该为$REMOTE\u ADDR添加代理\u set\u头X-Forwarded;在my/etc/nginx/sites available/myproject文件中?或者我应该将其添加到我的nginx.conf中?请给出建议。在仔细查看了从nginx传递到Django应用程序的request.META之后,我发现REMOTE_ADDR是“”,尽管HTTP_X_REAL_IP和HTTP_REMOTE_ADDR设置正确。Postgresql IP属于INET类型,而不是字符串,并且“”也不是您猜测的可接受值。如何为REMOTE_ADDR设置值?据我所知,proxy_set_头指令只能在location块中使用。我更新了答案,以反映这一点,通常在myproject.conf文件中。虽然我通常将这些指令放在一个单独的文件proxy_params.conf中,我通过include指令将其包含在我的位置块中,但这不是必需的。现在只需硬编码它们。这将开始向Django发送正确的头。如果仍然不起作用,那么问题就在Django。打印出request.META以查看nginx发送给DjangoHTTP_X_FORWARDED_的所有头是错误的。这将是代理服务器的IP,在您的案例中是nginx,实际上我错了。HTTP_X_FORWARDED_FOR将包含用户的真实ip,但是您需要对其进行解析,因为它将是以逗号分隔的ip列表,等等。我更新了答案
据我所知,proxy_set_header指令只能在location块中使用。我更新了答案,以反映这一点,通常在myproject.conf文件中。虽然我通常将这些指令放在一个单独的文件proxy_params.conf中,我通过include指令将其包含在我的位置块中,但这不是必需的。现在只需硬编码它们。这将开始向Django发送正确的头。如果仍然不起作用,那么问题就在Django。打印出request.META以查看nginx发送给DjangoHTTP_X_FORWARDED_的所有头是错误的。这将是代理服务器的IP,在您的案例中是nginx,实际上我错了。HTTP_X_FORWARDED_FOR将包含用户的真实ip,但是您需要对其进行解析,因为它将是以逗号分隔的ip列表,等等。我更新了答案