# Upstream may not have port 80 ; upgrade from 1.2.1 to 1.4.1 **URL:** \ **Category:** NGINX\ **Created:** [June 3, 2013, 12:32pm UTC](https://www.ruby-forum.com/t/upstream-may-not-have-port-80-upgrade-from-1-2-1-to-1-4-1/235153 "2013-06-03T12:32:16Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![addis\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/c4cdca/32.png) [@addis\_a](https://www.ruby-forum.com/u/addis_a)\ **Post date:** [June 3, 2013, 12:32pm UTC](https://www.ruby-forum.com/t/upstream-may-not-have-port-80-upgrade-from-1-2-1-to-1-4-1/235153/1 "2013-06-03T12:32:16Z")
Hi, After running nginx 1.2.1 with the following configuration, I now get warnings when testing the same configuration under 1.4.1 Any advice on this would be highly appreciated. [error] $ nginx -t -c /tmp/nginx.conf nginx: [warn] upstream “appcluster-secure” may not have port 80 in /tmp/nginx.conf:60 nginx: configuration file /tmp/nginx.conf test failed $ nginx -V nginx version: nginx/1.4.1 TLS SNI support enabled configure arguments: --prefix=/usr/local/etc/nginx --with-cc-opt=‘-I /usr/local/include’ --with-ld-opt=‘-L /usr/local/lib’ –conf-path=/usr/local/etc/nginx/nginx.conf –sbin-path=/usr/local/sbin/nginx --pid-path=/var/run/nginx.pid –error-log-path=/var/log/nginx-error.log --user=www --group=www –with-ipv6 --http-client-body-temp-path=/var/tmp/nginx/client\_body\_temp –http-fastcgi-temp-path=/var/tmp/nginx/fastcgi\_temp –http-proxy-temp-path=/var/tmp/nginx/proxy\_temp –http-scgi-temp-path=/var/tmp/nginx/scgi\_temp –http-uwsgi-temp-path=/var/tmp/nginx/uwsgi\_temp –http-log-path=/var/log/nginx-access.log --with-http\_stub\_status\_module –add-module=/usr/ports/www/nginx/work/nginx-sticky-module-1.1 –with-pcre –add-module=/usr/ports/www/nginx/work/yaoweibin-nginx\_tcp\_proxy\_module-b83e5a6 –with-http\_ssl\_module [http] Server listen on 192.168.1.227:80 forwards to 192.168.3.224:80 Server listen on 192.168.1.226:80 forwards to 192.168.0.123:80 and 192.168.0.124:80 [tcp] Server listen on 192.168.1.226:443 forwards to 192.168.0.123:443 and 192.168.0.124:443 —[nginx.conf]— 1 # $Id: nginx.conf,v 1.15 2013/06/03 07:16:28 root Exp $ 2 3 #user nobody; 4 worker\_processes 1; 5 6 events { 7 worker\_connections 1024; 8 } 9 10 http { 11 proxy\_read\_timeout 300; 12 13 upstream appcluster { 14 sticky; 15 server 192.168.0.123:80; 16 server 192.168.0.124:80; 17 } 18 19 upstream single\_server { 20 sticky; 21 server 192.168.3.244:80; 22 } 23 24 default\_type application/octet-stream; 25 sendfile on; 26 keepalive\_timeout 65; 27 28 server { 29 listen 192.168.1.227:80; 30 server\_name localhost; 31 location / { 32 proxy\_pass http://single\_server; 33 proxy\_set\_header Host $host; 34 } 35 error\_page 500 502 503 504 /50x.html; 36 location = /50x.html { 37 root /usr/local/www/nginx-dist; 38 } 39 } 40 41 server { 42 listen 192.168.1.226:80; 43 server\_name localhost; 44 location / { 45 proxy\_pass [http://appcluster](http://appcluster); 46 proxy\_set\_header Host $host; 47 } 48 } 49 } 50 51 tcp { 52 upstream appcluster-secure { 53 server 192.168.0.123:443; 54 server 192.168.0.124:443; 55 } 56 server { 57 listen 192.168.1.226:443; 58 server\_name \_; 59 tcp\_nodelay on; 60 proxy\_pass appcluster-secure; 61 } 62 } 63 } 64 —[EOF]— – Rasmus G. Andersen ---
**Author:** ![Rasmus\_Glud\_Anderse](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/ecd19e/32.png) [@Rasmus\_Glud\_Anderse](https://www.ruby-forum.com/u/Rasmus_Glud_Anderse)\ **Post date:** [June 3, 2013, 1:07pm UTC](https://www.ruby-forum.com/t/upstream-may-not-have-port-80-upgrade-from-1-2-1-to-1-4-1/235153/2 "2013-06-03T13:07:21Z")
Hello! On Mon, Jun 03, 2013 at 11:31:58AM +0200, Rasmus Glud Andersen wrote: > nginx: configuration file /tmp/nginx.conf test failed > > $ nginx -V > nginx version: nginx/1.4.1 > TLS SNI support enabled > configure arguments: --prefix=/usr/local/etc/nginx --with-cc-opt=‘-I > /usr/local/include’ --with-ld-opt=‘-L /usr/local/lib’ > –conf-path=/usr/local/etc/nginx/nginx.conf --sbin-path=/usr/local/sbin/nginx > –pid-path=/var/run/nginx.pid --error-log-path=/var/log/nginx-error.log --user=www > –group=www --with-ipv6 > –http-client-body-temp-path=/var/tmp/nginx/client\_body\_temp > –http-fastcgi-temp-path=/var/tmp/nginx/fastcgi\_temp > –http-proxy-temp-path=/var/tmp/nginx/proxy\_temp > –http-scgi-temp-path=/var/tmp/nginx/scgi\_temp > –http-uwsgi-temp-path=/var/tmp/nginx/uwsgi\_temp > –http-log-path=/var/log/nginx-access.log --with-http\_stub\_status\_module > –add-module=/usr/ports/www/nginx/work/nginx-sticky-module-1.1 --with-pcre > –add-module=/usr/ports/www/nginx/work/yaoweibin-nginx\_tcp\_proxy\_module-b83e5a6 > –with-http\_ssl\_module You have to upgrade tcp proxy module to a newer version. […] – Maxim D. > **[nginx: donation](http://nginx.org/en/donation.html)** ---
**Author:** ![Rasmus\_Glud\_Anderse](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/ecd19e/32.png) [@Rasmus\_Glud\_Anderse](https://www.ruby-forum.com/u/Rasmus_Glud_Anderse)\ **Post date:** [June 3, 2013, 2:53pm UTC](https://www.ruby-forum.com/t/upstream-may-not-have-port-80-upgrade-from-1-2-1-to-1-4-1/235153/3 "2013-06-03T14:53:07Z")
On Mon, Jun 03, 2013 at 03:06:46PM +0400, Maxim D. wrote: > > $ nginx -V > > nginx version: nginx/1.4.1 > > TLS SNI support enabled > > configure arguments: --prefix=/usr/local/etc/nginx --with-cc-opt=‘-I > > /usr/local/include’ --with-ld-opt=‘-L /usr/local/lib’ > > –conf-path=/usr/local/etc/nginx/nginx.conf --sbin-path=/usr/local/sbin/nginx > > –pid-path=/var/run/nginx.pid --error-log-path=/var/log/nginx-error.log --user=www > > –group=www --with-ipv6 > > –http-client-body-temp-path=/var/tmp/nginx/client\_body\_temp > > –http-fastcgi-temp-path=/var/tmp/nginx/fastcgi\_temp > > –http-proxy-temp-path=/var/tmp/nginx/proxy\_temp > > –http-scgi-temp-path=/var/tmp/nginx/scgi\_temp > > –http-uwsgi-temp-path=/var/tmp/nginx/uwsgi\_temp > > –http-log-path=/var/log/nginx-access.log --with-http\_stub\_status\_module > > –add-module=/usr/ports/www/nginx/work/nginx-sticky-module-1.1 --with-pcre > > –add-module=/usr/ports/www/nginx/work/yaoweibin-nginx\_tcp\_proxy\_module-b83e5a6 > > –with-http\_ssl\_module > > You have to upgrade tcp proxy module to a newer version. […] Thank you, solved the problem. – Rasmus G. Andersen