# Unsupported FastCGI protocol - Django **URL:** \ **Category:** NGINX\ **Created:** [November 22, 2012, 1:41pm UTC](https://www.ruby-forum.com/t/unsupported-fastcgi-protocol-django/224708 "2012-11-22T13:41:20Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![aris](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/258eb7/32.png) [@aris](https://www.ruby-forum.com/u/aris)\ **Post date:** [November 22, 2012, 1:41pm UTC](https://www.ruby-forum.com/t/unsupported-fastcgi-protocol-django/224708/1 "2012-11-22T13:41:20Z")
I can no longer access my Django app via a nginx / fastcgi proxy on Centos 5.7 after upgrading to Django 1.4.2 Upgrading nginx via yum didn’t solve the problem. The error message in the logs is: upstream sent unsupported FastCGI protocol version: 60 while reading response header from upstream There’s a thread in the Russian list on this error. Can any Russian speakers shed any light on this? Thanks Michela Posted at Nginx Forum: > **[unsupported FastCGI protocol - Django](https://forum.nginx.org/read.php?2,233136,233136#msg-233136)** > > I can no longer access my Django app via a nginx / fastcgi proxy on Centos 5.7 after upgrading to Django 1.4.2 Upgrading nginx via yum didn't solve the problem. The error message in the logs is: upstream sent unsupported FastCGI protocol version: 60... ---
**Author:** ![michela](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/898d66/32.png) [@michela](https://www.ruby-forum.com/u/michela)\ **Post date:** [November 22, 2012, 2:05pm UTC](https://www.ruby-forum.com/t/unsupported-fastcgi-protocol-django/224708/2 "2012-11-22T14:05:19Z")
On Nov 22, 2012, at 16:40 , michela wrote: > I can no longer access my Django app via a nginx / fastcgi proxy on Centos > 5.7 after upgrading to Django 1.4.2 > > Upgrading nginx via yum didn’t solve the problem. > > The error message in the logs is: > > upstream sent unsupported FastCGI protocol version: 60 while reading > response header from upstream 60 is a code of “\<” character and probably begin of “”. This means that Django response is HTTP but not is FastCGI protocol. – Igor S. > **[Technical Support for NGINX and NGINX Plus Software](https://www.nginx.com/support/)** > > Get the help you need with support directly from the authors and maintainers of NGINX Open Source and NGINX Plus. ---
**Author:** ![michela](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/898d66/32.png) [@michela](https://www.ruby-forum.com/u/michela)\ **Post date:** [November 23, 2012, 7:36pm UTC](https://www.ruby-forum.com/t/unsupported-fastcgi-protocol-django/224708/3 "2012-11-23T19:36:09Z")
Use of uWSGI protocol is much more common for Django. [http://projects.unbit.it/uwsgi/](http://projects.unbit.it/uwsgi/) Both NGINX and Django natively support this protocol. Posted at Nginx Forum: > **[Re: unsupported FastCGI protocol - Django](https://forum.nginx.org/read.php?2,233136,233191#msg-233191)** > > I can no longer access my Django app via a nginx / fastcgi proxy on Centos 5.7 after upgrading to Django 1.4.2 Upgrading nginx via yum didn't solve the problem. The error message in the logs is: upstream sent unsupported FastCGI protocol version: 60... ---
**Author:** ![michela](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/898d66/32.png) [@michela](https://www.ruby-forum.com/u/michela)\ **Post date:** [November 23, 2012, 8:33pm UTC](https://www.ruby-forum.com/t/unsupported-fastcgi-protocol-django/224708/4 "2012-11-23T20:33:59Z")
On Friday 23 November 2012 22:35:28 Wireless wrote: > Use of uWSGI protocol is much more common for Django. > [The uWSGI project — uWSGI 2.0 documentation](http://projects.unbit.it/uwsgi/) > > Both NGINX and Django natively support this protocol. Django doesn’t support uwsgi. You probably have confused it with wsgi. It’s completely different thing. wbr, Valentin V. Bartenev – > **[Technical Support for NGINX and NGINX Plus Software](https://www.nginx.com/support/)** > > Get the help you need with support directly from the authors and maintainers of NGINX Open Source and NGINX Plus. [http://nginx.org/en/donation.html](http://nginx.org/en/donation.html) ---
**Author:** ![michela](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/898d66/32.png) [@michela](https://www.ruby-forum.com/u/michela)\ **Post date:** [November 24, 2012, 3:32pm UTC](https://www.ruby-forum.com/t/unsupported-fastcgi-protocol-django/224708/5 "2012-11-24T15:32:19Z")
On Saturday 24 November 2012 10:09:19 Wireless wrote: > “Django doesn’t support uwsgi” > > [How to use Django with uWSGI | Django documentation | Django](https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/uwsgi/#how-to-u) > se-django-with-uwsgi According to your link: “Configuring and starting the uWSGI server for Django”. It doesn’t mean that django supports the uwsgi protocol natively (please, do not confuse the uwsgi protocol with the uWSGI server). To use FastCGI you need Flup or any other application server that talks with Django by WSGI and with nginx by FastCGI. To use uwsgi you need uWSGI. So there’s no difference. wbr, Valentin V. Bartenev – > **[Technical Support for NGINX and NGINX Plus Software](https://www.nginx.com/support/)** > > Get the help you need with support directly from the authors and maintainers of NGINX Open Source and NGINX Plus. [http://nginx.org/en/donation.html](http://nginx.org/en/donation.html) ---
**Author:** ![michela](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/898d66/32.png) [@michela](https://www.ruby-forum.com/u/michela)\ **Post date:** [November 24, 2012, 7:09am UTC](https://www.ruby-forum.com/t/unsupported-fastcgi-protocol-django/224708/6 "2012-11-24T07:09:55Z")
“Django doesn’t support uwsgi” > **[Django](https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/uwsgi/#how-to-use-django-with-uwsgi)** > > The web framework for perfectionists with deadlines. Regards Posted at Nginx Forum: > **[Re: unsupported FastCGI protocol - Django](https://forum.nginx.org/read.php?2,233136,233197#msg-233197)** > > I can no longer access my Django app via a nginx / fastcgi proxy on Centos 5.7 after upgrading to Django 1.4.2 Upgrading nginx via yum didn't solve the problem. The error message in the logs is: upstream sent unsupported FastCGI protocol version: 60...